WAVE Management 4.0: ADODB Connection error

[tofs]

We sometimes encounter the following error when trying to log on to the WAVE Management system:

ADODB.Connection error ‘800a0e78’
Operation is not allowed when the object is closed.
/wave/./_include/system.ssi, line 2493

The system is using an Access DB and is running the following software versions:
Windows Server 2003 R2 version 5.2 build 3790 SP 2
Microsoft Access Driver 4.00.6305.00
WAVE 4.0 Management Server

After this error occurs we are not able to log on to the WAVE Management before the IIS is restarted.

We do not know how to reproduce the error as is seams to occur at random.

Have anyone seen this error before or know how to resolve this problem?

[jspeaker]

@tofs: I'm looking into this issue to determine the cause. In the post you stated that the error occurs when logging in, but looking at the screenshot it appears that the error occurs on the Users page (user_mgt.asp). I appreciate the detailed error information, which gives me some idea of what might be going on, thanks! If you could also reply here with the steps to reproduce that would help me a good deal - I understand it occurs occasionally/sporadically, but the steps will still help me, e.g. 1) login to management server [with or without administrator account] 2) navigate to page name 3) etc.

Thanks in advance.

Cheers
Jim

[tofs]

Yes in this case it seams that the error has occurred while being on the user page. The session however had timed out and thus redirecting the browser to the login page. Closing the browser and reconnecting to the management will result in the same error on the login page.

We always log on to the management system as an administrator.

I have asked everyone in our team to inform me if the error reappeared, but as for now we have not seen it yet. We will soon start reinstalling the system so this might provoke the error as the management system will be exercised a lot more than it does now. I will keep you posted if we find anything.

[jspeaker]

Thanks tofs. I think that the error you are describing may be indicative of a condition that might occur through extensive use of the management server, as you have suggested, rather than it being a time based anomaly. Will appreciate any additional information you might come upon, even empirical information. I have subscribed to this thread and will stay tuned in.

Thanks again.
Jim

[tofs]

We encountered the error again.

We have reinstalled the entire machine with the same configuration as before, except that we this time installed WAVE Management 4.5 instead of 4.0.

The guy who discovered the error told me that the browser was on the user configuration page when he got to the machine. It had most likely been on that page from the day before, and thus the session had properly timed-out.

Anyway he closed the browser without trying to navigate on the page. He then reconnected to the WAVE Management page in a new browser, where he was presented with the login page as expected. After he entered the credentials for the administrator account he was presented with the error as seen in the attachment.

The error did not occur at the same position in the code as the previous error I reported, but seems to relate the same object oDB being closed.

To recover from the error we restarted the application pool on the IIS.

[jspeaker]

@tofs: Thanks for the additional screenshot and the followup info.

I have opened a defect and included all of the information that you provided so we can get this into the triage process. For now, I'm glad to hear you have a workaround (the app pool restart or iisreset), although I must say I feel your pain as I know it's not optimal by any means.

I'll follow up again on this thread when I know more.

Cheers
Jim

[Sagady]

Ive recieved an error from a media server when trying to update its configuration:
"Failed to notify server ERR: cannot open server connection"
Any ideas?