If I understand you correctly, this is occurring at
Step 4 when you try to run the 7.0.01 upgrade installer against the
restored 5.01.02 database on a new machine? Support may have to look at the
installer in that case - keep in mind that the T### number assigned to any given
table except User and Group will be different from one install to the next. The
0.01 installers for ARS components and applications have been nothing but
trouble so far. I wonder if you would have better luck installing the ARS 7.0
upgrade to 5.01.02 first??? Also make sure that all of the db level permissions
had been updated on the restored 5.x environment and you could access that
system from User and Admin before running the upgrade
installer.
Christopher Strauss, Ph.D.
Remedy Database
Administrator
University of North Texas Computing Center
http://remedy.unt.edu/helpdesk/
From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Marquez Rankin
Sent: Wednesday, November 15, 2006 10:17 AM
To: arslist@ARSLIST.ORG
Subject: Re: Migration/Uprage from 5.01.02 to 7.01 (cant connect to Remedy with clients)
**
Thank you Mr. Strauss,
I did try this sequence and recieved the same upgrade error. But upon
viewing the SQL install log, it shows the following Errors regarding T373 which
I believe is 'AR System Email Mailbox Configuration'.
I have forwarded these results to Remedy Support.
Any course of action on these? At the database level I assume?
/* Tue Nov 14 17:56:57 2006 */ ALTER TABLE T373 ADD newencrypted102 varchar(255) NULL
/* Tue Nov 14 17:56:57 2006 */ *** ERROR *** Cannot find the object "T373" because it does not exist or you do not have permissions. (SQL Server 4902)
/* Tue Nov 14 17:56:57 2006 */ ROLLBACK TRANSACTION
/* Tue Nov 14 17:56:57 2006 */ *** ERROR *** The ROLLBACK TRANSACTION request has no corresponding BEGIN TRANSACTION. (SQL Server 3903)
/* Tue Nov 14 17:56:57 2006 */ OK
/* Tue Nov 14 17:56:57 2006 */ ALTER TABLE T2 DROP COLUMN newencrypted102
/* Tue Nov 14 17:56:57 2006 */ *** ERROR *** ALTER TABLE DROP COLUMN failed because column 'newencrypted102' does not exist in table 'T2'. (SQL Server 4924)
/* Tue Nov 14 17:56:57 2006 */ ALTER TABLE user_cache DROP COLUMN newencrypted102
/* Tue Nov 14 17:56:57 2006 */ *** ERROR *** ALTER TABLE DROP COLUMN failed because column 'newencrypted102' does not exist in table 'user_cache'. (SQL Server 4924)
/* Tue Nov 14 17:56:57 2006 */ ALTER TABLE T373 DROP COLUMN newencrypted102
/* Tue Nov 14 17:56:57 2006 */ *** ERROR *** Cannot find the object "T373" because it does not exist or you do not have permissions. (SQL Server 4902)
/* Tue Nov 14 17:56:57 2006 */ DROP TABLE temp_102_upgrade
/* Tue Nov 14 17:56:57 2006 */ OK
/* Tue Nov 14 17:56:57 2006 */ CLOSE DATABASE
/* Tue Nov 14 17:56:57 2006 */ SQL Trace Log -- OFF
On 11/14/06, strauss
<[EMAIL PROTECTED]>
wrote:
__20060125_______________________This posting was submitted with HTML in it___
**I would expect you to have to do this:1. Backup the existing ARS 5.01.02 ARSystem db in SQL Server 2000 to file.2. Build a new system on ARS 5.01.02 and SQL Server 2000 (ARS 5 and 6 will not install on SQL Server 2005)3. Restore the ARSystem database file and change db owner, giving you a clone of production4. Upgrade the clone system to ARS 7.00.015. Upgrade the db to SQL Server 2005 and back up ARSystem to file - Or- back it up to file from SQL Server 2000 (SQL Server 2005 should be able to restore / upgrade a SQL Server 2000 db in one pass)6. Keep the backup file, scrub the server, and install SQL Server 2005 and ARS 7.00.01 clean7. Restore the AR System database over the newly installed db and change db owner8. Start the Remedy service and test... there are variations on this if you are installing the db in Windows-only authentication mode, which ARS 7 handles MUCH better than ARS 5 did.
