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!
 External Development Forums - General External Development
Forum to discuss general external development topic (related or not to SalesLogix development). View the code of conduct for posting guidelines.
Forums RSS Feed


 Back to Forum List | Back to General External Development | New ThreadView:  Search:  
 Author  Thread: Webservice Error
joe
Posts: 26
 
Webservice ErrorYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 21 Oct 08 8:00 AM
I am trying to create a C#.NET webservice that connects to either the sqlserver(works) or local datatase(partial working). I am only reading from the local.
I can get the local to work if I know the user name and password, but I am not sure that I am going to be able to pull that information out of the code. Even if I can I would rather user sa or sysdba. (Q1) Can I get the users password.

For local; SLX would call the webservice which would query SLX. Passing all of the params that I need directly to the webservice would defeat the purpose of having a cnetralized webservice. Also, it would be a lot of code to put into SLX since I have over 40 params that I need to fill. (Q2) Why can't I connect with sa or sysdba accounts?

I also can connect through SQL Management studio with sysdba and masterkey. In SQL Management under Security\Users I see dbo and sysdba, but not the actual users name, which also surprised me. (Q3) Why is that?

My webservice uses a SqlDataReader for the Server and OleDbDataReader for the local instance to an IDataReader. Also, I pass SQLCommand and OleDBCommand to an IDbCommand. I use these to objects to query and read the data.



_userDB.SQLUserID = "sa";//fails
_userDB.SQLPwd = "SLXMaster";//fails
Provider=SLXOLEDB.1;Data Source=SDR9390D;Initial Catalog=SLXREMOTE;User Id=saassword=SLXMasterersist Security Info=True;Extended Properties=Port=1706;

OR

_userDB.SQLUserID = "sysdba";//fails
_userDB.SQLPwd = "masterkey";//fails
Provider=SLXOLEDB.1;Data Source=SDR9390D;Initial Catalog=SLXREMOTE;User Id=sysdbaassword=masterkeyersist Security Info=True;Extended Properties=Port=1706;

All failuers result in the message below. See even farther down for a working con string.

System.Data.OleDb.OleDbException: No error message available, result code: DB_SEC_E_AUTH_FAILED(0x80040E4D).
at System.Data.OleDb.OleDbConnectionInternal..ctor(OleDbConnectionString constr, OleDbConnection connection)
at System.Data.OleDb.OleDbConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningObject)
at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup)
at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
at System.Data.OleDb.OleDbConnection.Open()
at Dematic.Tools.SLX.Data.DBConnections.get_connOLE() in C:\Data\Code\EngApps\Dematic.Tools.SLX\Dematic.Tools.SLX.Webservice\Dematic.Tools.SLX.Data\DBConnections.cs:line 33
at Dematic.Tools.SLX.Data.SLXOpportunity..ctor(String opportunityID, String conLoc) in C:\Data\Code\EngApps\Dematic.Tools.SLX\Dematic.Tools.SLX.Webservice\Dematic.Tools.SLX.Data\SLXOpportunity.cs:line 63
at Dematic.Tools.SLX.Data.SLXIntegration.CreateNewIPS(String opportunityId, String conLoc) in C:\Data\Code\EngApps\Dematic.Tools.SLX\Dematic.Tools.SLX.Webservice\Dematic.Tools.SLX.Data\SLXIntegration.cs:line 9
at Service.NewIPSFromSLX(String opportunityID, String connLoc) in c:\Data\Code\EngApps\Dematic.Tools.SLX\Dematic.Tools.SLX.Webservice\App_Code\Service.cs:line 30




_userDB.SQLUserID = "holtrone";//works
_userDB.SQLPwd = "holtrone";//works
//working conn string
Provider=SLXOLEDB.1;Data Source=SDR9390D;Initial Catalog=SLXREMOTE;User Id=holtroneassword=holtroneersist Security Info=True;Extended Properties=Port=1706;

I greatly appreciate any responces to these issues.
[Reply][Quote]
Ken Poggensee
Posts: 71
 
Re: Webservice ErrorYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 22 Oct 08 12:47 AM
The Slx Provider 'SLXOLEDB.1' does not use SQL Logins to connect. These parameters are set up in the Slx 'Connection Manager' and are used when the provider tries to connect. Now with that being said, the provider connects by first using the SQL 'sysdba' user\pass to the database that was defined in the ‘Connection Manager’. The parameters you are passing in the connection string are for the Slx user\pass. The Provider layer uses this to validate a valid ‘Slx User’ and pass. You could use the Admin\Pass but this has disadvantages as you have to hard-code the admin password and that obviously can change, but you might be able to think of other alternatives…

Hope I was on-track with what you were asking

--Ken--
[Reply][Quote]
joe
Posts: 26
 
Re: Webservice ErrorYour last visit to this thread was on 1/1/1970 12:00:00 AM
Posted: 22 Oct 08 6:17 AM
I guess I am a little confused. All I really want to do is connect to different users local database, but I do not know what credentials would work. I can get a slx user user\pass to work, but I cannot get any type of admin(sysdba, sa, admin) credentials to work. What should I be passing from my webservice?
[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 3:13:44 PM