| Author |
 Topic Search  Topic Options
|
WebWiz-Bruce 
Admin Group
Web Wiz Developer
Joined: 03 September 2001
Location: Bournemouth
Status: Offline
Points: 9844
|
 Post Options
 Thanks(0)
 Quote  Reply
 Posted: 18 September 2006 at 12:18pm |
|
I can't remember offhand as I don't have Enterprise Manager but if you look through the settings, usually under something like properties for the database, you should find a way to increase the timeout for the database.
Also check that the SQL Server you are using to update the database has permissions to create and alter tables, moving this user to DBO group in SQL Server should do this. (DBO stands for Database Owner)
|
|
|
 |
CinemaemCena
Groupie
Joined: 05 February 2006
Status: Offline
Points: 46
|
Post Options
Thanks(0)
Quote Reply
Posted: 18 September 2006 at 12:39pm |
Well, borg, I'm stuck. When I checked the timeout value was set to "Wait indefinetely". The dabase HAS permissions to create and alter tables.
But the upgrading process takes about 100 seconds and, when the final screen appears, everything is right BUT the stage 2, where the Time Out message regarding tblThreads appears.
I guess that's it for me, huh? :(
|
|
WebWiz-Bruce
Admin Group
Web Wiz Developer
Joined: 03 September 2001
Location: Bournemouth
Status: Offline
Points: 9844
|
Post Options
Thanks(0)
Quote Reply
Posted: 18 September 2006 at 1:26pm |
|
The only thing you can do then, as it is only the the tblThread table that there is a problem, is have a look in the version history file and manually add the new fields to the table.
Luckily the only changes were to add towo new fields which I have listed below:-
Changes to tblThread
New fields:-
1. Hide - data type = true/false - default value = false
2. File_uploads - data type = text 255 characters
For the first one in SQL server it needs to be set to binary and have the default value of 0 as SQL Sever doesn't have a true/false datatype.
|
|
|
|
CinemaemCena
Groupie
Joined: 05 February 2006
Status: Offline
Points: 46
|
Post Options
Thanks(0)
Quote Reply
Posted: 18 September 2006 at 6:49pm |
Borg, do you recommend I do this before or after running the upgrade?
And what if there's some other table that should've been created but wasn't because of the tblThread time out? I mean... after doing the tblThread, the program would upgrade other tables, wouldn'it?
|
|
WebWiz-Bruce
Admin Group
Web Wiz Developer
Joined: 03 September 2001
Location: Bournemouth
Status: Offline
Points: 9844
|
Post Options
Thanks(0)
Quote Reply
Posted: 19 September 2006 at 10:55am |
|
Do this after the upgrade.
As the only error message is a timeout on that particular table the other tables should have been created and updated successfully.
|
|
|
|
CinemaemCena
Groupie
Joined: 05 February 2006
Status: Offline
Points: 46
|
Post Options
Thanks(0)
Quote Reply
Posted: 21 September 2006 at 2:18am |
Ok, I did everything like you said. But now, when I click on any topic of the forum, I get the message: Microsoft VBScript runtime error '800a005e'
Invalid use of Null: 'CBool'
/forum/forum_posts.asp, line 779
|
|
WebWiz-Bruce
Admin Group
Web Wiz Developer
Joined: 03 September 2001
Location: Bournemouth
Status: Offline
Points: 9844
|
Post Options
Thanks(0)
Quote Reply
Posted: 21 September 2006 at 7:40am |
|
It maybe then that the other new fields are also not created.
You may need to go through the version history file and create all fields manually if you can not findout why your database is timing out when alterations are applied to the tables.
I still think it would be a permissions issue and that the user you are logging into the SQL Server with doesn't have sufficient permissions to alter tables. Try logging in with the 'sa' account for doing the database upgrade.
Also a SQL Server site may be able to give you better advice on dealing with issues with SQL Server as it can be quite a complex database system.
|
|
|
|
jeffdaro
Groupie
Joined: 15 April 2005
Status: Offline
Points: 171
|
Post Options
Thanks(0)
Quote Reply
Posted: 21 September 2006 at 1:45pm |
|
Just to add to the mix...our install went fine, but timeouts seem to be a daily issue with our forums. I've been blaming it on my ISP. Just my 2 cents...
|
|
