Upgrade to ECC 6.0 fails - cannot read SVERS

[Former Member]

I recently migrated a 4.7 system to new hardware and in the process upgraded from SQL 2000 to SQL 2005.

Now I'm doing an upgrade and the upgrade fails - it is unable to find table SVERS.

When I log in to SQL Ent Mgr as <sid>adm and I run a query against my database, the following query does not work:

select * from SVERS

but

select * from sid.SVERS does work

This means that somehow sidadm is not connecting correctly. I've verified the connection setting and the sid database is the default db for this user.

Any ideas?

[Former Member · Accepted solution]

more info ...

environment variables are correctly I beleive:

MSSQL_SERVER=rpulbx

MSSQL_DBNAME=LBX

MSSQL_SCHEMA=lbx

In the Default profile:

dbms/type mss

dbs/mss/server rpulbx

dbs/mss/dbname LBX

dbs/mss/schema lbx

[Former Member · Accepted solution]

Hi,

Check the SAP note 610640, this may be helpful.

Best Regards,

Sachin.

[Former Member]

Hi,

The problem is, that the SQL logins are not correct. The problem is, that if you change something on OS level, SQL Server always uses the old login information. In you case the user logs in to the wrong database (master and not <SID>) so SVERS couldn't be find.

Solution: Delete the SAP logins in SQL Server (<sidadm>, SAPService<SID>) and then create them manually in SQL Server (default DB <SID>). After that everything would work fine.

Regards

Daniel