Quantcast
Channel: West Wind Message Board Messages
Viewing all articles
Browse latest Browse all 10393

Re: OLE Error 0x80030003

$
0
0
Re: OLE Error 0x80030003
Web Connection 5.0
Re: OLE Error 0x80030003
04/19/2012
12:36:31 PM
3HE0R106T Show this entire thread in new window
Gratar Image based on email address
From:
Michael Hogan
To:
Attachments:
None
Finally got around to looking at this. Turns out you use OWC for traffic charts by default (strangely, only when using SQL log tables). I don't like installing that kinda stuff on my web servers so it only reported a COM error when we tried looking at the log through the admin page. I commented out the graph portion of the wwmaint code - please consider removing it if you haven't already done so - or replacing it with something that doesn't depend on components like that, or detecting whether it's installed before using it.

Thanks

It sounds to me like you have an error in your error handler code. The error handler bonks and the request might go through - so the problem only occurs if there's an error in your app somewhere, so it's intermittent. Could be a corrupt file possibly or an invalid db structure on the server if it's the log.

I'd double check the error handling. Run the app locally in COM mode and forcibly cause some errors in code and see what happens.

+++ Rick ---



Getting it again - this time on a server using SQL for sessions and logs. Here are the details:

Error Message: OLE error code 0x80030003: Unknown COM status code.
Error Number: 1426
Running Method: getoutput
Current Code:
Current Code Line: 313
Exception Handled by: Wwmaint.OnError()

The Server Error Log displays fine, but the Server Hit Log generates this error. Tried re-loading servers - same error.

Thoughts?


Sounds like one of the servers in your pool of servers is corrupt? Restart the instances?

+++ Rick ---


When I "Show Web Connection Server Hit Log" from the administration page in 5.42, I get: "OLE Error 0x80030003: Unknown COM Status Code"

If I click 'Ignore', I get the log.

If I delete wwRequestLog, it works normally for awhile, but then it ultimately resumes it's evil dance. I'm operating in COM mode as interactive user for final testing.

Suggestions are welcomed...

Michael





Viewing all articles
Browse latest Browse all 10393

Trending Articles