Recently I got the error "automation server can't create object", for which I know the solution is to add your website to trusted sites and enable the setting: "Initialize and script ActiveX controls not marked as safe for scripting". But since this is a security issue, I searched for an alternative workaround but came up with nothing.
So, I am wondering if there is any other work around for this?
Please look at this SO question. Check if you did everything that was discussed there.
The first thing is to implement IObjectSafety interface. Then sign the activex and installer and CAB. You might also want to look at this example how to implement an activex.
Related
I've been using Jira recently and I came across a problem that I don't know how to fix it.
I have to Jira instances. when I try to link an issue to one on the other instance it doesn't link. It used to work but now it won't.
every time I try to link it I will get this even though for other projects it wasn't needed :
and when press authenticate I get this page:
afterward, when I press the link nothing changes.
Please if you are familiar with this problem help me.
afterward, when I press the link nothing changes.
I tried to link the other way and it's working but I still can't identify where the problem is.
Please if you are familiar with this problem help me.
It's all about Application Links.
Some server changes (like reverse proxy, update in web.xml, etc.) or changes in the admin user account may break the links.
You need the check Application Links between two instances; if there is a problem, try to solve that first.
If not, remove the application link from both instances and add it again.
By the way, if the users in the two Jira instances are same, enable the "OAuth" in the application links (and also be sure that the admin account is same on these two instances.)
Sources:
Linking issues
Application Links
I'd like to translate the management console to localized language. I've try to follow the instructions from http://wso2.com/library/knowledge-base/2011/11/playing-around-carbon-product-themes/ as a starting point, cause I think that should be in the same theory. But this didn't work, and cause an exception when entering the site.
I see the document is pretty old (2011), is this not work anymore? or the procedure has been changed?
Edit:
sorry, forgot to mention, I'm using WSO2 ESB 4.8.1.
Yes as you have mentioned, above link is outdated. However, the concept is same in new versions as well. Keeping an extracted jar file in the plugins directory will no longer work since we have disabled that along the way as a security fix.
Herewith I have given [1]. the latest documentation of "Customizing the Management Console" of the WSO2 Enterprise Service Bus. You can use it as a starting point.
If you need further help regarding this issue, please let me know.
Thanks,
Upul
[1]. https://docs.wso2.com/display/ESB481/Customizing+the+Management+Console
I have searched for days with no solution in sight.
I need multiple Chromium instances in one single application and each of this instance logins to the same site with different account (ex: outlook.com).
I tried this solution but there's no "OnGetCookieManager" event in DECF3 new version. Apparently there was a related bug and event onGetCookieManager was removed in the 1547 CEF3.
I tried this but it doesn't work too.
Is this really possible? How?
I'm using DCEF3 (revision: 0cc175e7a629) and Delphi XE3.
Here's what CEF3 maintainer told me:
"Cookies can be stored globally, per request context or something else entirely. It depends on whether you pass a CefRequestContext to CreateBrowser*() and what you return from CefRequestContextHandler::GetCookieManager."
I'm not entirely sure how CreateBrowser is exposed in Delphi (I only use the C++ API), but I can confirm that GetCookieManager still exists in trunk (as the only method of CefRequestContextHandler).
Quite not sure why I see this error.
I navigate to my Login View like so http://test.staging.com/mywebsite/Login
My Login view was just redone using MVC but I have seen this same error message going to an aspx page as well...
If I use http I get the error message The specified request cannot be executed from current Application Pool.
If I use https://test.staging.com/mywebsite/Login, I'm good.
If I don't specify a protocol, test.staging.com/mywebsite/Login, I get the error as well
Is there an error happening under the covers and my custom error page can't be shown like discussed here?
What are some other causes of this error?
That usually means your custom errors are configured to run as a different AppPool.
You can read more at MSDN. (See section "Using Custom Errors from Another Application Pool").
There are two ways to correct this behavior. The first is possibly not one that you are interested in because it would require you to change your current architecture and run both sites in the same application pool (such as share the same worker process memory space). To do this, simply move the /errors virtual directory to run in the same application pool as the site for which it serves the custom error.
The second way is to make use of a registry key provided by IIS 6.0. This registry key makes sure IIS 6.0 does not check the metadata during the execution of the custom error and therefore allowing this to work.
See the article for information on the registry key fix.
It may also mean that you are using something along the lines of Server.Transfer to a page that is in a different AppPool.
It could be because you're using different versions of ASP.NET for one or many apps in the pool.
Make sure all apps in the pool use the same version of ASP (e.g. ASP 2.0.50727)
If you just added a new app, try changing the app momentarily to a different version of ASP, then back to same version. I experienced an issue where the displayed version was correct, but under the hood, a different version was used!
Check your event log, under Application, to get more details about the error.
The message would be caused by your page server-side redirecting to a page served by another application pool. Such as for example, in your link, the error page.
I know this is an old thread, but I stumbled upon it and found a different solution. Here's what worked for me: Make sure your application handles .asmx files correctly
From IIS:
Right Click on your project > Properties > Configuration
If necessary, add the .asmx file extension that maps to the aspnet_isapi.dll
Limit to: "GET,HEAD,POST,DEBUG" and restart.
Because I can't comment on vcsjones's answer, I'll add it down here. The DWORD value IgnoreAppPoolForCustomErrors needs to be set under HKLM\SYSTEM\CurrentControlSet\Services\W3SVC\ Parameters vs HKLM\SYSTEM\CurrentControlSet\Services\W3SVC referenced in that technet article. Set it to 1 and do an iisreset and you're good to go.
Source Blog Post
In my particular case, I received this error while trying to serve a content (non ASP.NET) website while it was an Application. Right-Clicking the virtual folder and removing the application fixed it for me.
In my case the application used the application pool that didn't exist. I have no idea how it's happened.
I've built a web part and after several deployments to a specific site, SharePoint suddenly won't give the option to deploy to a specifi site, a message is immediatelly displayed that the solution is deplyed globally.
I don't know what I did to cause this. I've been useing stsadmn -o addsolution method, except once when when I tried to just run the Setup.exe file.
Anyone has any idea why is it happenning and how to correct this.
Thanks,
EJM
First make sure to retract the solution (with stsadm), if it doesn't work, use -force/-override, and then delete with the same.
Than try to do it again, and it should work.