'Error Type:Server object, ASP 0177 (0x800AEA5F)800aea5f' Thread RSS Feed

Error Type:Server object, ASP 0177 (0x800AEA5F)800aea5f

Wed, 19 Dec 2007 04:38:20 -0700

I have used COM component for ASP WebPages to show pages. The old component

worked fine. When I added new procedure to the COM component, compiled and

registered it, I get the following error in end user machine:

Error Type:

Server object, ASP 0177 (0x800AEA5F)

800aea5f

In the development machine the component working fine. Any idea what is the

problem.

Re: Error Type:Server object, ASP 0177 (0x800AEA5F)800aea5f

Wed, 19 Dec 2007 21:24:37 -0700

Unregister the previous component,
regsvr32 /u yourcomponent.dll ' THE OLDER VERSION (Which you have in a backup)

Register your new component,
regsvr32 yourcomponent.dll ' THE NEW VERSION

And reboot the server machine.
Or at least reload the process of IIS.

Good luck!
Hackman

Re: Error Type:Server object, ASP 0177 (0x800AEA5F)800aea5f

Wed, 19 Dec 2007 22:49:54 -0700

hi,
i did the same. but, still it is giving the same error. if i run the website without registering the component, it is showing the same error with "Invalid class string" message.

Unregister the previous component,
: regsvr32 /u yourcomponent.dll ' THE OLDER VERSION (Which you have in
: a backup)
:
: Register your new component,
: regsvr32 yourcomponent.dll ' THE NEW VERSION
:
: And reboot the server machine.
: Or at least reload the process of IIS.
:
: Good luck!
: Hackman

Re: Error Type:Server object, ASP 0177 (0x800AEA5F)800aea5f

Thu, 20 Dec 2007 12:11:01 -0700

:o

This looks like the "Twilight Zone" for me !!!
Thats odd, but funny, kind of funny ... :)

http://www.google.com/search?q=ASP+0177+800AEA5F

You have 171 (more or less) answers to the
same question, but it looks like none of them
was useful.

That is a little bit scary. :)
You are in the unknown dimension.

The most interesting one for myself...
I quote:

Dar - 4/15/2005 12:00:00 AM

I've had this problem a couple of times now.
The error is just not recognised by Microsoft at all, so you're on your own.
http://www.developmentnow.com/g/60_2003_10_0_0_254236/Server-CreateObject-error.htm

This is what I would do in your case:

1. Take the older one and register properly on the server.
   Check if it still works.
2. Unregister the older one in the server and check in the
   "Registry" to remove everything about your component.
   Use search in the "Registry Editor".
3. Open the older project on VB on the development machine
   and ensure "Binary Compatibility".
4. Compile the new component.
5. Copy the component to the server and check security ACL.
   The user which the server is running on should have read
   access to your component .dll
6. Register properly the component on the server.
7. Shutdown (power-off) the server and restart.

Good luck!
Hackman

Re: Error Type:Server object, ASP 0177 (0x800AEA5F)800aea5f

Fri, 21 Dec 2007 02:12:56 -0700

hi,
now it is working fine. but, i have added some code in one DLL file which will check the SQL service status,if it is stopped,it will display a messagebox. now, how to display the messagebox which i have added in DLL file? also, can u provide the sample code for checking for sql service status? i am Visual Basic 6.0.

Re: Error Type:Server object, ASP 0177 (0x800AEA5F)800aea5f

Fri, 21 Dec 2007 13:35:08 -0700

Would be great for all those people having the same problem than you, if you share how did you fix the problem, in a blog or something.

To check the SQL Service status could be easy handled by opening a connection, and catching the "On Error" if the connection can't be opened.

But displaying a "MessageBox" from your DLL running inside "Internet Information Server" IIS would be lot of trouble, if the MessageBox can't be displayed could shutdown the whole server. For you convenience ... nobody does that. IIS runs like a Windows Service, and Windows Services should not relay on user interaction.

You better find another logging method. If you want monitor SQL Server status and get alerts, there are tools in SQL 2000 to do exactly that. Your application shouldn't monitor the status unless your applications is a monitoring application.

App.LogEvent() to log events to "Event Viewer".

Good luck!
Hackman