I have ASP Pages hosted on IIS 5.1 that uses the COM DLL (VB).
I am browsing the ASP page and it is giving me an Server.CreateObject error.
I registered and Unregsitered my COM components. I registered it again.
I am trying to figure out how IIS does the mapping for the COM DLL and
the reason for the error messages.
It would help if you gave us the exact error message that you are receiving. In the meantime check this out.
Related
I am a system admin tasked with migrating Classic ASP based web application from Windows Server 2003 (IIS 6) to Windows Server 2008 r2 (IIS 7.5)
The application is very old written in around 2002-03 and the concerned developer people are not around anymore to let me know anything related to this Web Application.
After lot of trial and error, I have been able to get the Web Application running on 2008 r2.
While navigating through application, I am getting various errors which on further investigation I understood are related to DLLs which the Web Application is invoking.
My issue is, I don't know what all DLLs are used/invoked on the source server, which I need to copy & register on the new server.
I tried to use DependancyWalker but I am not able to find a way to use this tool for Web Application.
I would really appreciate this community's help in this regard.
I found out a simple way of finding the DLLs which are specific to my Web Application.
I got a small freeware utility called as RegDLLView from Nirsoft.net which lists all the DLLs which are registered with the Server with File Paths, Description, Company name, etc details.
I found out all the DLLs which my Web Application is invoking by checking the company name and paths of all the DLLs which were listed.
Now I just have to copy these DLLs to my new server and register these on the new system.
It's not rocket science.
When you find a COM component dependancy you can use the ProgId to identify and locate the DLL which is registered in the Windows Registry.
The only DLL dependancies come from COM component DLLs and these can only be invoke in Classic ASP / VBScipt with the
Server.CreateObject("ProgId")
and
CreateObject("ProgId")
respectively.
Wrote about this extensively here
Error ASP 0177: 8007007e Server.CreateObject fails for COM DLL
I have one server with IIS 5.0 running an ASP application. I changed the ASP application from Windows Server 2003 to Windows Server 2012, so I've installed IIS 8.5 and I've activated the ASP extension. It's ok, but I have a problem.
I have one extension which is named Gestion.dll, When I try to access the URL, I found this error:
This Object has a ProgID no valid.
I don't know how I can add the DLL extension to solve it. I have tried to add DLL with a module in the IIS 8.5 administrator, but it isn't running.
I have just started to debug a Classic ASP website. The old development environment was running in a VM machine on Windows Server 2003.
I have created a new Windows Server 2003 R2 server and have transferred the website.
The site also uses 11 ActiveX DLL's written in VB 6.
I have moved them over and used regsvr32 on all of the DLL's to register them and all appears well.
When I try and view the web page however I get the Error:
MX error '800a01ad'
ActiveX component can't create object.
/includes/somefile.asp, line 16
If I create a basic asp page, the page is served from both the root of the website and the virtual directory /includes fine.
Thanks
Some other VB6 activeX dependencies were discovered. Registered them, now working sweet.
I need to do some work on an old ASP Classic site, so I’m trying to host it on my IIS, but when I try load a page I get:
An error occurred on the server when processing the URL. Please contact the system administrator.
If you are the system administrator please click here to find out more about this error.
When I follow the link, it takes me to a Microsoft site and talks about running ASP Classic on IIS 7, but none of the pages help and nothing I found on Google will get it to work. I have all the elements under turn Windows features on and off - IIS - WWW services - app dev features.
This was bugging me earlier today and it turned out I had an error in my script.
This assumes you have installed the ASP/ISAPI extensions via the Control Panel's "Add/Remove Windows Features."
By default, errors will not be sent to the browser. To enable sending errors to the browser, go to the site in your IIS manager. Double click the ASP icon and expand "Debugging Properties." Set "Send Errors to Browser" to True.
I had this same problem and it turns out you need to set application pool to classic .net for it to work.
I have a Classic ASP aplication and now I installed that on my new PC with Windows7 64bit and IIS 7.5. The problem is that when the app tries to open de dabase, I have this error:
Error HTTP 404.0 - Not Found
I tried to open the database from this path and it works correctly. The fact is that I have my asp aplicacion on inetpub\wwwroot directory, but the access database is on C:\ProgramData\MyApp\bbdd.mdb it would be something with permisions? I added a IUSR_XXX user but it is not working too
any help or clue?
thanks in advance
In IIS 7.0 and 7.5, the classic version of ASP is not installed by default. Because of this, you might see HTTP 404 errors when you try to browse to an ASP page on your server, or you might see the source code for your ASP page displayed in your browser window.
Both of these error conditions are created when configuration settings that are used to define the environment for classic ASP are not installed.
Click Start, and then click Control Panel.
In Control Panel, click Programs and Features, and then click Turn Windows Features on or off.
Expand Internet Information Services, then World Wide Web Services, then Application Development Features.
Select ASP, and then click OK.
Classic ASP Not Installed by Default on IIS 7.0 and IIS 7.5