SAP client requires re-connecting to SQL Server every login
Hi Experts
I have one PC where the user always has to enter the SQL server details every time they login.
Is there a reason this would happen? The client PC in question is running Vista.
Thanks
Greig
Hi Greig,
You mat check this thread first:
terminal server connection reset after each login to local server
Thanks,
Gordon
Similar Messages
-
SAP ECC6.0 cannot connect to SQL Server Database after recreating DB server
We had a disaster with our ECC 6.0 Development system a few days ago. The system is called “DEV”. The SQL Server database server got wiped out and we didn’t have a backup. Luckily, we did have a backup of the database. Our system engineers rebuilt the server and our DBA reinstalled SQL Server and restored the database. The database came up fine, but when we try to start SAP, it fails. “R3trans –d” also fails. The database is SQL Server 2008R2 10.50.2769. The OS is Windows Server 2008R2.
We verified that the “devadm” and “SAPServiceDEV” accounts have permissions on the on the server. We set the following Environment Variables for the devadm account on the database server:
DBMS_TYPE = mss
MSSQL_DBNAME = DEV
MSSQL_SCHEMA = dev
MSSQL_SERVER = <database server name>
SAPLOCALHOST = <database server name>
SAPSYSTEMNAME = DEV
We also set the following Registry Key:
HKEY_LOCAL_MACHINE/Software/SAP/DEV
Type: REG_SZ
Value: AdmUser
String: <database server name>\devadm
We didn’t install any kind of SAP software on the database server.
Is there any kind of SAP components we need to install on the database server? Do we need to run the SAP installer on the database server to get everything setup correctly? I looked at another one of our SQL Server database servers and it has SAP Management Console installed and there is a C:\Program Files\SAP\hostcntl folder. I don't know what that is or it has anything to do with SAP being able to connect to the database.
Here is the error message in the R3trans log file:
4 ETW000 [ dev trc,00000] Wed Apr 29 09:44:39 2015 1501385 1.531756
4 ETW000 [ dev trc,00000] ERROR: -1 in function ExecuteAndFlush (SQLExecDirect) [line 6702] 35 1.531791
4 ETW000 [ dev trc,00000] (102) [42000] [Microsoft][SQL Server Native Client 10.0][SQL Server]Incorrect syntax near 'execute.'.
4 ETW000 22 1.531813
4 ETW000 [ dev trc,00000] <if user_name() != 'dev' execute as login = suser_sname(suser_sid('dev')) with no revert> failed -- connect terminated
4 ETW000 38 1.531851
4 ETW000 [ dblink ,00000] ***LOG BY2=>sql error 102 performing CON 56 1.531907
4 ETW000 [ dblink ,00000] ***LOG BY0=>[Microsoft][SQL Server Native Client 10.0][SQL Server]Incorrect syntax near 'execute.'.
4 ETW000 30 1.531937
2EETW169 no connect possible: "DBMS = MSSQL --- SERVER = '<db server name>' DBNAME = 'DEV'"
Please let me know what we need to do to get SAP to connect to the database.
Thanks,
JerryHere it is: 4 ETW000 R3trans version 6.22 (release 720 - 18.11.11 - 11:29:00). 4 ETW000 unicode enabled version 4 ETW000 =============================================== 4 ETW000 4 ETW000 date&time : 29.04.2015 - 19:33:01 4 ETW000 control file: 4 ETW000 R3trans was called as follows: R3trans -d 4 ETW000 trace at level 2 opened for a given file pointer 4 ETW000 [ dev trc,00000] Wed Apr 29 19:33:01 2015 83 0.000083 4 ETW000 [ dev trc,00000] db_con_init called 28 0.000111 4 ETW000 [ dev trc,00000] set_use_ext_con_info(): rsdb/ssfs_connect not set => ssfs not used 31 0.000142 4 ETW000 [ dev trc,00000] determine_block_commit: no con_hdl found as blocked for con_name = R/3 4 ETW000 20 0.000162 4 ETW000 [ dev trc,00000] create_con (con_name=R/3) 10 0.000172 4 ETW000 [ dev trc,00000] Loading DB library 'dbmssslib.dll' ... 31 0.000203 4 ETW000 [ dev trc,00000] DlLoadLib success: LoadLibrary("dbmssslib.dll"), hdl 0, addr 000007FEEE6D0000 4 ETW000 1865 0.002068 4 ETW000 [ dev trc,00000] using "D:\usr\sap\DEV\SYS\exe\uc\NTAMD64\dbmssslib.dll" 14 0.002082 4 ETW000 [ dev trc,00000] Library 'dbmssslib.dll' loaded 13 0.002095 4 ETW000 [ dev trc,00000] function DbSlExpFuns loaded from library dbmssslib.dll 15 0.002110 4 ETW000 [ dev trc,00000] Version of 'dbmssslib.dll' is "720.00", patchlevel (0.200) 84 0.002194 4 ETW000 [ dev trc,00000] function dsql_db_init loaded from library dbmssslib.dll 16 0.002210 4 ETW000 [ dev trc,00000] function dbdd_exp_funs loaded from library dbmssslib.dll 11 0.002221 4 ETW000 [ dev trc,00000] New connection 0 created 29 0.002250 4 ETW000 [ dev trc,00000] 0: name = R/3, con_id = -000000001, state = DISCONNECTED, tx = NO , bc = NO , hc = NO , perm = YES, reco = NO , frco = NO , timeout = 000, con_max = 255, con_opt = 255, occ = NO , prog = 4 ETW000 29 0.002279 4 ETW000 [ dev trc,00000] db_con_connect (con_name=R/3) 12 0.002291 4 ETW000 [ dev trc,00000] determine_block_commit: no con_hdl found as blocked for con_name = R/3 4 ETW000 16 0.002307 4 ETW000 [ dev trc,00000] find_con_by_name found the following connection: 9 0.002316 4 ETW000 [ dev trc,00000] 0: name = R/3, con_id = 000000000, state = DISCONNECTED, tx = NO , bc = NO , hc = NO , perm = YES, reco = NO , frco = NO , timeout = 000, con_max = 255, con_opt = 255, occ = NO , prog = 4 ETW000 21 0.002337 4 ETW000 [ dev trc,00000] Thread ID:3492 594 0.002931 4 ETW000 [ dev trc,00000] Thank You for using the SLODBC-interface 17 0.002948 4 ETW000 [ dev trc,00000] Using dynamic link library 'D:\usr\sap\DEV\SYS\exe\uc\NTAMD64\dbmssslib.dll' 4 ETW000 21 0.002969 4 ETW000 [ dev trc,00000] dbmssslib.dll patch info 27 0.002996 4 ETW000 [ dev trc,00000] SAP patchlevel 0 12 0.003008 4 ETW000 [ dev trc,00000] SAP patchno 200 92 0.003100 4 ETW000 [ dev trc,00000] Last MSSQL DBSL patchlevel 0 20 0.003120 4 ETW000 [ dev trc,00000] Last MSSQL DBSL patchno 200 14 0.003134 4 ETW000 [ dev trc,00000] Last MSSQL DBSL patchcomment Take care of warnings during database connect (1600066) 4 ETW000 18 0.003152 4 ETW000 [ dev trc,00000] ODBC Driver chosen: SQL Server Native Client 10.0 native 273 0.003425 4 ETW000 [ dev trc,00000] Network connection used from XXSAPDEV01 to XXSQLSAPDEV01 using tcp:XXSQLSAPDEV01 4 ETW000 128 0.003553 4 ETW000 [ dev trc,00000] Network connection used from XXSAPDEV01 to XXSQLSAPDEV01 using tcp:XXSQLSAPDEV01 4 ETW000 20908 0.024461 4 ETW000 [ dev trc,00000] Network connection used from XXSAPDEV01 to XXSQLSAPDEV01 using tcp:XXSQLSAPDEV01 4 ETW000 3485 0.027946 4 ETW000 [ dev trc,00000] Driver: sqlncli10.dll Driver release: 10.50.2769 3695 0.031641 4 ETW000 [ dev trc,00000] GetDbRelease: 10.50.2769.00 475 0.032116 4 ETW000 [ dev trc,00000] GetDbRelease: Got DB release numbers (10,50,2769,0) 18 0.032134 4 ETW000 [ dev trc,00000] ERROR: -1 in function ExecuteAndFlush (SQLExecDirect) [line 6702] 6505 0.038639 4 ETW000 [ dev trc,00000] (102) [42000] [Microsoft][SQL Server Native Client 10.0][SQL Server]Incorrect syntax near 'execute.'. 4 ETW000 27 0.038666 4 ETW000 [ dev trc,00000] failed -- connect terminated 4 ETW000 31 0.038697 4 ETW000 [ dblink ,00000] ***LOG BY2=>sql error 102 performing CON 49 0.038746 4 ETW000 [ dblink ,00000] ***LOG BY0=>[Microsoft][SQL Server Native Client 10.0][SQL Server]Incorrect syntax near 'execute.'. 4 ETW000 27 0.038773 2EETW169 no connect possible: "DBMS = MSSQL --- SERVER = 'XXSQLSAPDEV01' DBNAME = 'DEV'"
-
Addon in Client is not connecting to SQL Server 2005
Hi, we have an add-on, which is working in SBO 2005 with SQL Server 2000.
When the addon tries to connect to the same DB, restored on a SQL Server 2005, the addon is hanging up on the oCompany.Connect method. But this only happens when we try a remote connection from a SBO client.
If we run the addon from the SBO server, where the SQL Server is running too, the addon completes the connection in the expected way.
The SBO Client is connecting to the server, and works fine, but the addon is not connecting to the server.
We try to connect to the server from the client, using SQL Query Analizer from SQL Server 2000, and it works fine too.
Does anyone knows how to fix this issue?
ThanksHi Alejandro, thanks for your response.
After installing SBO Patch 20 the add-on is now connecting fine, so I think it must be an upgrade on the new DI API. I noticed the version changes from 6.80.318 to 6.80.319
I had checked the SQL to confirm is was allowing remote connections.
Thank you guys. -
Encryption is required to connect to this server but the client library does not support encryption
Hi ,guys
I came cross a trouble when I configured connection encryption.
I met the following problem when I have configured connection encryption done.
Encryption is required to connect to this server but the client library does not support encryption; the connection has been closed. Please upgrade your client library. [client: ip]
environment info:
SQL:SQL2008 \SQL2005\SQL2008R2
SERVER:WIN2003 \WIN2008R2
We use C# to develop asp.net webform app, so the provider I use should be SQL client.
client .NET Framework version:NET Framework 3.5
Pls tell me why I met this weird problem.
Thanks in advance.
Love SQLSure,here is the connetion string of java app.
jdbc
db.url=jdbc:jtds:sqlserver://60.x.x.x./TaskSiteInfo
db.username=xxx
db.pwd=xxx
Your initial post stated you were using SqlClient in an ASP.NET 3.5 app. I think this is an issue with the jTDS client based on the error message. Are you using the latest jTDS driver? If so, try posting this issue to
http://sourceforge.net/p/jtds/discussion/
Dan Guzman, SQL Server MVP, http://www.dbdelta.com -
How to connect to SQL Server (Non-SAP) in SAP R/3(Unix)?
Hi, All..
please, help me.
I am ABAPer.
I already read the text for connect DB.
but, I am not clear.
my system is,
- Source : SAP R/3, Oracle DB, Unix(OS)
- Target : Non-sap, SQL Server, Windows 2000
I want to connect to SQL Server by EXEC SQL.
Waht's BC(Basis) Jobs?
Thanks, all.Hello,
have a look at Note: 323151.
Regards
Gregor -
SAP query error - 1). [Microsoft][SQL Server Native Client 10.0][SQL Server]Conversion failed when converting date and/or time from character string. 'Received Alerts' (OAIB)
SELECT
CASE WHEN T0.DocStatus = 'O' THEN 'OPEN'
WHEN T0.DocStatus = 'C' THEN 'CLOSED' END AS 'Document Status',
T0.DocDate AS 'Posting Date',
T0.DocNum AS 'Doc.No',
T0.NumAtCard,
T0.TransId AS 'Trans. No.',
T0.Comments AS 'Remarks',
T0.CardCode AS 'Offset Acct',
T0.CardName AS 'Offset Acct Name',
sum(T0.DocTotal) + (T0.WTSum) as 'DocTotal',
T3.DueDate AS 'Cheque Date',
T3.CheckSum AS 'Amount'
FROM ODPO AS T0 LEFT OUTER JOIN
VPM2 AS T1 ON T0.ObjType = T1.InvType AND T0.DocEntry = T1.DocEntry LEFT OUTER JOIN
OVPM AS T2 ON T2.DocEntry = T1.DocNum LEFT OUTER JOIN
VPM1 AS T3 ON T2.DocEntry = T3.DocNum
where T0.DocDate>='[%0]' and T0.DocDate<='[%1]'Hi,
Try this:
SELECT
CASE WHEN T0.DocStatus = 'O' THEN 'OPEN'
WHEN T0.DocStatus = 'C' THEN 'CLOSED' END AS 'Document Status',
T0.DocDate AS 'Posting Date',
T0.DocNum AS 'Doc.No',
T0.NumAtCard,
T0.TransId AS 'Trans. No.',
T0.Comments AS 'Remarks',
T0.CardCode AS 'Offset Acct',
T0.CardName AS 'Offset Acct Name',
sum(T0.DocTotal) + (T0.WTSum) as 'DocTotal',
T3.DueDate AS 'Cheque Date',
T3.CheckSum AS 'Amount'
FROM ODPO T0 LEFT OUTER JOIN
VPM2 T1 ON T0.ObjType = T1.InvType AND T0.DocEntry = T1.DocEntry
LEFT OUTER JOIN
OVPM T2 ON T2.DocEntry = T1.DocNum LEFT OUTER JOIN
VPM1 T3 ON T2.DocEntry = T3.DocNum
where T0.DocDate >= '[%0]' and T0.DocDate <='[%1]'
group by T0.DocStatus,T0.DocDate ,
T0.DocNum ,
T0.NumAtCard,
T0.TransId ,
T0.Comments ,
T0.CardCode,
T0.CardName ,
T0.WTSum ,
T3.DueDate ,
T3.CheckSum
Thanks & Regards,
Nagarajan -
How to connect MS-sql server with SAP BW
hi all,
i want the connection procedure to how to connect MS-sql server with SAP BW.so that i can extract the data from ms sql server and can create cubes using that data.please help me in this issue.Hi Vamshi,
Go through this DOC it explains u how to connect to other data bases like SQL...
[https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/58f4db47-0501-0010-a2bf-ff01b150fdff]
this is a thread related to connect the SQL server..
[DB Connect MS SQL Server;
Regards,
NR
Assign points if helpful... -
How to Configure Remote Connections To SQL Server 2008 R2 Express
Post written June 10, 2010 and pertains to:
SQL Server 2008 R2 Express on both my server and local machines: SQLX_SRV,
SQLX_LOC
SQL Server 2008 R2 Management Studio on both my server and local machines:
MS_SRV, MS_LOC
Windows Server 2008 R2 Enterprise installed on a Hyper-V VPS: WS
SQL Server Configuration Manager on both my server and local machines:
CMGR_SRV, CMGR_LOC
Server Manager: SMGR
I am connecting to my hosting server via Remote Desktop Connection: RDC
I installed SQLX_SRV and MS_SRV on my hosting server and SQLX_LOC and MS_LOC on my local development machine. I am able to use MS_LOC to connect to SQLX_LOC and to use MS_SRV to connect to SQLX_SRV. However I am not able to use MS_LOC to connect
with SQLX_SRV. Here's what I have done so far:
SMGR -> Configuration -> Windows Firewall to turn off the Windows Firewall for Domain, Private and Public profiles. Obviously I'll change this later, but until I can connect I want to remove as many variables as possible.
CMGR_SRV -> SQL Server Services to confirm that both SQL Server (SQLEXPRESS) and SQL Server Browser services were running.
CMGR_SRV -> SQL Server Network Configuration -> Protocols for SQLEXPRESS to ENABLE the Shared Memory, Named Pipes, and TCP/IP protocols and DISABLE the deprecated VIA protocol.
CMGR_SRV -> SQL Server Network Configuration -> Protocols for SQLEXPRESS -> double click TCP/IP to open the TCP/IP properties dialogue. On the Protocol tab Enabled: Yes, Keep Alive: 30000, changed Listen All to No. I've tried it both
ways, but I've got six IP addresses on my server and I wanted to configure SQLEXPRESS to listen to only the first and primary IP. On the IP Addresses tab went to IPALL and cleared the TCP Dynamic Ports field and entered 1433 in the TCP Port field.
For my first and primary IP Address I made sure that Enabled was Yes, I cleared the TCP Dynamic Ports field, and entered 1433 in the TCP Port field. For all other IP Addresses Enabled was set to No and I cleared both the TCP Dynamic Ports and TCP Port
fields.
CMGR_SRV -> SQL Server Services -> SQL Server (SQLEXPRESS) right click and Restart. This of course stopped and restarted my instance of SQLX_SRV enabling the TCP/IP configuration in the previous step to take effect.
On my server, SQLX_SRV is the only instance of SQL Server running and so it's easy to hard wire it to the default port 1433.
The instance name for both SQLX_SRV and SQLX_LOC is the default "SQLEXPRESS". My server machine name is "SERVER1" on the EnglishBrains.com domain. So the proper local name (local within the context of my remote server as connected via RDC) for
my instance of SQLX_SRV would be:
SERVER1\SQLEXPRESS
Note the use of a backslash NOT a forward slash.
Of course to connect remotely from my development machine, which is not on the same domain as my hosting server, I would need to specify the domain as well, so the SQL Server name becomes:
SERVER1.EnglishBrains.com\SQLEXPRESS
I must also use SQL Server Authentication. Before I can use such a remote connection, however, there are still several configuration steps required. So on my server (connected via RDC) I used MS_SRV to connect to SQLX_SRV using SERVER1\SQLEXPRESS
for the server name and Windows Authentication. Once connected I performed the following steps:
MS_SRV -> right click the connected parent SERVER1\SQLEXPRESS instance node at the top -> Properties -> Security -> Server authentication: select "SQL Server and Windows Authentication mode". This will enable connections using either type
of authentication.
Next, leaving the Server Properties dialogue open, Connections -> check "Allow remote connections to this server" box.
Click OK to save these changes and close the Server Properties dialogue.
MS_SRV -> Security -> right click Logins and select "New Login...", the Login - New dialogue opens.
On the General page Enter a name for your new login
Select SQL Server Authorization
Enter and confirm a password
Uncheck Enforce password expiration
Select the default Database and Language
On the ServerRoles page Public will be checked, also check SysAdmin. This is probably not a good idea and I'll uncheck this as soon as I can connect to the SQLX_SRV.
On the User Mapping page select the databases you want your new Login to access and enter the Default Schema of "dbo".
At the bottom of the User Mapping page you'll see the Database Roles table. Public will be selected by default. Also select db_Owner. Again this is probably not a good idea, and I'll refine this once I can connect.
On the Status page confirm that "Grant" is checked under "Permission to connect to database engine" and "Enable" is checked under "Login".
Click OK to save all changes and close the Login - New dialogue.
With these steps completed you should now be able to use MS_SRV to connect to SQLX_SRV using SQL Server Authentication by supplying the name and password for your new Login. I tried this and it worked fine. Next I tried to use this same login
remotely, that is I went to my local development machine and used MS_LOC to try and connect to SQLX_SRV by using
SERVER1.EnglishBrains.com\SQLEXPRESS
and opting for SQL Server Authentication and supplying the name and password of my new login.
THIS DID NOT WORK?? Instead I get the following error message:
Cannot connect to SERVER1.EnglishBrains.com\SQLEXPRESS.
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider:
SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)
For help, click:
http://www.microsoft.com/products/ee/transform.aspx?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=-1
If you follow the suggested help link, you are told:
The SQL Server client cannot connect to the server. This error could be caused by one of the following reasons:
A specified SQL Server instance name is not valid.
The TCP, or named pipes protocols are not enabled.
The firewall on the server has refused the connection.
The SQL Server Browser service (sqlbrowser) is not started.
WRONG on all 4 counts! The instance name IS valid. Both TCP/IP and Named Pipes protocols are enabled. The firewall has been shut down, so it is not relevant. Finally the SQL Server Browser IS started.
The next thing I tried was to circumvent discovery by the SQL Browser service by using the following syntax to specify the IP address and port directly when specifying the SQL Server name.
tcp:68.71.134.186,1433
Using this in the Server Name field I was able to use MS_SRV to successfully connect to SQLX_SRV (using SQL Server Authentication of course) with or without the SQL Browser service running.
However when I tried to connect from MS_LOC to SQLX_SRV using this same login (WITH SQL Browser service running just for good measure) it does not work?? I get the following error message:
Cannot connect to tcp:68.71.134.186,1433.
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider:
TCP Provider, error: 0 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.) (Microsoft SQL Server, Error: 10060)
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=10060&LinkId=20476
If you follow the help link you are told:
"The SQL Server client cannot connect to the server. This error could occur because either the firewall on the server has refused the connection or the server is not configured to accept remote connections."
However, the firewall has been shut down and the server HAS been configured to accept remote connections!
I confirmed that i could indeed Ping to 68.71.134.186 and running NetStat -a |find /i "listening" on the server shows that the server is indeed listening at 68.71.134.186 Port 1433 -- which is why I was able to connect to SQLX_SRV using MS_SRV with
tcp:68.71.134.186,1433 .
IN SUMMARY: Even though I can connect to my SQLEXPRESS instance multiple ways from the server itself, I cannot connect remotely from my development machine!
If anyone can help me figure out why I would be very, very grateful!My two cents to help you out on c# code example to configure the remote sql server express.
Hope it helps. It works, but you have to be extra carefull to read it all and setup the server configuration and netsh commands; also the port fowarding on the router.
using System;
using System.Collections.Generic;
using System.Linq;
using System.Text;
using System.Data.SqlClient;
namespace sqlremoteconnection
class Program
static void Main(string[] args)
// this is the local sql server connection
// 192.168.1.101\SQLEXPRESS
// now, the configuration for remote access:
// activate SQL SERVER BROWSER - set it to start "automatic"; then START UP
// SQL Server Configuration Manager
// --> SQL SERVER BROWSER -> properties -> Service -> Start Mode -> automatic -> apply
// --> Log On -> Start -> Ok
// netsh firewall set portopening protocol = TCP port = 1433 name = SQLPort mode = ENABLE scope = all profile = CURRENT
// netsh firewall set portopening protocol = UDP port = 1434 name = SQLPort mode = ENABLE scope = all profile = CURRENT
// netsh advfirewall firewall add rule name = SQLPort dir = in protocol = tcp action = allow localport = 1433 remoteip = any profile = PUBLIC
// netsh advfirewall firewall add rule name = SQLPort dir = in protocol = udp action = allow localport = 1434 remoteip = any profile = PUBLIC
// VERY IMPORTANT FOR REMOTE ACCESS: you have to add the rules on port fowarding
// on the router!!!
// TCP: 1433
// UDP: 1434
// or just a personal port like TCP 31433/UDP 31434
// read carefully the netsh commands above
// server name: 123.132.24.177\SQLEXPRESS
// server name: anyurl.myftp.org\SQLEXPRESS,1433 <<-- regular port
// server name: anyurl.myftp.org\SQLEXPRESS
// server name: anyurl.myftp.org\SQLEXPRESS,31433 <<-- WOW different PORT here!!!
SqlConnection myConnection = new SqlConnection(
"user id=sa;" +
"password=password_goes_here!;" +
"server=anyurl.myftp.org\\SQLEXPRESS,31433;" +
//"Trusted_Connection=no;" +
"database=database_name_here; " +
"connection timeout=30");
try
myConnection.Open();
catch (Exception e)
Console.WriteLine(e.ToString());
try
SqlDataReader myReader = null;
SqlCommand myCommand = new SqlCommand("select * from mytable", myConnection);
myReader = myCommand.ExecuteReader();
while (myReader.Read())
Console.WriteLine(myReader["tab01_name"].ToString());
Console.WriteLine(myReader["tab01_age"].ToString());
catch (Exception e)
Console.WriteLine(e.ToString());
try
myConnection.Close();
catch (Exception e)
Console.WriteLine(e.ToString());
Adelino Araujo -
Dispatcher stopped and not able to connect with sql server
Hi ,
In one of test system disp+work is started and then within no time its stopped.
I am able to connect with sql server 2005 database but while starting sap dispatcher is stopping.
Here is the log of dev_wo
trc file: "dev_w0", trc level: 1, release: "700"
ACTIVE TRACE LEVEL 1
ACTIVE TRACE COMPONENTS all, MJ
B
B Thu Jan 05 07:24:02 2012
B create_con (con_name=R/3)
B Loading DB library 'C:\usr\sap\DE1\SYS\exe\uc\NTI386\dbmssslib.dll' ...
B Library 'C:\usr\sap\DE1\SYS\exe\uc\NTI386\dbmssslib.dll' loaded
B Version of 'C:\usr\sap\DE1\SYS\exe\uc\NTI386\dbmssslib.dll' is "700.08", patchlevel (0.72)
B New connection 0 created
M sysno 11
M sid DE1
M systemid 560 (PC with Windows NT)
M relno 7000
M patchlevel 0
M patchno 75
M intno 20050900
M make: multithreaded, Unicode, optimized
M pid 988
M
M kernel runs with dp version 217000(ext=109000) (@(#) DPLIB-INT-VERSION-217000-UC)
M length of sys_adm_ext is 572 bytes
M ***LOG Q0Q=> tskh_init, WPStart (Workproc 0 988) [dpxxdisp.c 1299]
I MtxInit: 30000 0 0
M DpSysAdmExtCreate: ABAP is active
M DpSysAdmExtCreate: VMC (JAVA VM in WP) is not active
M DpShMCreate: sizeof(wp_adm) 23936 (1408)
M DpShMCreate: sizeof(tm_adm) 3994272 (19872)
M DpShMCreate: sizeof(wp_ca_adm) 24000 (80)
M DpShMCreate: sizeof(appc_ca_adm) 8000 (80)
M DpCommTableSize: max/headSize/ftSize/tableSize=500/8/528056/528064
M DpShMCreate: sizeof(comm_adm) 528064 (1048)
M DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0
M DpShMCreate: sizeof(file_adm) 0 (72)
M DpShMCreate: sizeof(vmc_adm) 0 (1440)
M DpShMCreate: sizeof(wall_adm) (38456/34360/64/184)
M DpShMCreate: sizeof(gw_adm) 48
M DpShMCreate: SHM_DP_ADM_KEY (addr: 07F90040, size: 4659000)
M DpShMCreate: allocated sys_adm at 07F90040
M DpShMCreate: allocated wp_adm at 07F91E40
M DpShMCreate: allocated tm_adm_list at 07F97BC0
M DpShMCreate: allocated tm_adm at 07F97BF0
M DpShMCreate: allocated wp_ca_adm at 08366E90
M DpShMCreate: allocated appc_ca_adm at 0836CC50
M DpShMCreate: allocated comm_adm at 0836EB90
M DpShMCreate: system runs without file table
M DpShMCreate: allocated vmc_adm_list at 083EFA50
M DpShMCreate: allocated gw_adm at 083EFA90
M DpShMCreate: system runs without vmc_adm
M DpShMCreate: allocated ca_info at 083EFAC0
M DpShMCreate: allocated wall_adm at 083EFAC8
X EmInit: MmSetImplementation( 2 ).
X MM global diagnostic options set: 0
X <ES> client 0 initializing ....
X Using implementation flat
M <EsNT> Memory Reset disabled as NT default
X ES initialized.
M
M Thu Jan 05 07:24:03 2012
M ThInit: running on host sugarland
M
M Thu Jan 05 07:24:04 2012
M calling db_connect ...
C Warning: Env(MSSQL_SERVER) [SUGARLAND\DE1] <> Prof(dbs/mss/server) [SUGARLAND]. Profile value will be used.
C Thread ID:708
C Thank You for using the SLOLEDB-interface
C Using dynamic link library 'C:\usr\sap\DE1\SYS\exe\uc\NTI386\dbmssslib.dll'
C dbmssslib.dll patch info
C patchlevel 0
C patchno 72
C patchcomment MSSQL: Thread check in DbSlDisconnect (969143)
C np:(local) connection used on SUGARLAND
C CopyLocalParameters: dbuser is 'de1'
C Using Provider SQLNCLI
C OpenOledbConnection: MARS property was set successfully.
C
C Thu Jan 05 07:24:19 2012
C OpenOledbConnection: line 23391. hr: 0x8000ffff Login timeout expired
C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 0, sev 0), Login timeout expired
C Procname: [OpenOledbConnection - no proc]
C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 2, sev 0), An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
C Procname: [OpenOledbConnection - no proc]
C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 2, sev 0), Named Pipes Provider: Could not open a connection to SQL Server [2].
C Procname: [OpenOledbConnection - no proc]
C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 0, sev 0), Invalid connection string attribute
C Procname: [OpenOledbConnection - no proc]
C Using Provider SQLNCLI
C OpenOledbConnection: MARS property was set successfully.
C
C Thu Jan 05 07:24:34 2012
C OpenOledbConnection: line 23391. hr: 0x8000ffff Login timeout expired
C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 0, sev 0), Login timeout expired
C Procname: [OpenOledbConnection - no proc]
C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 2, sev 0), An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
C Procname: [OpenOledbConnection - no proc]
C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 2, sev 0), Named Pipes Provider: Could not open a connection to SQL Server [2].
C Procname: [OpenOledbConnection - no proc]
C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 0, sev 0), Invalid connection string attribute
C Procname: [OpenOledbConnection - no proc]
C Using Provider SQLNCLI
C OpenOledbConnection: MARS property was set successfully.
C
C Thu Jan 05 07:24:49 2012
C OpenOledbConnection: line 23391. hr: 0x8000ffff Login timeout expired
C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 0, sev 0), Login timeout expired
C Procname: [OpenOledbConnection - no proc]
C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 2, sev 0), An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
C Procname: [OpenOledbConnection - no proc]
C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 2, sev 0), Named Pipes Provider: Could not open a connection to SQL Server [2].
C Procname: [OpenOledbConnection - no proc]
C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 0, sev 0), Invalid connection string attribute
C Procname: [OpenOledbConnection - no proc]
C failed to establish conn to np:(local).
C Retrying without protocol specifier: (local)
C Using Provider SQLNCLI
C OpenOledbConnection: MARS property was set successfully.
C
C Thu Jan 05 07:25:05 2012
C OpenOledbConnection: line 23391. hr: 0x8000ffff Login timeout expired
C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 0, sev 0), Login timeout expired
C Procname: [OpenOledbConnection - no proc]
C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 2, sev 0), An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
C Procname: [OpenOledbConnection - no proc]
C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 2, sev 0), Named Pipes Provider: Could not open a connection to SQL Server [2].
C Procname: [OpenOledbConnection - no proc]
C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 0, sev 0), Invalid connection string attribute
C Procname: [OpenOledbConnection - no proc]
C Using Provider SQLNCLI
C OpenOledbConnection: MARS property was set successfully.
C
C Thu Jan 05 07:25:21 2012
C OpenOledbConnection: line 23391. hr: 0x8000ffff Login timeout expired
C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 0, sev 0), Login timeout expired
C Procname: [OpenOledbConnection - no proc]
C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 2, sev 0), An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
C Procname: [OpenOledbConnection - no proc]
C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 2, sev 0), Named Pipes Provider: Could not open a connection to SQL Server [2].
C Procname: [OpenOledbConnection - no proc]
C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 0, sev 0), Invalid connection string attribute
C Procname: [OpenOledbConnection - no proc]
C Using Provider SQLNCLI
C OpenOledbConnection: MARS property was set successfully.
C
C Thu Jan 05 07:25:37 2012
C OpenOledbConnection: line 23391. hr: 0x8000ffff Login timeout expired
C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 0, sev 0), Login timeout expired
C Procname: [OpenOledbConnection - no proc]
C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 2, sev 0), An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
C Procname: [OpenOledbConnection - no proc]
C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 2, sev 0), Named Pipes Provider: Could not open a connection to SQL Server [2].
C Procname: [OpenOledbConnection - no proc]
C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 0, sev 0), Invalid connection string attribute
C Procname: [OpenOledbConnection - no proc]
C failed to establish conn. 0
B ***LOG BY2=> sql error 0 performing CON [dbsh#2 @ 1204] [dbsh 1204 ]
B ***LOG BY0=> <message text not available> [dbsh#2 @ 1204] [dbsh 1204 ]
B ***LOG BY2=> sql error 0 performing CON [dblink#3 @ 431] [dblink 0431 ]
B ***LOG BY0=> <message text not available> [dblink#3 @ 431] [dblink 0431 ]
M ***LOG R19=> ThInit, db_connect ( DB-Connect 000256) [thxxhead.c 1411]
M in_ThErrHandle: 1
M *** ERROR => ThInit: db_connect (step 1, th_errno 13, action 3, level 1) [thxxhead.c 10156]
M
M Info for wp 0
M
M stat = 4
M reqtype = 1
M act_reqtype = -1
M rq_info = 0
M tid = -1
M mode = 255
M len = -1
M rq_id = 65535
M rq_source = 255
M last_tid = 0
M last_mode = 0
M semaphore = 0
M act_cs_count = 0
M control_flag = 0
M int_checked_resource(RFC) = 0
M ext_checked_resource(RFC) = 0
M int_checked_resource(HTTP) = 0
M ext_checked_resource(HTTP) = 0
M report = > <
M action = 0
M tab_name = > <
M vm = V-1
M
M *****************************************************************************
M *
M * LOCATION SAP-Server sugarland_DE1_11 on host sugarland (wp 0)
M * ERROR ThInit: db_connect
M *
M * TIME Thu Jan 05 07:25:37 2012
M * RELEASE 700
M * COMPONENT Taskhandler
M * VERSION 1
M * RC 13
M * MODULE thxxhead.c
M * LINE 10354
M * COUNTER 1
M *
M *****************************************************************************
M
M PfStatDisconnect: disconnect statistics
M Entering TH_CALLHOOKS
M ThCallHooks: call hook >ThrSaveSPAFields< for event BEFORE_DUMP
M *** ERROR => ThrSaveSPAFields: no valid thr_wpadm [thxxrun1.c 720]
M *** ERROR => ThCallHooks: event handler ThrSaveSPAFields for event BEFORE_DUMP failed [thxxtool3.c 260]
M Entering ThSetStatError
M ThIErrHandle: do not call ThrCoreInfo (no_core_info=0, in_dynp_env=0)
M Entering ThReadDetachMode
M call ThrShutDown (1)...
M ***LOG Q02=> wp_halt, WPStop (Workproc 0 988) [dpnttool.c 327]
Please help me on this
Thanks
SrikanthHi Amit,
I restarted the system but dispatcher still in same stage.
Here is the log for dev_w0
========================================
Fri Jan 06 03:41:06 2012
C OpenOledbConnection: line 23391. hr: 0x8000ffff Login timeout expired
C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 0, sev 0), Login timeout expired
C Procname: [OpenOledbConnection - no proc]
C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 2, sev 0), An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
C Procname: [OpenOledbConnection - no proc]
C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 2, sev 0), Named Pipes Provider: Could not open a connection to SQL Server [2].
C Procname: [OpenOledbConnection - no proc]
C sloledb.cpp [OpenOledbConnection,line 23391]: Error/Message: (err 0, sev 0), Invalid connection string attribute
C Procname: [OpenOledbConnection - no proc]
C failed to establish conn. 0
B ***LOG BY2=> sql error 0 performing CON [dbsh#2 @ 1204] [dbsh 1204 ]
B ***LOG BY0=> <message text not available> [dbsh#2 @ 1204] [dbsh 1204 ]
B ***LOG BY2=> sql error 0 performing CON [dblink#3 @ 431] [dblink 0431 ]
B ***LOG BY0=> <message text not available> [dblink#3 @ 431] [dblink 0431 ]
M ***LOG R19=> ThInit, db_connect ( DB-Connect 000256) [thxxhead.c 1411]
M in_ThErrHandle: 1
M *** ERROR => ThInit: db_connect (step 1, th_errno 13, action 3, level 1) [thxxhead.c 10156]
M
M Info for wp 0
M
M stat = 4
M reqtype = 1
M act_reqtype = -1
M rq_info = 0
M tid = -1
M mode = 255
M len = -1
M rq_id = 65535
M rq_source = 255
M last_tid = 0
M last_mode = 0
M semaphore = 0
M act_cs_count = 0
M control_flag = 0
M int_checked_resource(RFC) = 0
M ext_checked_resource(RFC) = 0
M int_checked_resource(HTTP) = 0
M ext_checked_resource(HTTP) = 0
M report = > <
M action = 0
M tab_name = > <
M vm = V-1
M
M *****************************************************************************
M *
M * LOCATION SAP-Server sugarland_DE1_11 on host sugarland (wp 0)
M * ERROR ThInit: db_connect
M *
M * TIME Fri Jan 06 03:41:06 2012
M * RELEASE 700
M * COMPONENT Taskhandler
M * VERSION 1
M * RC 13
M * MODULE thxxhead.c
M * LINE 10354
M * COUNTER 1
M *
M *****************************************************************************
M
M PfStatDisconnect: disconnect statistics
M Entering TH_CALLHOOKS
M ThCallHooks: call hook >ThrSaveSPAFields< for event BEFORE_DUMP
M *** ERROR => ThrSaveSPAFields: no valid thr_wpadm [thxxrun1.c 720]
M *** ERROR => ThCallHooks: event handler ThrSaveSPAFields for event BEFORE_DUMP failed [thxxtool3.c 260]
M Entering ThSetStatError
M ThIErrHandle: do not call ThrCoreInfo (no_core_info=0, in_dynp_env=0)
M Entering ThReadDetachMode
M call ThrShutDown (1)...
M ***LOG Q02=> wp_halt, WPStop (Workproc 0 3632) [dpnttool.c 327] -
Connect to sql server from 10g webforms using exec sql
Hi
We are embarking on a project to upgrade our 6i client server forms to 10g web
based. One of our forms uses the exec_sql package to open a connection to an MS
SQL Server database and execute queries on that database.
Oracle open client adapter and an odbc driver for SQL Server is installed on
every client to achieve this. I have read that open client adapter is no longer
available on 10g.
I also read that there a feature of the Oracle database called Generic
Connectivity which would allow us to install an odbc driver on the database
server and allow us to connect to sql server. However I discovered that this
feature is not supported on TRU64 - the operating system our database runs on.
I have read about Oracle Transparent gateways but I have been informed that they are not supported from forms.
Is there any alternative? How can our webform connect to sql server and execute
queries against it? The sql we need to execute is already sql server compliant so no translation is required - just a simple pass through
thanks
paul schweigerI used in the past Forms 6i against DB2 on a mainframe through Transparent Gateway for DB2. So I'm wondering who did you tell such a configuration does not work. And the migration guide states:
/* Open Client Adapters (OCA)
In order to provide platform-independent access to a wider range of non-Oracle data sources, use the Oracle Transparent Gateway and Generic Connectivity solutions in place of OCA. */
At least gateway is mentioned.
Werner -
Hi there,
I am having a serious issue with The Power BI Data Management Gateway which I am hoping that someone can help me with.
Basically I am setting a connection between a Power BI demo site and a SQL 2012 Database based on Azure. The Data Management Gateway and is up and running, and Power BI has managed to connect to it successfuly.
By following the tutorials at
here I was able to successful create my Data Connection Gateway with a self-signed certificate.
However, when trying to create the data source I come into problems. The Data Source Manager manages to successfully resolve the hostname, as per the screenshot below:
Bear in mind that I exposed the require ports in Azure as endpoints and I managed to modify my hosts file on my local machine so I could access the SQL server hosted in Azure using its internal name -- otherwise I would not be able to get this far.
However the creation of the data source also fails when trying to created it whilst logged in the SQL server in question:
The Data Source Manager returns the error when using the Microsoft OLE DB Provider for SQL Server:
Failed to test connection. [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied
I tried using the SQL Server Native Client 11.0 instead but I also get an error. This time the error is:
Failed to test connection. Login timeout expiredA network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.Named Pipes Provider: Could not open a connection to SQL Server [53].
Some considerations
If I provide an invalid username/password, the Data Source Manager does say that the username and password is incorrect.
Firewall is turned off in the SQL Server (either way, this error also happens if I try top use the Data Source Manager whilst logged in the SQL Server itself).
SQL Profiler does not show any attempt of connection.
The SQL server instance in question is the default one.
The error happens regardless if I select the option to encrypt connection or not.
In SQL Configuration manager I can see that all protocols are enabled (TCP/IP, Named Pipes and Shared Memory.
The Event Viewer does not provide any further errors than the one I have copied in this post.
I'm at a loss here. Could someone please advise what might I be doing wrong?
Regards,
P.Here is what I had to do to solve this issue:
Basically I had to add the MSSQL TCP/IP port as an end-point in Azure. After I did that, then I was able to create the data-source. However, I was only able to authenticate with a SQL account, as any domain account would return me an error saying that the
domain isn't trusted.
What puzzles me here is how come the Data Source Manager would inform me that an account username/password was invalid, but it would fail/timeout if I provided valid credentials (!?!?!!?) -
Re: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server
Hi,
I'm encountering an issue with "Named Pipes Provider, error: 40 windows" and am having problems determining how to fix it due to the environment I'm using. I have two SQL Servers installed on two separate Win2K3 Server boxes, one is SQL Server 2000 and the other is SQL Server 2005. The SQL Server 2000 contains the actual application data. The 2005 database is used only for Reporting Services. I've set up the reports on SSRS such that their datasources hit the 2000 server. This is using SQL Server authentication.
When testing the reports via SSRS (in Visual Studio 2005), the connection to the data works and the reports are generated fine. When I deploy them to the reporting server and launch IE to test locally (still on the 2005 box), I get this "Named Pipes Provider, error 40" issue. I made sure that Named Pipes and TCP were enabled and the port set at 1433 (to match that on the 2000 box).
Now I changed the datasource's authentication from SQL Server to Windows authentication. I tested this in SSRS and this works too. When I redeployed the reports with this authentication change, testing the reports via IE locally (on the 2005 box) worked. Great. Now when I open IE on an external box, i.e. on the 2000 box, and try to test the reports, I get this same error 40 issue. I've been through a few threads describing the error 40, fiddling around with the SQL Server configuration as well as SSRS, to no avail. I have a feeling this error 40 issue has to due with permissions/authentication between the SQL Server boxes but I can't really be sure. Anyone have any ideas on how to troubleshoot my situation. Thanks.
larryNamed Pipes Provider, error: 40 - Could not open a connection to SQL Server :
I. Incorrect connection string, such as using SqlExpress.
Check out: http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=558456&SiteID=17
https://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1245564&SiteID=1
The typical error when dealing with Express includes:
a. User is not aware of SqlExpress was installed as a named instance, consequently, in his/her connection string, he/she only specify ".","localhost" etc instead of ".\SqlExpress" or "<machinename>\Sqlexpress".
b. Np was disabld by default after installing SqlExpress.
c. If Sqlexpress was installed on the remote box, you need to enable remote connection for Express.
Please read the following blog for best practice of connecting to SqlExpress.
http://blogs.msdn.com/sql_protocols/archive/2006/03/23/558651.aspx
II. Named Pipes(NP) was not enabled on the SQL instance.
Check out: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=136253&SiteID=1
Oppose to SQL 2000 which turn on all protocols, SQL 2005 SKUs turn off NP by default. So, when you see this error, please check:
1) Go to SQL Server Configuration Manager, See Server has NP enabled.
2) %windir%\program files\microsoft sql server\mssql.1\mssql\log, notepad ERRORLOG, see whether Server is listening on NP. You should see "Server named pipe provider is ready to accept connection on [ \\.\pipe\sql\query ] or [\\.\pipe\mssql$<InstanceName>\sql\query]"
3) Notice that "sql\query" is the default pipe name, so you need to know server is listening on which pipe name. eg: if you specify server pipe name is "sql\query1", then you would see in the errorlog that server listening on [ \\.\pipe\sql\query1 ], and go to SQL Server Configuration Manager, click client Named Pipe properties, see whether the pipe name is same with the one server listening on.
4) If you are using SQL Native Client ODBC/OLEDB provider({SQL Native Client} or SQLNCLI), go to SQL Configuration Manager, click client protocols, make sure NP and TCP are both enabled. Right click properties of NP, make sure client is using the same pipe name as server for connection.
5) If you are using MDAC ODBC/OLEDB({SQL Server} or SQLOLEDB) provider, in command line, launch "cliconfg.exe" and make sure NP enabled and right pipe name specified.
III. Remote connection was not enabled.
Check out: when you right click on the Server in SQL Server Management Studio, in Connections, the Remote server connections part, you have enabled the "Allow remote connections to this server" check box
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=322792&SiteID=1
https://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=763875&SiteID=1
If you are making a remote connection, namely, your target SQL Server is on the different box as client application, you might need to check whether:
a. "File and Printer Sharing" was opened in Firewall exception list.
b. Please see the blog for enabling remote connection for express and troubleshooting tips of remote connection.
http://blogs.msdn.com/sql_protocols/archive/2005/11/14/492616.aspx
http://blogs.msdn.com/sql_protocols/archive/2006/09/30/SQL-Server-2005-Remote-Connectivity-Issue-TroubleShooting.aspx
IV. Server not started, or point to not a real server in your connection string.
Check out: Open SQL Server Surface Area Configuration and ensure all the required services are started, Remote Connections are configured.
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=348662&SiteID=1
a. use "sc query mssqlserver" for default instance or "sc query mssql$<instancename>" to make sure SQL Server was started. Sometimes, reseason behind the broken of your client application w/ this error:40 might be SQL server restarted and failed, so, it'd better for you to double check.
b. User specified wrong server in their connection string, as described in the forum discussion, "MSSQLSERVER" is an invalid instance name. Remember, when you connect to default instance, <machinename> could be best representitive for the instance, when you connect to a named instance such as sqlexpress, you should specify <machinename>\<instancename> as data source in your connection string.
V. Other reasons such as incorrect security context.
Check out: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=192622&SiteID=1
Such error also occured during user operation such as moving database or db mirroring or cluster, any DB OP that might invovle different sql instances, namely, the destination database is located in another sql instance and user is not aware of the state of the destination. I recommend you first isolate whether this fail is during connection stage or data operation stage.
a. During data operation, you are normally asked to type in the destination server name whether it is default to "(local)" or another server "<remotemachinename>". So, remember the exact string that represent the target instance, then when the error repros, open command line, use "sqlcmd -S<representitive> -E" ,see what happens, if the connection fail, please follow up above I - IV troubleshooting lists. otherwise continue.
b. If you can make basic conection, but still face the error, then there must be something that server reject the connection or client close the connection for some reason.
VI. Please try basic connectivity tests between the two mahcines you are working on. One simple way to verifty connectivity is to use command line tools, such as osql.exe. For example, osql -E -Stcpervername\instancename. If it connects cross-machine successfully, please also verify that your connection string in your scenario is correct.
Here are some blogs which could be helpful: just follow the basic connectivity troubleshooting guidelines on the SQL Protocols blog, see:
SQL Server 2005 Connectivity Issue Troubleshoot - Part I
http://blogs.msdn.com/sql_protocols/archive/2005/10/22/483684.aspx
and
SQL Server 2005 Connectivity Issue Troubleshoot - Part II
http://blogs.msdn.com/sql_protocols/archive/2005/10/29/486861.aspx
Hope this helps. -
i'm recently working on hardening of sql server 2008. now i face with a problem. my problem is how to secure connection in sql server 2008? my main problem is which certificate should i add in mmc? what are these certificates about?and guide
me in choosing the appropriate certificate.
and how should i know that the connection in sql server is secured?
plz guide me from the beginning cause i'm rookie in this subject.
thanks in advance.Hi sqlfan,
Question 1: my problem is how to secure connection in sql server 2008?
Microsoft SQL Server can use Secure Sockets Layer (SSL) to encrypt data that is transmitted across a network between an instance of SQL Server and a client application. For more information about Encrypting Connections to SQL Server, please refer to the following
article:
http://technet.microsoft.com/en-us/library/ms189067(v=sql.105).aspx
Question 2: my main problem is which certificate should i add in mmc? what are these certificates about?and guide me in choosing the appropriate certificate.
To install a certificate in the Windows certificate store of the server computer, you will need to purchase/provision a certificate from a certificate authority first. So please go to a certificate authority to choose the appropriate certificate.
For SQL Server to load a SSL certificate, the certificate must meet the following conditions:
The certificate must be in either the local computer certificate store or the current user certificate store.
The current system time must be after the Valid from property of the certificate and before the Valid to property of the certificate.
The certificate must be meant for server authentication. This requires the Enhanced Key Usage property of the certificate to specify Server Authentication (1.3.6.1.5.5.7.3.1).
The certificate must be created by using the KeySpec option of AT_KEYEXCHANGE. Usually, the certificate's key usage property (KEY_USAGE) will also include key encipherment (CERT_KEY_ENCIPHERMENT_KEY_USAGE).
The Subject property of the certificate must indicate that the common name (CN) is the same as the host name or fully qualified domain name (FQDN) of the server computer. If SQL Server is running on a failover cluster, the common name must match the host
name or FQDN of the virtual server and the certificates must be provisioned on all nodes in the failover cluster.
Question 3: how should i know that the connection in sql server is secured?
If the certificate is configured to be used, and the value of the ForceEncryption option is set to Yes, all data transmitted across a network between SQL Server and the client application will be encrypted using the certificate. For more detail about this,
please refer to Configuring SSL for SQL Server in the following article:
http://technet.microsoft.com/en-us/library/ms189067(v=sql.105).aspx
If you have any question, please feel free to let me know.
Regards,
Donghui Li -
Hi,
I have one client and one server. In both hosts I created an OS-user named User1.
The user have been given various role under the prefix SQLServer2005.
The default instance of SQL Server and instance (background-process) of
Analysis Service are also run under User1.
I connected via Management Studio to Analysis Service directly in the
server. I set the permission to access Analysis Service to Everyone.
This means everyone should be able to use Analysis Service. I have set
ODBC data source to the server. Testing was successful.
I created a project to create a cube. The tables are fairly small (total 300 MB, biggest one 290).
On project setting (created at client) I set the server host as
deployment target. I managed to deploy project when all I have are Data
Source and Data Source Views.
But on deployment I always failed. The errors remain the same, begins with
OLE DB error: OLE DB or ODBC error: [DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access denied.; 08001.
I have tried 4 combinations of Impersonation :
(A) Use a specific username and password
* in which I supply User1 and the password of User1
(B) Use the service account
(C) Use the credentials of the current user
(D) Default
Why is this? The server does certainly exist. I think the error message is wrong.
I have seen 3 posting that seems related. One of them say the solution is giving the right impersonation, but gave no detail. About the privilege, User1 are granted the role of
SQLServer2005MSOLAP. What is the solution?
Thank you,
BernaridhoI just had this problem and solved it by creating an alias in SQL Server Configuration Manager, as below:
Scenario: My SQL server is accessible from the internet under my.domain.com, and from itself at ServerName. But the local network can't see itself through the router at my.domain.com, so the deployed project is unable to process the cube, since that would
require Analysis Services to be able to see the SQL Server at my.domain.com, which it can't do.
So I changed the server in my project from my.domain.com to ServerName, and I created a local alias to ServerName in SQL Server Configuration Manager, under SQL Native Client 11.0 Configuration, Aliases. In my case, I pointed it to localhost port 1333, and
used SSH -L 1333:my.domain.com:1433, but I could have pointed the alias directly to the server, just as well. (Verifying... yes, that worked too, so you can forget SSH if you have no interest in it.) -
Hello friends..i m not able to connect MS SQL SERVER 2005 FROM cmd prompt
dear friends,
i m not able to connect MS SQL SERVER from command prompt..
do you know how to connect from command prompt or any other ways to connect to database only for delete SAP* user purpose.
thanks
zaheerHi,
you can use the SQLCMD tool:
Microsoft (R) SQL Server Command Line Tool
Version 10.50.1600.1 NT x64
Copyright (c) Microsoft Corporation. All rights reserved.
usage: Sqlcmd [-U login id] [-P password]
[-S server] [-H hostname] [-E trusted connection]
[-N Encrypt Connection][-C Trust Server Certificate]
[-d use database name] [-l login timeout] [-t query timeout]
[-h headers] [-s colseparator] [-w screen width]
[-a packetsize] [-e echo input] [-I Enable Quoted Identifiers]
[-c cmdend] [-L[c] list servers[clean output]]
[-q "cmdline query"] [-Q "cmdline query" and exit]
[-m errorlevel] [-V severitylevel] [-W remove trailing spaces]
[-u unicode output] [-r[0|1] msgs to stderr]
[-i inputfile] [-o outputfile] [-z new password]
[-f <codepage> | i:<codepage>[,o:<codepage>]] [-Z new password and exit]
[-k[1|2] remove[replace] control characters]
[-y variable length type display width]
[-Y fixed length type display width]
[-p[1] print statistics[colon format]]
[-R use client regional setting]
[-b On error batch abort]
[-v var = "value"...] [-A dedicated admin connection]
[-X[1] disable commands, startup script, enviroment variables [and exit]]
[-x disable variable substitution]
[-? show syntax summary]
You have to have the SQL Server tools installed on the box, to get sqlcmd.
You then can connect with SQL authentication
sqlcmd -S <Servername\Instancename> -U user -P password
or with windows authentication
sqlcmd -S <Servername\Instancename> -E
Best regards
Clas
Maybe you are looking for
-
My internet explorer works without any problem but I don't like using explorer I prefer Firefox please help if you can
-
I just upgraded to Firefox v32.0.1 yesterday, and I see that keyboard-created emoticons like smileys (colon +right parenthesis), winks, hearts, etc. are not displaying in Facebook on status messages or comments. This isn't just for new posts, but for
-
Where is my editable PDF content?
I have created editable business card PDF which saves perfectly. When I upload to an online printing company my editable content does not show.
-
Facing a problem with standard text in custom program
Hi, As per my requirement i need to create a standard text (transaction code s010 ) in custom program using below code. But when click save button then it needs to be come out of the screen without click back button. CALL FUNCTION 'CREATE_TEXT' E
-
Hi all, We are running B1 2005B PL6 on MSSQL Enterprise 2005 with SP1. I know that the SQL server has other product levels SP2 and SP3. Is it necessary to upgrade it to highest product level? If yes, is there any areas required to pay attention?