Click here to Skip to main content
15,998,003 members
Please Sign up or sign in to vote.
0.00/5 (No votes)
See more:
Dear All,
I migrated my web application to windows server 2008. Then crystal report in classic asp page is not working.

My previous versions

windows server 2003,
crystal report 11
.net 2.0

current versions

windows server 2008 64bit,
crystal report XI r2.
.net 2.0.

I am calling crystal report from classic asp page.

Server.Create Object("CrystalDecisions.Application.115"); getting error at this line.
I Googled and tried all work around. But not is working.

Is it possible to call crystal report from asp page in server 2008 64 bit?


Please help me.


OP Comment:
This is the error:
Error Occurred creating Report Object: 006~ASP 0177~Server.CreateObject Failed~800401f3
Posted
Updated 8-Oct-11 0:03am
v2
Comments
André Kraak 6-Oct-11 17:13pm    
Please specify the error message you are getting.

If you wish to change your question use the Improve Question button.
telme 8-Oct-11 5:58am    
This is the error:

Error Occurred creating Report Object: 006~ASP 0177~Server.CreateObject Failed~800401f3

1 solution

Why do I get 800401F3 / 800A01AD errors?
This error is usually associated with trying to create an instance of a COM object using a ProgID that is not actually registered on the machine. The error message might be one of the following:

Server object error 'ASP 0177 : 800401f3'
Server.CreateObject Failed
/<file>.asp, line <line>
Invalid class string

Server object error 'ASP 0177 : 800a01f3'
Server.CreateObject Failed
/<file>.asp, line <line>
Invalid class string

Microsoft VBScript runtime (0x800A01AD)
ActiveX component can't create object: <progid>
/<file>.asp, line <line>

Common causes for this are:

forgetting to register the object using regsvr32;
fat-fingering the ProgID (e.g. "CDNOTS.NewMial");
not realizing that the object is not actually installed;
corrupted MDAC (see Article #2121;
using an MSWC or IIS sample component that is not installed (see KB #249290 for more info).

See Article #2135 for information on determining if a COM object is installed on your server.

If you are getting the following error:

Server object error 'ASP 0177 : 80080005'
Server.CreateObject Failed
/<file>.asp, line <line>
Server execution failed

See KB #241057 for information on setting your MTS package identity appropriately.

If you are using Index Server, and this error occurs on the following line:

Set something = Server.CreateObject("IXSSO.Query")

Then try the following, in this order:

Make sure session state is enabled
Stop Index Service, empty the catalog.wci folder, restart the Index service
upgrade to version 3.0
uninstall / reinstall Index Server
 
Share this answer
 
v2

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)



CodeProject, 20 Bay Street, 11th Floor Toronto, Ontario, Canada M5J 2N8 +1 (416) 849-8900