COM / ASP problem

Gman

Gman

Gman

Soldato
Joined
18 Oct 2002
Posts
4,925
Location
Yorkshire
Well been working on an application involving asp and COM's which has been working fine. On Friday I was messing around with a print service in .Net and was having problems with it and eventually got it in a state where the service for it was stuck in a 'starting' state.

To fix this I tried a few things like uninstalling .net 1.1 (which it uses) and reinstalling etc. reinstalling MSDTC etc which didn't seem to fix the problem.

Later when I gave up and went back to the ASP / COM web application its no longer working :( all i'm getting is an error message with the following.

MyUtility (0x8007000E)
System Error &H80004005 (-2147467259).
/test/again.asp, line 5

Any ideas what i've screwed up ? been going through a few sites and found the odd thing but nothing relating to ASP/COM issues on this. the only ones that do mention this don't finish with a solution :(

Little update:
It appears that its a problem with coms that try and talk to the database, created a simple one which just returns a string and that worked ok.
 
Last edited:
0x8007000E is out of memory, which you sometimes see when DCOM can't retrieve the error from a remote object. Is that what you're doing?

&H80004005 is access denied. Could be anything really.

Anything in the event log?
 
Nope not a thing the event log's empty both for the application and system.

i'm thinking some permissions might have got reset when I re-installed MSDTC. Will have a play but right clicking on the com's seem to have the right security info and user access as before.
 
I'd be surprised if you were even using MSDTC. What identity is the web site running under? You need to check the launch permissions allow that user to launch the COM object
 
sorted it only took the best part of 4 hours going through website after website over the weekend.

In the end it was the MSDTC, was the security configuration which wasn't allowing any transactions. so they must have got reset when I uninstalled them before :( oh well live a learn.
 
resurrecting this thread again as i'm having te same problem.

This time it seems that the same error message is occurring if there's a problem in the COM. i.e. in the COM I just entered the wrong data type in a stored procedure call and I got the above error message. Before when I did this I'd get an decent error message and an entry in the event log but this time nothing.

Any ideas what I can do to get my error messages back for the COM's?

UMMMM interesting, It seems to fall over not not because of the COm error but because the COm tries to write to the event log. Just entered an App.Logevent("") to echo a string to the event log and it falls over.

Any ideas ?


Update:
Sorted it, seems i'd clocked up one too many event log entries and it was resulting in a mem problem. Dam you Microsoft it aint to dificult to say Error: Event Log Full.
 
Last edited:
You must log in or register to reply here.
Back
Top Bottom