Post reply

Connecting to MSDE

  • February 19, 2006 at 8:10 pm

    #68285

    Hi All,

    I have a number of questions relating to connecting to MSDE that I have not been able to discover the answers for on the web.

    Any help is appreciated.

    1. Can MSDE be connected to across a workgroup (no domain)?

    2. What order do I use in a connection string (.NET/C# app)

       a) data source=server2003\AMOSGSQL

       b) data source=AMOSGSQL\server2003

       c) data source=AMOSGSQL

    None of these seem to work for me.

    I have tried both Windows and SQL authentication. I have re-installed MSDE making sure I used SECURITYMODE=SQL, DISABLENETWORKPROTOCOLS=0, SAPWD=xxxx

    3. When attempting to connect to an instance of MSDE from another computer using SQL authentication, I am receiving an error advising that the login failed for user (Fred).

    4. When attempting to connect to a local instance of MSDE using SQL authentication, I recieve the error "Cannot open the database requested in login 'SIMSup'. Login fails. Login failed for user Fred."

    I am able to connect to a local instance of MSDE using Windows authentication, but when using a remote PC, I receive the error in #3 above.

    Here is the connection string as it appears in my config file

    <add key="connALaN.ConnectionString" value="data source=Server2003;user id=Fred; password=pptl77;initial catalog=SIMSup" /> (this works for local instances only)

    I have also tried this connection string:

    <add key="connALaN.ConnectionString" value="Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=COACHman;Data Source=SERVER2003;Use Procedure for Prepare=1;Auto Translate=True;Packet Size=4096;Workstation ID=DELLXEON;User Use Encryption for Data=False;Tag with column collation when possible=False" />

    (This string works both locally and remotely, but it means I have to enter every user into the SQL database and provide security access, and this is not possible for some client sites. ie: Users change from time to time).

    Sorry about all the questions but things only seem to work properly on my development machine and I must be missing something when deploying elsewhere.

    cheers,

    Mark Chimes

  • February 19, 2006 at 9:30 pm

    #621929

    There is one further question I meant to ask.

    Does it make any difference if the workstation is running Windows XP home edition rather than Professional edition?

    I realise this means the home edition cannot connect to a Domain, but I have no idea if this effects connecton to a SQL server.

    cheers,

    Mark

     

  • February 20, 2006 at 4:02 am

    #621958

    Hey Guys,

    Got it sorted!

    I created my table user IDs before the database user IDs 🙁

    cheers,

    Mark Chimes

     

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply