Hi,

I'm trying to connect a new DB with SLX.

In the Connection Manager I log in with sysdba and DB "Master" Is that correct? I Remember that it has to be the new DB Name. I cant change to the new DB its not in the selection.

When I try to Connect the new DB in SLX with the user Admin I get a message box "unguilts Objectname SYSTEMINFO"

I can't login with SLX and the new DB.

regards for your help

Dennis

Use the AttachRemote.exe program found in c:\pf\saleslogix. Run it with the switch attachremote \admin (note, that's a backslash). Then, you will be able to choose what system to attach to and all options are enabled. The user is sysdba/masterkey (unless you are running the more secure version which is the sysdba: Ma$t3rk3y pair). To attach you'll need sa: SLXMa$t3r

Hi Mike,

thanks for your help.

Maybe i didnt explain correctly. I don't want to attach a Remote DB. I try to connect SLX on our Testserver to a Backup DB of our Livesystem.

I created a DB in the SQL Server Mng. Studio with the Backup of our Livesystem. Than i try to connect SLX with it.

regards Dennis

In which case, do the following:

1) Drop whatever you did

2) Create a new login called sysdba, set the password as non-enforced and give it a password.

3) Create a new database, grant sysdba permissons on it (public/dbowner only)

4) Restore the database over the top

5) Run: sp_change_users_login 'Update_One', 'sysdba', 'sysdba' on this database

You're then done, setup a connection as normal, using sysdba/password

Thx it helped me.

When i'm done the Connection Mng. ask me if the Testserver should be the LiveSyncServer. No way its just the Testsystem. Is there any chance to change that in the DB? I don't want to geht in trouble with the Remote DB/Users

Actually, the prompt is the other way around. It will warn you that the current server is set to "live", are you sure you want to set it to "dev". That's fine - you do. Also, if this is a database that involves remote users/offices - be VERY sure to remove the syncserver and alter the paths in BRANCHOPTIONS. Unless your server is well away (different subnet, vm etc) from your live then you can very easily start to pollute your live system as the paths will be accessible !

Actually, the prompt is the other way around. It will warn you that the current server is set to "live", are you sure you want to set it to "dev". That's fine - you do. Also, if this is a database that involves remote users/offices - be VERY sure to remove the syncserver and alter the paths in BRANCHOPTIONS. Unless your server is well away (different subnet, vm etc) from your live then you can very easily start to pollute your live system as the paths will be accessible !

ok i did that now

update sysdba.branchoptions set attachmentpath = '\\Ntsg44\SLXUPD_Test\WPEJAWL\Documents'

where sitecode = (Select PrimaryServer from sysdba.Systeminfo where SystemInfoID = 'PRIMARY')

update sysdba.branchoptions set saleslibrarypath = '\\Ntsg44\SLXUPD_Test\WPEJAWL\Library'

where sitecode = (Select PrimaryServer from sysdba.Systeminfo where SystemInfoID = 'PRIMARY')

update sysdba.Syncserver set serverpath = '\\Ntsg44\SLXUPD_Test\WPEJAWL'

where sitecode = (Select PrimaryServer from sysdba.Systeminfo where SystemInfoID = 'PRIMARY')

delete from sysdba.syncservicefile

delete from sysdba.synctransfer

delete from sysdba.slxwebserver

update sysdba.systeminfo set PINGSERVER = 'ntsg44'

NTSG44 is our Testsystem, that should be ok after that. Its in the same net.

Yep, that's fine - if, however, you don't need sync at all then you can just do this:

UPDATE sysdba.SYSTEMINFO SET PRIMARYSERVER = 'NOSYNCSERVER' WHERE SYSTEMINFOID = 'PRIMARY'
go
UPDATE sysdba.BRANCHOPTIONS SET SITECODE = 'NOSYNCSERVER'
go
UPDATE sysdba.SITEOPTIONS SET HOSTSERVER = 'NOSYNCSERVER' WHERE HOSTSERVER IS NOT NULL
go

That'll remove all sync just to be sure !

ohh perfect thanks, I don't need it on the Testsystem.

great thanks Mike

this is not working

UPDATE sysdba.BRANCHOPTIONS SET SITECODE = 'NOSYNCSERVER'

telling me

verletzung der PRIMARY KEY-Einschrnkung 'PK_BRANCHOPTIONS'. Ein doppelter Schluessel kann in das 'sysdba.BRANCHOPTIONS'-Objekt nicht eingefügt werden.

That's OK, it's because you had 2 sync servers (a remote office maybe). Just go into Admin now and delete the 2 sync server/ro licenses. You can then delete the 2nd one in branchoptions but there's no need really.

I can not login to SLX and Admin

Data dictionary can not be initialized. Seems to be a problem with the Admin account

Did you do all of these steps ?

www.empath-e.com/documents/bulletins/081009.pdf

That worked thanks. Now i get a msgbox: Startfailure: The Module cant be found. when I start SLX.

Hmm, that's a new one on me - probably best if you call into SLX support for further guidance. Provided the database etc. is fine then everything should work now. I don't see any reason why not - but, unfortunately, there could be a whole host of them (local machine, versions, hot-fixes etc) but v.difficult to do this remotely now.