5/15/2024 1:31:07 AM
|
| |
| slxdeveloper.com Community Forums |
|
| |
|
|
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!
Forum to discuss using the SalesLogix OLE DB Provider from external applications (including usage of built-in provider procedures). View the code of conduct for posting guidelines.
|
|
|
|
OLEDB connection string fails if SalesLogix database .mdf file is stored on D: drive
Posted: 09 Dec 08 1:01 PM
|
From a Visual Basic script, I've successfully connected to a SalesLogix database using the following connection string IF the database .mdf file is stored on drive C:\.
Provider=SLXOLEDB.1;
Password=;
Persist Security Info=True;
User ID=admin;
Initial Catalog=slx72_proto;
Data Source=DBS01;
Extended Properties=PORT=1706;LOG=ON;CASEINSENSITIVEFIND=ON;AUTOINCBATCHSIZE=1;SVRCERT=;
However, the connection fails when attempting to connect to a database whose .mdf file is stored on drive D:\. Is there a way to modify the connection string for such a case, or must the database file always be housed on drive C\: if an external OLEDB connection is to be used?
UPDATED INFORMATION: I restored my prototype database to the C:\ drive and found that the connection string fails on the restored database but succeeds on the SalesLogix databases (saleslogix and saleslogix_eval). I've hunted for any differences in configuration or permissions but haven't found any. |
|
|
|
Re: OLEDB connection string fails if SalesLogix database .mdf file is stored on D: drive
Posted: 10 Dec 08 4:36 AM
|
After you restore the database, are you also fixing the sysdba user (if it is a different machine), and setting up a new connection in the oledb provider?
You can test being able to connect by building a UDL file.
- create a text file, rename it to .UDL and double click it. (Make sure to save passwords)
After you have connected, open with notepad to see the connect string
ws |
|
|
|
Re: OLEDB connection string fails if SalesLogix database .mdf file is stored on D: drive
Posted: 10 Dec 08 5:20 PM
|
| Thanks for your reply, Walter. Yes, I had run the sysdba fix script, but still experienced the error. I've since fixed the problem, though, through a combination of placing the database .mdf file on the C: drive (with the log file on a separate drive) and editing the sysdba user security settings in SQL Server. Once I did this, generating a connection string via the UDL tool succeeded and my external scripts connect successfully. |
|
|
|
You can
subscribe to receive a daily forum digest in your
user profile. View the site code
of conduct for posting guidelines.
 Forum RSS Feed - Subscribe to the forum RSS feed to keep on top of the latest forum activity!
|
|
|
|
|
|
|
|