We've got a problem when trying to upload a picture to a IIS application after we've migrated from Windows Server 2003 & IIS 6.0 to Windows Server 2008 R2 & IIS 7.5 a couple of days ago.
You are allowed to choose a picture, but as soon as you click on the "Send"-button to perform the upload you're introduced to the following error message:
"
Server object error 'ASP 0177 : 800401f3'
Server.CreateObject Failed
/****/****/photouploadproc.asp, line 15
800401f3
"
In this code, the program uses a proprietary third library called w3upload.dll.
We tried to migrate the dll from the old IIS to the new one and give the access rights.
It's still not working.
We're close to the edge of insanity, so please, if anybody has any hints or tips we've will gladly accept it :)
I'd imagine your running in a 64bit application pool in IIS? you may need to set IIS to allow 32bit applications (dll's, com objects & assemblies etc).
Also, have you registered the dll using regsvr32?
Related
While migrating a Classic asp project from windows server 2003(IIS 6) to windows server 2008 R2(IIS 7.5), the Menu is not getting loaded, when checked in the log. It displays the below error.
Menu.asp |107|ASP_0177_:_800401f3|Server.CreateObject_Failed
When checked the code, the line shows
Server.CreateObject("webCalendarv1.objCalandar")
Can some one please help me why im getting this error.
Server.CreateObject_Failed
This type of error usually means the component (DLL) you are trying to reference isn't installed on that server or your syntax is incorrect.
As you say that you've moved servers I would suggest that you check that the
webCalendarv1.objCalandar
component is installed/registered on your new server. Most likely you can move the relevant DLL file across and run;
Regsvr32.exe nameofthecomponent.dll
One thing you'll have to check is that you have the correct bit version of your component that matchs the bit version of your Windows Server OS. There is an option within IIS that allows use of 32bit components on a 64bit Windows Server for a specific App Pool.
We have a web application built with target framework as x86.
On Server 2008 (IIS 7/7.5) we are able to run the application without any issue (For 64 bit system we enable 32 bit application from app pool).
On 32 bit server 2003 - no issue.
On 64 bit server 2003 (SP2) - we are unable to load a dll:
Could not load file or assembly 'acPDFCreatorLib.Net' or one of its dependencies. An attempt was made to load a program with an incorrect format.
We know this error comes on 64 bit system when Enable 32bit application is set to false. So I tried the following:
Ran the script:
cscript %SYSTEMDRIVE%\inetpub\adminscripts\adsutil.vbs SET W3SVC/AppPools/Enable32bitAppOnWin64 1
The issue persisted.
%SYSTEMROOT%\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis.exe -ir
On running this the World Wide Web Publishing service stops.
On trying to restart we are getting the following error
ISAPI Filter 'C:\WINDOWS\microsoft.net\Framework\v2.0.50727\aspnet_filter.dll' could not be loaded due to a configuration problem. The current configuration only supports loading images built for a AMD64 processor architecture.
Any ideas?
Below worked for me regarding the issue "Could not load file or assembly 'acPDFCreatorLib.Net' or one of its dependencies. An attempt was made to load a program with an incorrect format."
Go to Application Pools => Select the AppPool you have created (Else Choose DefaultAppPool or ASP .Net v4.0)
Right click AppPool and Select Advanced Settings
Set Enable 32-bit Applications to True
Reset IIS and Check
The following fixed the issue for me:-
Right Click "Web Sites" and select property
Go to Services tab.
Uncheck - "Run WWW services in IIS 5.0 isolation mode".
After removing the selection from Run WWW Services...., I was able to start the service.
Hi we have configured IIS with helicon and webgate.
when I am accessing my site I am finding Following Error message on page
HTTP Error 500.0 - Internal Server Error
Calling LoadLibraryEx on ISAPI filter "C:\Appl\Softwares\Webgate\access\oblix\apps\webgate\bin\webgate.dll" failedror
Please help.
My configuration as my other environment where all the things are working.
Yesterday, while setting up a website on IIS 7 and Windows Server 2008, I loaded up the website in the browser and ended up getting the following error message:
Calling LoadLibraryEx on ISAPI filter C:\…isapi.dll failed
The path was to the isapi.dll file in C:\Program Files\etc and I was pretty sure everything was setup properly. After doing a bit of research on the topic, I figured out that since I’m running IIS 7 on a 64-bit version of Windows Server and my web application was 32-bit, I had to change a setting in the IIS configuration.
To fix this problem, all you have to do is open IIS7 and click on Application Pools.
Then right-click on the application pool for your website or the default application pool and go to the Advanced Settings tab. Make sure that Enable 32-bit applications is set to True.
That’s it! Now restart IIS and load up Internet Explorer again and your website should load fine.
I received the same error after installing .NET 1.1.
After uninstalling .NET 1.1 I still had the same error.
However, the error has gone immediately after I went to IIS Manager -> ISAPI filters and removed the only filter from here (it was ASP.NET_4.0.30319.0).
This error might be because of the following reasons. Those are:
webgate installation folder has restricted permissions. Give required permissions for the webgate installation and configuration folder for the IIS process which runs your website. (Had you run configuration script for webgate or just manually configured it?)
There may be other DLLs missing on which webgate is dependent. For example, VC++ runtime redistributables. (For 10g use 2005 version, for 11g use 2012 version).
Some internal files are missing for webgate. Try re-installing webgate and running config script.
We have a webapplication, made in ASP.NET 2.
This app runs without problems in IIS 6. When we upload it to an IIS 7 (Windows Server 2008 R2 Datacenter) it runs in IIS, but when we open the site in a browser we get this error:
Server Error
500 - Internal server error.
There is a problem with the resource you are looking for, and it cannot be displayed.
I would make sure that everything is set correctly in the ASP.NET tab, and also check under the Home Directory tab to make sure that the application has sufficient read/write and execute permissions.
The problem was that I nedded to add a feature to the server. After I added .NET Framework 3.5.1 Features it worked.
We have a couple of web apps built in Classic ASP which are currently running on Windows Server 2003 32 Bit and IIS 6.
We are trying to migrate this to a new server running Windows Server 2008 64 Bit with IIS 7. But we are finding it very difficult to make Classic ASP work on IIS 7 in a 64 Bit OS.
I got to a tage where running the following code:
<%
Response.Write "This is the new www5"
Response.End
%>
Gives us an error on Response.End
This is the new www5 error '8002801d'
/test.asp, line 4
I have enabled 32bit Applications, also registered a few times asp.dll running regsvr32.exe but no luck so far.
Tried restaring IIS, recycling the application pool after each config change but nothing.
Thanks in advance.
Federico
In the end it turned out to be a permission issue on the registry.
I googled a bit more and found that 8002801d error means than a library is not registered or not properly registered.
I used procmon to monitor the access to the registry and found out that a key under HKCR\TypeLib was getting access denied.
Then i tried to run regedt32 to add the permissions for the IIS USR to that key, but was getting access denied as well.
So I downloaded PSTOOLS and run the following command: psexec -s -i regedt32
That opened regedt32 without having any access denied popups and added the IIS USR to that key.
After doing this Classic ASP is working on IIS 7 Windows Server 2008 64 Bit.
Cheers,
Federico
Do this Step by Step:
Go to control panel
Windows features on/off
Tick this features:
3.a) Internet Information Service>Web management tools>IIS6 Management Compatibility
3.b) Internet Information Service>Web management tools>IIS Management Console
3.c) Internet Information Service>Worldwide web services>Application dev. features>ASP
3.d) Internet Information Service>Worldwide web services>Application dev. features>ISAPI Extentions
To solve this issue you should change the application pool to "classic asp" in IIS settings and also change the application 64bit to 32bit.