Home | Forums | Contact | Search | Syndication  
 
 [login] [create account]   Friday, November 22, 2024 
 
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!
 Architect Forums - ADO General
Forum to discuss ADO specific questions for use with SalesLogix. View the code of conduct for posting guidelines.
Forums RSS Feed


 Back to Forum List | Back to ADO General | New ThreadView:  Search:  
 Author  Thread: COnnection problem with SLXOLEDB.1
Yogesh Dave
Posts: 24
 
COnnection problem with SLXOLEDB.1Your last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 08 Apr 09 1:17 PM
Hi,

We are on version 7.2 and have some issue connecting to the server using SLXOLEDB.1 from .NET code.
HEre is my connection string:
provider=SLXOLEDB.1; Datasource=My_SL_ALIAS;Initial Catalog=MY_SL_DB; User ID=MYSLUserName; password=MYSLPassword; Persisit Security Info=True; Extended Properties=\"SLX Server=MYSLServer; Port=1706; Log=On;\"

AND here is the error I am getting.
Failed to connect to SLXServer. Check if server is running and is compatible with the current provider version.


Could anybody point what is wrong with my connection string?

thanks,
Yogesh
[Reply][Quote]
Raul A. Chavez
Posts: 1300
Top 10 forum poster: 1300 posts
 
Re: COnnection problem with SLXOLEDB.1Your last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 08 Apr 09 4:51 PM
Assuming that you don't actually have a Connectivity problem and that yourr parameters are properly configured:

- Do you have the OLEDB Provider installed on your Dev machine (or wherever you are running this code from)? (Alternatively, do you have an SLX Application installed and is it able to connect to SLX?)
- If so, is the SLXSystem.exe process running (verify via Task Manager).
If it is running, you may want to kill it and then run your code and see if a new instance of it is launched.

[Reply][Quote]
Raul A. Chavez
Posts: 1300
Top 10 forum poster: 1300 posts
 
Re: COnnection problem with SLXOLEDB.1Your last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 08 Apr 09 4:52 PM
And on closer inspection, I have not seen in the past the use of SLX Server as an Extended Property. SLX Server should be the value of your Data Source.
[Reply][Quote]
Yogesh Dave
Posts: 24
 
Re: COnnection problem with SLXOLEDB.1Your last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 08 Apr 09 8:55 PM
Raul,

THanks for your response.

I have tried removing extended properties and moving SLX Server as DataSource as well. Still getting the same error.
I do have OLEDB installed on the development machine. I see the registry entry. But don't see SLXSystem.exe running in the TaskMaster. Could that be a problem? What is remedy?

I am really new to SalesLogix development.

thanks,
Yogesh
[Reply][Quote]
Phil Parkin
Posts: 819
Top 10 forum poster: 819 posts
 
Re: COnnection problem with SLXOLEDB.1Your last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 08 Apr 09 10:35 PM
Are you able to verify your connection string by creating a suitable UDL file?


[Reply][Quote]
Yogesh Dave
Posts: 24
 
Re: COnnection problem with SLXOLEDB.1Your last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 09 Apr 09 6:20 AM
I don't know how to do that. Can you describe please? And I will check it out.

thanks,
[Reply][Quote]
Phil Parkin
Posts: 819
Top 10 forum poster: 819 posts
 
Re: COnnection problem with SLXOLEDB.1Your last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 09 Apr 09 6:36 AM
No problems.

1) Create an empty text file - say conn.txt
2) Rename it to conn.udl
3) Double-click it - data link properties window will open
4) Select Provider/Connection information for your SLX connection and click OK to save.
5) Open conn.udl in Notepad and the connection string will be displayed as, I think, the final line in the file.
[Reply][Quote]
Yogesh Dave
Posts: 24
 
Re: COnnection problem with SLXOLEDB.1Your last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 09 Apr 09 9:46 AM
Hi Phil,

Thank you for your suggestions. It worked like a charm !

I am all set. I still am not sure what caused it to fail. But I am using this generated string now and it works. Here it is for all fellow members who may run into the same issue in near future.

Provider=SLXOLEDB.1ersist Security Info=False;Initial Catalog=MySLDBName;Data Source=MYSLServer;User ID=xxx; password=xxx;Extended Properties="PORT=1706;LOG=ON;CASEINSENSITIVEFIND=ON;AUTOINCBATCHSIZE=1;"

Thank you all,
Yogesh
[Reply][Quote]
 Page 1 of 1 
  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!
 

 
 slxdeveloper.com is brought to you courtesy of Ryan Farley & Customer FX Corporation.
 This site, and all contents herein, are Copyright © 2024 Customer FX Corporation. The information and opinions expressed here are not endorsed by Sage Software.

code of conduct | Subscribe to the slxdeveloper.com Latest Article RSS feed
   
 
page cache (param): 11/22/2024 10:50:13 AM