Web Wiz Forums - Moved hosts now a lot of errors v6.34

Print Page | Close Window

Moved hosts now a lot of errors v6.34

Printed From: Web Wiz Forums
Category: Web Wiz Web App Support Forums
Forum Name: Web Wiz Forums
Forum Description: Support forum for Web Wiz Forums application.
URL: https://forums.webwiz.net/forum_posts.asp?TID=1341
Printed Date: 30 March 2026 at 2:26pm
Software Version: Web Wiz Forums 12.08 - https://www.webwizforums.com

Topic: Moved hosts now a lot of errors v6.34

Posted By: ChampioN
Subject: Moved hosts now a lot of errors v6.34
Date Posted: 25 March 2003 at 3:30pm

I just moved webhosts and I am using version 6.34, the sql version. It was working flawlessly at my other host but I am having trouble getting it to work at my new host. When I try to post a message I get this error:

ADODB.Recordset error '800a0cb3'

Current Recordset does not support updating. This may be a limitation of the provider, or of the selected locktype.

/forum/post_message.asp, line 322

When I click on the active users link at the bottom of the main page, I get this error.

Microsoft VBScript runtime error '800a005e'

Invalid use of Null: 'CDate'

/forum/active_users.asp, line 198

The webhosting company is trying to figure out the problem but they have been looking at it for 24 hours now and can't solve it. Does anyone know what the problem could be? please let me know.

Replies:

Posted By: WebWiz-Bruce
Date Posted: 25 March 2003 at 3:35pm

Make sure they are running the latest ODBC drivers.

The CDate bug and a solution is listed in the documentation that comes with the forum. You may need to change the LCID locale.

-------------
https://www.webwiz.net/web-wiz-forums/forum-hosting.htm" rel="nofollow - Web Wiz Forums Hosting
https://www.webwiz.net/web-hosting/windows-web-hosting.htm" rel="nofollow - ASP.NET Web Hosting

Posted By: ChampioN
Date Posted: 25 March 2003 at 6:58pm

They checked their drivers and said they are running the latest. They are saying that it could be coding problems which I called bs on them over. I told them that I never had a problem at the other webhost and the problem only occured after we moved to them. Any ideas?