| Author |
 Topic  |
|
|
Curmudgeon
Starting Member
17 Posts |
 Posted - 20 January 2006 : 17:40:34
|
This problem is happening on a project to migrate a working old version Snitz forum on system A, updating and converting on system B, and final deployment on system C.
The error:
Microsoft OLE DB Provider for SQL Server error '80040e37'
Invalid object name 'FORUM_TOTALS'.
/Default.asp, line 90
This error occurs on system C, which has current code FTP’d from system B. The tables on C were imported from the database on B. The database on C has a name which is different from that on B. Users on C are different than those on B
I have checked the table on system C and it is there. When I change permissions on the table, the error changes to “page not found”.
The original database is v3.3.03 on system A. The upgrade to v3.4.05 was done on system B after doing a full restore of the system A database (called snitzforum) on B. Everything is working fine on B.
Final deployment will be on system C, using a virtual directory for the connection string. (The owner of system C insists on using the v-dir for security reasons.) The v-dir is working properly on system B, and appears to be ok on C.
I have searched Snitz forum’s postings and found the one on 1-Nov-05 called “Godaddy”. None of the postings on that thread have been of any help in this situation.
Suggestions, please!! |
|
|
ruirib
Snitz Forums Admin
Portugal
26364 Posts |
|
|
Curmudgeon
Starting Member
17 Posts |
Posted - 21 January 2006 : 01:27:17
|
quote:
Originally posted by ruirib
Check the table owner for FORUM_TOTALS. Quite likely the user being specified in the connection string is not the table owner.
Once again - Thanks for the great support! That fixed the problem.
But now, there is a new one: I can't add a new topic on system C. The error message is:
Microsoft OLE DB Provider for SQL Server error '80040e2f'
Cannot insert the value NULL into column 'TOPIC_ID', table 'C_snitzforum.C_snitzforum.FORUM_TOPICS'; column does not allow nulls. INSERT fails.
/post_info.asp, line 892
The test/development system (B) works fine. I don't see any ownership issues, and the table definition is the same on both system B and system C. I would expect a column like _ID to not allow null values - and that is what the table def says.
TIA |
 |
|
|
ruirib
Snitz Forums Admin
Portugal
26364 Posts |
Posted - 21 January 2006 : 07:22:19
|
You didn't create the tables using setup.asp, did you? Maybe you used DTS and chose to transfer data instead of copying objects? Either copy the objects in DTS, or create the tables using setup.asp and then DTS the data (making sure that you with the options to enable identity insert for each table and to delete existing data.
The procedure is pretty similar to an Access to SQL Server migration, as explained here:
http://forum.snitz.com/forum/topic.asp?TOPIC_ID=31144
Right now, you could edit the column in Enterprise Manage and make it an identiy column. If you have the option to redo all the tables per the previous explained method, I'd recommend it, since it's likely that you'll have similar problems with other tables. |
Snitz 3.4 Readme | Like the support? Support Snitz too |
|
|
|
Curmudgeon
Starting Member
17 Posts |
Posted - 26 January 2006 : 04:02:24
|
quote:
Originally posted by ruirib
You didn't create the tables using setup.asp, did you? Maybe you used DTS and chose to transfer data instead of copying objects? Either copy the objects in DTS, or create the tables using setup.asp and then DTS the data (making sure that you with the options to enable identity insert for each table and to delete existing data.
The procedure is pretty similar to an Access to SQL Server migration, as explained here:
http://forum.snitz.com/forum/topic.asp?TOPIC_ID=31144
Right now, you could edit the column in Enterprise Manage and make it an identiy column. If you have the option to redo all the tables per the previous explained method, I'd recommend it, since it's likely that you'll have similar problems with other tables.
A big thank you!!
Now, a related question: Will this procedure work as is, for moving data from one v3.4.05 database to another v3.4.05 database?
TIA |
|
|
|
ruirib
Snitz Forums Admin
Portugal
26364 Posts |
|
|
Curmudgeon
Starting Member
17 Posts |
Posted - 26 January 2006 : 04:40:53
|
quote:
Originally posted by ruirib
Yes, the same procedure will hold. Create the database first, using setup.asp and any mod dbs files and then transfer the data as explained.
One more detail - Two questions
1. In the access example you refer to, you call for running setup.asp with a qualifier as so: "setup.asp?RC=5" Does that qualifier apply to this situation also?
2. Is this or other qualifiers documented someplace?
TIA |
|
|
|
ruirib
Snitz Forums Admin
Portugal
26364 Posts |
Posted - 26 January 2006 : 04:43:31
|
Setup.asp?RC=5 was needed with Snitz 3.3.x to force table creation. With Snitz 3.4.x it is not needed, but it won't do any harm either.
The post was originally written for Snitz 3.3.x. |
Snitz 3.4 Readme | Like the support? Support Snitz too |
|
|
|
Curmudgeon
Starting Member
17 Posts |
Posted - 26 January 2006 : 04:54:10
|
quote:
Originally posted by ruirib
Setup.asp?RC=5 was needed with Snitz 3.3.x to force table creation. With Snitz 3.4.x it is not needed, but it won't do no harm either.
The post was originally written for Snitz 3.3.x.
Once again - Thanks for top quality support! |
|
|
|
ruirib
Snitz Forums Admin
Portugal
26364 Posts |
|
| |
Topic |
|
Topic Locked
