The Forums on slxdeveloper.com are now retired. The forum archive will remain available for the time being. Thank you for your participation on slxdeveloper.com!
|
|
Remote Database and SQL 2005
Posted: 13 Feb 07 1:48 PM
|
fiogf49gjkf0d Hi everyone.
I have a problem when i want to create a remote user database with slx 6.4 and SQL 2005. The main problem is that the architect cant complete the creation because the "master" database don’t have the table "sysxlogins". This is a change in SQL, but i need to know if there is something that i can do to make this works.
Maybe, in some way, if is possible, to hand-make that table in the "master" database of SQL 2005. I don't know
Any help will be appreciated
Thank you very much |
|
|
|
Re: Remote Database and SQL 2005
Posted: 13 Feb 07 2:27 PM
|
fiogf49gjkf0d I've been told by Sage (SalesLogix Support) that SQL 2005 isn't supported for remote databases. But if you created the remote DB with the SLX Admin the actual DB version should be 8.0 not 9.0. I know you can run a SQL 2000 DB on a SQL 2005 system but that may not be the problem. The underlying data connectivity to the database engine may not be compatible. I have a laptop running both 2000 and 2005 but I had 2000 (MSDE) on there first. |
|
|
|
Re: Remote Database and SQL 2005
Posted: 13 Feb 07 3:12 PM
|
fiogf49gjkf0d Thanks for the reply.
So you are telling me that in your case it did work because you have MSDE 2000 installed first?
And also that i can forget about remote database in SQL 2005, right?
Thanks |
|
|
|
Re: Remote Database and SQL 2005
Posted: 13 Feb 07 3:20 PM
|
fiogf49gjkf0d Here is what I did. I never counted on SQL 2005 Personal Edition for my remote setup. I'd heard pretty early on that it wasn't supported. But I wanted the new free 'Enterprise Manager' that comes with the 2005 Personal Edition. I loaded that AFTER the MSDE2000 was installed. By nature I have access to SQL 2005 DBs but SQL remains on 2000.
The bottom line is that SLX remote can live happily right next to SQL 2005 but not with it. Hope that helps. |
|
|
|
Re: Remote Database and SQL 2005
Posted: 13 Feb 07 3:31 PM
|
fiogf49gjkf0d This is certainly possible. It is even possible to have sql 2005 remotes, although that will take some extra work. To cut a database from SQL 2005, you need to do the following on the host database
Go to Start > All Programs > MS SQL Server 2005 > Configuration Tools >
SQL Server Surface Area Configuration.
Select surface are configuration for features
Select xp_cmdshell
Enable xp_cmdshell
Apply
OK.
log into QA as sa and run the following
use master
go
create view sysxlogins as select * from sys.syslogins
go
|
|
|
|
Re: Remote Database and SQL 2005
Posted: 14 Feb 07 1:32 PM
|
fiogf49gjkf0d Well Doug I really thank you your help. I did what you told me and finally its works perfect.
But I have another problem but this time is when I try to attach de database in a client with sql 2000.
While in the process i get this error: "COULD NOT FIND ROW IN SYSINDEXES FOR DATABASE ID 5, OBJECT ID 1, INDEX ID 1. RUN DBCC CHECKTABLE ON SYSINDEXES".
I don't know what to do.
Thanks in advance.
|
|
|
|
Re: Remote Database and SQL 2005
Posted: 14 Feb 07 1:34 PM
|
fiogf49gjkf0d You will need to set up an admin workstation with msde installed and cut to that workstation, instead of cutting on the host database server. That is your safest bet. |
|
|
|
Re: Remote Database and SQL 2005
Posted: 14 Feb 07 1:43 PM
|
fiogf49gjkf0d So, you are saying that i have to do it in a PC with ONLY the msde and not the SQL Server?
But in that pc could i have installed de thar architect and admin?
Thanks |
|
|
|
Re: Remote Database and SQL 2005
Posted: 14 Feb 07 2:25 PM
|
fiogf49gjkf0d You can still host the database on SQL 2005. When you go to cut the database, you need to point the database cutting utility to a workstation that has either MSDE or sql 2000 on it. You can then take that database (which will now be on the workstation) and send it to the remote machine and attach it. You can continue to use architect and admin from the SQL 2005 machine if you want to. |
|
|
|
Re: Remote Database and SQL 2005
Posted: 14 Feb 07 2:43 PM
|
fiogf49gjkf0d Sorry, but i still don't understend.
What i did is this: I create a Remote User Database with the Architect in a Server with SQL Server 2005 installed.
Then i bring the created DB to a EndUser PC, here at my work to test the atachment. This PC works with MSDE 2000 but also it has SQL Server 2000 installed on it.
And in this PC is where i have the error that i mention before.
Sorry but is the first time that we deal with SQL 2005
Thanks |
|
|
|
Re: Remote Database and SQL 2005
Posted: 15 Feb 07 2:39 AM
|
fiogf49gjkf0d Matias.
Due to the issues you have faced and I can only recommend you CEASE using SQL2005 and revert to using SQL2000/MSDE throughout. Your license for SQL2005 allows this back-grade. SQL2005 should *only* be used on the host and should not really be used to cut remotes from (as they end up as SQL2005 - which you then tried to load on SQL2000 which clearly won't work. To avoid further confusion and time consumption - revert back to SQL2000 throughout and you'll be sorted. |
|
|
|
Re: Remote Database and SQL 2005
Posted: 04 May 07 12:14 PM
|
fiogf49gjkf0d Hello!
I thought I would help here..I just spent about 40 hours with SLX tech support, over the past two months, trying to resolve this. After all that time on the phone with them, i found the solution on my own.
The solution is so simple, i almost cried.
In order for you to cut a remote db from a SQL 2005 server, to a remote pc, you must:
1. Have a clean machine
2. Have a valid msde install on the remote db (explained below)
Clean machine - I hate this term, but it proved useful. In order to cut the remote db, you must do this from the admin client on a machine similar to the remote pc. In this case, i had a fresh install of XP on my desktop. I had NO prior sql 2005 or 2000 installs. I installed MSDE 2000 Rel A SP3 on this machine. After installing the client, I was able to cut the remote. You would set the second "Create Option" as Create on MSDE Instance from SQL Host. In the "MSDE Instance Name" use the name of the machine you are on. The SYSDBA password is the default, 'masterkey' unless you have changed that for sysdba. In the Host DB Owner Login, use 'sysdba' and the 'masterkey' password. For the Target Database Administrator Login, the default for MSDE is blank. You can change that when you create your instance by using the "SAPWD=" flag on the installation. I would leave it blank. The remote path is TO YOUR LOCAL MACHINE. So make sure that path exists. DO NOT listen to slx support about having the SQL 2005 odbc drivers and crap, that is hogwash.
Remote PC- I had to uninstall everything, then go and re-install the remote client from the install point. Make sure, at the end of the installation for remote, you use THAT msde install. There is some SQL$ file that helps point the msde install, or some crap (according to slx support).
Then move the cut db from the clean machine to the remote pc, and it works. I was getting all the errors described above, until i used this method.
|
|
|
|
Re: Remote Database and SQL 2005
Posted: 27 Jun 07 11:47 AM
|
Hi Guys,
As you have got as far as syncing, I was wondering if you could help me???
I have set up a SQL Server 2005 database server with just connection manager on. i have installed the SQL Native client on this machine, then created a connection in connection manager using the SQL Native Client provider. This bit seems fine.
I have also set up a seperate server with the Admin workstation, sysnc server and speed search server on. I have installed MSDE on here (via SalesLOGIX install) and then installed the SQL Native Client. The problem that I have is that the SQL Native client does not appear in the provider tab of the Data Link Manager (For the client or Administrator). Is this the case for you guys too??? Also, if i try using the existing provider (SalesLOGIX OLE DB provider) in the Data Link manger I get the following error "Unable to initialise data directory".
I spoke to SalesLOGIX support who insist that the SQL Native provider is not supposed to appear in the provider tab of the Data Link Manager, but I know that I used it in a previous install.
I would really appreciate some help. Thanks in advance. |
|
|
|
Re: Remote Database and SQL 2005
Posted: 27 Jun 07 12:52 PM
|
| I have never seen the SQL Native Client show up in the Data Link Manager, nor would I expect it to. It should show up in the Connection Manager dialog. In this case I think SalesLogix support is correct. |
|
|
|
Re: Remote Database and SQL 2005
Posted: 27 Jun 07 2:02 PM
|
| thanks for your help Frank. Any idea why i'm getting the "unable to initialise data directory error", even though i have installed SQL Server Native client on the Both Servers? |
|
|
|
Re: Remote Database and SQL 2005
Posted: 27 Jun 07 7:02 PM
|
| Did you delete the existing Connection Manager and DataLink entries, then recreate them after you install the SQL Native Client? |
|
|
| |
|
Re: Remote Database and SQL 2005
Posted: 28 Jun 07 9:46 AM
|
I am at a loss as to why you are getting the error. I have seen the error before and it has always been fixed by installing SQL Native Client components on ALL the system that will access SalesLogix and ensure that the Connection Manager Configuration user the SQL Native Client.
BTW, all the site that I have setup have:
1. SQL 2005 DB Server: No SalesLogix components are installed on this system. Note: the SQL Native Client is part os SQL Server 2005
2. APP Server: SQL Native Client, SLXServer, SLX Admin, MSDE from SLX CD.
3. Sync Server: SQL Native Client, SLX SyncServer
|
|
|
|
Re: Remote Database and SQL 2005
Posted: 28 Jun 07 9:54 AM
|
Hi frank,
Thanks, I did the above earlier, which seemed to fix the problem. Although, as i was setting up an eval system for a client, I have kept the sync server on the same machine as the app server. This all works now. Thanks again for all your help. |
|
|
|