| Author |
 Topic  |
|
|
ryanjt
Starting Member
USA
20 Posts |
 Posted - 26 June 2002 : 15:22:13
|
Hi all,
I would like to upgrade to the latest version (3.3.05) from 3.1 SR2. Are there any problems I should be aware of? I am told we tried upgrading to 3.3.03 back in march and encountered some VBScript errors that were a bit to complicated for us to get around at the time (without making a big effort). I've read the installation instructions in the readme and didn't notice any sort of troubleshooting section. Any thoughts?
Moved by FrutZle from Help: General/Current Version
Reason: SQL related problem
Edited by - FrutZle on 02 July 2002 18:03:19 |
|
|
Roland
Advanced Member
Netherlands
9335 Posts |
Posted - 26 June 2002 : 15:23:40
|
If you follow the instructions, it should all go just as planned. Just make a backup of your current folder (including the database, if possible) before you upgade.
Roland
http://www.frutzle.com
Snitz Exchange | Do's and Dont's |
 |
|
|
ryanjt
Starting Member
USA
20 Posts |
Posted - 26 June 2002 : 16:21:45
|
I followed the instructions in the readme file to use our current SQL Server database. I then had another IT person check my work. (He said it looked good.) I then went to setup.asp on our server (through a browser) and tried performing the upgrade. Unforutnately I was faced with the following scary list of critcal errors (as well as 26 non-critical errors!):
quote:
80040E37 in statement [ALTER TABLE FORUM_CONFIG ADD C_STRAUTOLOGON SMALLINT NULL CONSTRAINT FORUM_SnitzC1015 DEFAULT 0 ; ] while trying to add C_STRAUTOLOGON to the CONFIG table
80040E37 in statement [ALTER TABLE FORUM_CONFIG ADD C_STRNTGROUPS SMALLINT NULL CONSTRAINT FORUM_SnitzC1016 DEFAULT 0 ; ] while trying to add C_STRNTGROUPS to the CONFIG table
80040E37 while trying to add default values to the CONFIG table
80040E37 while trying to add default values to the CONFIG table
80040E37 while trying to tranfer the existing config values to the new table
It may be worth noting that additional columns have been added to our SQL database to connect the SNITZ forum with our own website membership system. Would these new columns (even though they were added at the end of the database) have a negative effect on the upgrade process?
|
|
|
|
Roland
Advanced Member
Netherlands
9335 Posts |
Posted - 26 June 2002 : 16:34:56
|
Upgrading and installing on an SQL server (be it MS Sql or MySql) should be done with setup.asp?RC=5
If you use that, the necessary tables will be created/updated for you. Did you use setup.asp?RC=5 or just setup.asp?
Roland
http://www.frutzle.com
Snitz Exchange | Do's and Dont's |
|
|
|
ryanjt
Starting Member
USA
20 Posts |
Posted - 02 July 2002 : 17:17:10
|
I did try setup.asp?RC=5, but the page I was taken to seems to allow installations only, not upgrades. It wouldn't let me choose the previous version. Nevertheless, I plowed onwards. Here's what I did:
- On the page it took me to, I enter a User ID and password which possess admin rights. It gives me a bunch of errors, most of which are of the form:
[Microsoft][ODBC SQL Server Driver][SQL Server]There is already an object named 'FORUM_CATEGORY' in the database.
I suppose these errors make sense since our database needs to be upgraded, not installed. Anyways...
- I then click on Click Here to Check the Database and it gives me a page that says the setup has been completed!? This was a suprise.
- Being a little suspicious, I then click on Upgrade the Database.
- I then select Snitz Forums 2000 V3.1 Service Release 2 from the list of versions from which to upgrade.
- I then enter an SQL server User ID and password and click Continue.
It then gives me those critical errors I mentioned in my previous post, plus 26 noncritical errors.
So now what? I did notice that the Upgrade page has RC=3. We tried that page first at one point and it failed as well.
Edited by - ryanjt on 02 July 2002 17:40:03
Edited by - ryanjt on 02 July 2002 17:41:02 |
|
|
|
Roland
Advanced Member
Netherlands
9335 Posts |
Posted - 02 July 2002 : 18:02:10
|
Ruirib, I see what you meant... Thanks for the e-mail 
I'm not too knowledgeable with SQL after only having set up one set of forums on it and that was a clean install. I  guessed that you should use setup.asp?rc=5 for upgrading too, but as Ruirib pointed out in an e-mail to me, that's not the case.
So in short, I can't help you with this. Ruirib probably can.
Since this is an SQL related question I will move this topic to the SQL forum where you will most likely get better help. Sorry.
Roland
http://www.frutzle.com
Snitz Exchange | Do's and Dont's |
|
|
|
ruirib
Snitz Forums Admin
Portugal
26364 Posts |
Posted - 02 July 2002 : 18:14:37
|
Ok, Roland.
Ryanjt, try to run setup.asp without anything else, ok? Just setup.asp.
-------------------------------------------------
Installation Guide | Do's and Dont's | MODs
Edited by - ruirib on 02 July 2002 18:15:39 |
|
|
|
ryanjt
Starting Member
USA
20 Posts |
Posted - 02 July 2002 : 18:40:18
|
OK, but I did try that once already. That's the post which lists the "Critical errors". I'll let you know what happens in the second go-around as soon as I can.
Thanks!
|
|
|
|
ruirib
Snitz Forums Admin
Portugal
26364 Posts |
Posted - 02 July 2002 : 18:48:55
|
I've experienced upgrades where all things went well at first, others where I made it only on third or fourth attempt. Can't figure out why. Did the same every time.
-------------------------------------------------
Installation Guide | Do's and Dont's | MODs |
|
|
|
ryanjt
Starting Member
USA
20 Posts |
Posted - 03 July 2002 : 14:51:42
|
OK, I tried running setup.asp (no parameters) several times as follows and here's what happened:
- First, I updated config.asp so that the following lines were uncommented:
strDBType = "sqlserver"
strConnString = "driver={SQL Server};server=OurServer;uid=;pwd=;database=community" '## MS SQL Server 6.x/7.x/2000 (ODBC connection)
Note: I have changed the server name and omitted uid and pwd for security reasons, but they are included in the actual file.
- I then tried running setup.asp
At this point it says there was an error as follows:
---------------------------------------------------------
There has been an error !!
The database could not be opened !!
Check your config.asp file and set the
strConnString so it points to the database.
Also check if strDBType is set to the right databasetype.
Code : 80004005
---------------------------------------------------------
- I check config.asp and end up changing it so that the uid and pwd
used have admin priveleges since this is the only thing that seems wrong (I guess).
- Click the "Click Here to Retry" link. It then says:
---------------------------------------------------------
You need to logon first.
To upgrade the database you need to be logged on as a
forum administrator.
---------------------------------------------------------
- I entered two different user ids and passwords (that
I know have admin priveleges for the forum). Both
resulted in the following:
---------------------------------------------------------
Microsoft OLE DB Provider for ODBC Drivers error '80040e37'
[Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name 'FORUM_MEMBERS'.
/forum/setup_login.asp, line 80
---------------------------------------------------------
So, this doesn't seem to be working. I did all this in
IE 6.0. When I try this in netscape communicator 4.7,
step 4 only shows the text "You need to logon first."
It does not give me any opportunity to logon for some
reason. Perhaps the setup program does not work in this
version of Netscape.
Any ideas?
quote:
I've experienced upgrades where all things went well at first, others where I made it only on third or fourth attempt. Can't figure out why. Did the same every time.
|
|
|
|
ruirib
Snitz Forums Admin
Portugal
26364 Posts |
Posted - 03 July 2002 : 19:06:36
|
Much more important than the user you specify in the connection string is the user name and password you need to specify at the upgrade options setup page. Those need to be from a user with permissions to create and change tables in the database. You could even use the sa user data here.
-------------------------------------------------
Installation Guide | Do's and Dont's | MODs |
|
|
|
Massimo
Junior Member
Italy
125 Posts |
|
|
ryanjt
Starting Member
USA
20 Posts |
Posted - 09 July 2002 : 10:59:10
|
We used sa in many of our attempts. Any other suggestions?
quote:
Much more important than the user you specify in the connection string is the user name and password you need to specify at the upgrade options setup page. Those need to be from a user with permissions to create and change tables in the database. You could even use the sa user data here.
-------------------------------------------------
Installation Guide | Do's and Dont's | MODs
|
|
|
|
ruirib
Snitz Forums Admin
Portugal
26364 Posts |
Posted - 09 July 2002 : 12:11:33
|
Make sure the user you are specifying has the dbowner role. Maybe even check the database to see who's registered as dbowner and use that login/user data to try upgrade the database.
-------------------------------------------------
Installation Guide | Do's and Dont's | MODs |
|
|
|
ryanjt
Starting Member
USA
20 Posts |
Posted - 16 July 2002 : 12:21:37
|
I passed this upgrade problem along to a colleague who is a bit more qualified to handle the database end of things. He discovered some sort of permissions problem with it. After fixing this the upgrade went smoothly. Thanks for all the help!
quote:
Make sure the user you are specifying has the dbowner role. Maybe even check the database to see who's registered as dbowner and use that login/user data to try upgrade the database.
-------------------------------------------------
Installation Guide | Do's and Dont's | MODs
|
|
|
|
ruirib
Snitz Forums Admin
Portugal
26364 Posts |
|
| |
Topic |
|
Topic Locked
.