Showing posts with label solution. Show all posts
Showing posts with label solution. Show all posts

Saturday, February 25, 2012

Connecting SQL2005 from older C++ client - the solution was ...

After setting up
SQL2005express server with
mixed authentification I got the problem
1. I couldnt find a working ConnectionString
2. Studio2005 didnt connect to SQL any more
In the meantime I found that at least the following OLEDB-ConnectionString is working, when Im logged in as admin and can use Windows Autentication:
Provider='sqloledb'
Data Source='.' - without '/SQLEXPRESS' !!
Initial Catalog='MyDatabaseName'
Integrated Security='SSPI'
For details of SQL setup and code to test possible connetion strings
please see my homepage.
Martin
text of my question from 02 Dec 2005
I want to feed data of a C++ 6.0 project into SQL server and hoped that StudioExpress would give me the correct connection string in detail.
But my StudioExpress doesnt conntect to a SQL server configured for SQL-Authentication.
I made screenshote of the details an put them in subfolders of my homepage
http://home.arcor.SQL2005.
Does anybody know what exact connection string has to be used and which changes in StudioExpress AdvancedConnectionProperties are necessary to establish a working connection?

The above link contains a collection of screenshots with details of the problem.
In the meantime I did a standard setup of the whole StudioExpress2005 C# paket and put screenshots on my homepage where you can see the difference between standard setup and single SQLExpress setup in SQL-Authentication mode.
Martin

Friday, February 24, 2012

Connecting OSQL to MSDE using Windows NT Authentication?

I am installing MSDE SP3a on an NT 4.0 server and experiencing the
'CryptoAPI failed' error.
Now I found the error solution on the MS website, but this requires using
osql and connecting using Windows NT Authentication.
I have installed using SQL securitymode. Will this prevent me from
connecting using Windows NT Auth..?
If so, how can reset the securitymode to SQL after I have installed and
applied the correction for the original issue?
I am logged onto the NT server using the ADMINISTRATOR id, can I start OSQL
without the -U and -P parms?
Does the ADMINISTRATOR id require any additional permissions to connect to
MSDE? The reason I ask is because the MS document specifies "Make sure to
use Windows NT Authication while you are logged on with a Windows NT Account
that is a member of the SQL Server sysadmin role".
Install parms:
MSDERelA\setup.exe DATADIR=^sDataDrive"^ DISABLENETWORKPROTOCOLS=0
INSTANCENAME=XXXXX SAPWD=SA_pwd SECURITYMODE=SQL TARGETDIR=^sDataDrive^ /L*v
^sDataDrive XXXXX.log^ /qb
Thanks for any/all help..
Jim K.
This is mixed Authentication, so Windows Authentication should work, if
you are a local administrator try using the -E switch with OSQL. OSQL
-E which connects to the local server with the Windows credentials.
HTH, Jens Suessmeyer.