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 - SalesLogix Scripting & Customization
Forum to discuss writing script in Architect plugins for SalesLogix & general SalesLogix customization topics (for Windows client only). View the code of conduct for posting guidelines.

Forums RSS Feed

Back to Forum List | Back to SalesLogix Scripting & Customization | New Thread

View: Search:

Author

Thread: hwo to fix the double quote probelm in connection string - Extended Properties="PORT=1706;LOG=ON;CASEINSENSITIVEFIND=ON;AUTOINCBATCHSIZE=1;"

Jordan
Posts: 30

hwo to fix the double quote probelm in connection string - Extended Properties="PORT=1706;LOG=ON;CASEINSENSITIVEFIND=ON;AUTOINCBATCHSIZE=1;" Your last visit to this thread was on 1/1/1970 12:00:00 AM

Your last visit to this thread was on 1/1/1970 12:00:00 AM

Posted: 11 May 07 10:29 PM

In an asp page (SLX third party application), it needs to connect to SLX server. I'd like to know hwo to resolve the double quote probelm in connection string. In other words, how to add Extended Properties="PORT=1706;LOG=ON;CASEINSENSITIVEFIND=ON;AUTOINCBATCHSIZE=1;" into the connection string.

Thanks

[Reply][Quote]

Jason Huber
Posts: 77

Re: hwo to fix the double quote probelm in connection string - Extended Properties="PORT=1706;LOG=ON;CASEINSENSITIVEFIND=ON;AUTOINCBATCHSIZE=1;" Your last visit to this thread was on 1/1/1970 12:00:00 AM

Posted: 12 May 07 1:31 AM

You dont need the quotes there....

Your connectionstring should just be

Dim sConnectionString
sConnectionString = "Provider=SLXOLEDB.1

assword=

ersist Security Info=True;"
sConnectionString &= "User ID=admin;Initial Catalog=SalesLogix_Eval;Data Source=Windows2003base;"
sConnectionString &= "Extended Properties=PORT=1706;LOG=ON"

It does look funny, but it ISNT
sConnectionString = "Provider=SLXOLEDB.1

assword=

ersist Security Info=True;"
sConnectionString &= "User ID=admin;Initial Catalog=SalesLogix_Eval;Data Source=Windows2003base;"
sConnectionString &= "Extended Properties="PORT=1706;LOG=ON""

If it were necessary, you could use """ to inject a single double quote into the string, but you dont need to.

[Reply][Quote]

Jason Huber
Posts: 77

Posted: 12 May 07 1:32 AM

The smiley faces with the tongues sticking out are complete unecessary as well

[Reply][Quote]

Jordan
Posts: 30

Posted: 13 May 07 10:32 AM

Thanks Jason. I tried the two ways, it still doesn't work.

Further more, my question is that:
Before, our SLX lan system is lan version 6.2.3. We have a testing classic asp web page like :

<%
Dim ContactID
Dim testConn
Dim testRS

Set testConn = Server.CreateObject("ADODB.Connection")
testConn.Open ("Provider=SLXOLEDB.1

assword=******

ersist Security Info=True;User ID=******;Initial Catalog=SALESLOGIX;Data Source=SLXTESTSERVER")
Set testRS = testConn.Execute("slx_dbids('Contact', 1)")
ContactID = testRS.Fields(0).Value
Response.Write(ContactID)
Response.Write("
")
testRS.Close
Set testRS = Nothing
testConn.Close
Set testConn = Nothing

%>

It worked so well. Then we upgraded our system to 7.0.1. The page doesn't work anymore. But I still can use an UDL file to connect the SLX Server and the connection string is the same as before. I added the item -- Extended Properties="PORT=1706;LOG=ON;CASEINSENSITIVEFIND=ON;AUTOINCBATCHSIZE=1;" -- into the connection string. It still failed. I tried the ways you offered, failed again

The error message is:
Could not establish connection with SLXServer. Check server is running and PORT is correct.
/portfolioadmin/Testing.asp, line 8

Any thought about it? Thanks

[Reply][Quote]

Ryan Farley
Posts: 2265

Posted: 14 May 07 12:06 PM

Sounds like the local version of the SLX provider does not match the version of the SLX Server. When you upgraded SLX to 7.0.1, did you reinstall the SLX provider on the web server?

[Reply][Quote]

Jordan
Posts: 30

Posted: 14 May 07 1:21 PM

I did install the SLX provider 7.0.1 on the web server. I used udl file to try the connection to the SLX Server and got it successfully. But when I tried to connect to the SLX server from an ASP page (third party application), It failed.

In our former SLX 6.2.3, on the web server, as long as I could connect to SLX Server successfully by using udl file, I must could get the connection from an asp page.

Because there is the double quote issue about port = 1706 in the connection string, I didn't add the part -- Extended Properties="PORT=1706;LOG=ON;...-- into the connection string in 6.2.3 environment. The default value was indeed 1706. In 7.0.1, do I have to add the port number in the connection string? If so, how do we handle the double quote problem? I tried the 2 ways Jason provided but the error message was the same as before:

[Reply][Quote]

Ryan Farley
Posts: 2265

Posted: 14 May 07 1:28 PM

You can just omit the quotes and it will still work fine. This is a valid connection string (notice no quotes around the extended properties)

connstr = "Provider=SLXOLEDB.1;Data Source=MYSLXSERVER;Initial Catalog=MYSLXALIAS;User Id=Admin

assword=

ersist Security Info=True;Extended Properties=Port=1706;Log=On"

Or you could add in the quotes like this (assuming we're still talking about your classic ASP page):

connstr = "Provider=SLXOLEDB.1;Data Source=MYSLXSERVER;Initial Catalog=MYSLXALIAS;User Id=Admin

assword=

ersist Security Info=True;" & Chr(34) & "Extended Properties=Port=1706;Log=On" & Chr(34)

See what I mean?

[Reply][Quote]

Jeremy Brayton
Posts: 491

Posted: 14 May 07 2:41 PM

Here's a C# version:


ConnectionString = "Provider=SLXOLEDB.1;Data Source=\"\";Initial Catalog=NO_ALIAS;Extended Properties=\"Port=1706;Log=On\"";

Data Source="" is unnecessary but I think I put it in there to make it easier to parse the OleDbConnectionStringBuilder.

[Reply][Quote]

Peter Hebenstreit
Posts: 3

Posted: 15 May 07 9:14 AM

I like to use chr(34) to input the double quote.

[Reply][Quote]

Jordan
Posts: 30

Posted: 22 May 07 10:47 AM

Thanks Ryan, using Chr(34), I can get the same string as the one I get from a testing UDL file.

I have further problem:
My saleslogix server (lan version) was upgraded from 6.2.3 to 7.0.1.
In the Connection Manager, I changed the provider from "Microsoft OLE DB Provider for SQL Server" into "SQL Native Client" (The SQL Server 2005 with SLX database is on the other server). The testing connection succeeded.
In a testing UDL file on a web server, I inputted the saleslogix provider, saleslogix server name, saleslogix database name, saleslogix username and password. The testing connection to the saleslogix server succeeded too. Furthermore, for the SLX system itself, it works well.
I have a third party asp application on the web server. A testing asp page has the following testing code:

<%
Dim testConn
Set testConn = Server.CreateObject("ADODB.Connection")
testConn.Open ("Provider=SLXOLEDB.1;password=testpwd;User ID=testacc

ersist Security Info=True;Initial Catalog=saleslogix;
Data Source=SLXTESTSERVER;Extended Properties=" & Chr(34) & "Port=1706;Log=On;CASEINSENSITIVEFIND=ON;AUTOINCBATCHSIZE=1;" & Chr(34))

testConn.Close
Set testConn = Nothing
%>

When requesting the testing page, it crashed and the error message was
Provider error '8000ffff'
Catastrophic failure
/t.asp, line 4 (note: the line of "testConn.Open ......)

But, before the 7.x upgrade (in 6.2.x), the page worked well. Any thought about it? Thanks for everyone in advance.

[Reply][Quote]

Jordan
Posts: 30

Posted: 22 May 07 10:55 AM

Please see above mentioned

[Reply][Quote]

Jordan
Posts: 30

Posted: 22 May 07 10:57 AM

Please see above mentioned

[Reply][Quote]

Duncan Cook
Posts: 164

Posted: 23 May 07 4:16 AM

HI Jordan,

I hold my connection string in the web.config as below, notice I just use single quotes instead of double quotes


<connectionStrings>
    <add name="DBConnector" connectionString="Provider=SLXOLEDB.1assword=admin1ersist Security Info=True;User ID=admin;Initial Catalog=MyDB;Data    Source=MYServer;Extended Properties='PORT=1706;LOG=ON;CASEINSENSITIVEFIND=ON;Impersonate=@ADMIN'"
        providerName="System.Data.OleDb" />
  </connectionStrings>

and below is how I call the ConnectionString


        Dim dbCon As New System.Data.OleDb.OleDbConnection(ConfigurationManager.ConnectionStrings(0).ToString)

[Reply][Quote]

Paul Engelbrecht
Posts: 4

Posted: 12 Jul 07 9:35 PM

Jordan,
Were you ever able to resolve your Provider error '8000ffff' "Catastrophic failure" on your ASP page?
I am having the same problem with the OLE DB Provider using PHP.

[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 © 2025 Customer FX Corporation. The information and opinions expressed here are not endorsed by Sage Software.	code of conduct \|

page cache (param): 6/19/2025 10:40:37 AM