SQL Server Non default Instance

Hi
I believe that the Installer for the Server Package, 2005 2007 whatever isn't able to script SBO-COMMON database in an SQL instance other than the default one. Em I right?
I also believe that moving databases after having created other SQL Server instances should allow for different Servers to point to different SQL instances without experimenting any other issue across the board. Em I right?
In other words, my question is : Is there anyone out there that can confirm that a single SAP B1 site can have more than one SAP Servers, running each their own version, having their respective SBO-COMMON database under different SQL Server instances?
Thanks
Charles

Hi Paul, thanks.
This doesn't solve the whole issue, but certainly help taking good decisions for the "Patch Level(s)" aspect of it.
Thank you very much.
However, I have been testing the following lately:
sqlserver\B12005
sqlserver\B12007
both integrated as separate instances database engine. Everything, every function in B1 tested so far, including the DTW operate just fine under this architecture.
Therefore I still think that the Server Installer should allow us to deploy B1 this way, again for resource optimization purposes.
Please note that most folks attempting to integrate B1 under SQL Server Express would probably appreciate being able to install under sqlserver\SQLEXPRESS as well, which I believe will not work with the current Server Installer unless you install SQL Express by simulating a 'default' instance (that is, one without any backslash).
Thanks again !!
Charles

Similar Messages

Sql server with multiple instance

hi All,
i want to install sql server with two instance and i want to assign two separate is ips for both default instance and named instance and both should work like
two different server
note: If i logged with one ip(default instance) it should show its own databases not both or named instance databases
thanks
chintala

Hi chintala,
According to your description, if you want to assign the two different IP to stand for default instance
and named instance, I recommend you set up aliases on a SQL Server with multiple instances. For example, a physical server is named WinServer and 2 instances of SQL Server named WinServer and WinServer\instance1.
We need to add 1 IP addresse to the WinServer, there is one IP address already assigned to WinServer, 192.168.1.1, by adding one new IP's, 192.168.1.2 .
We need to move into DNS to configure our host names and aliases. The physical machine must be steup as a static IP in DNS. SQLAlias1, which point to the default instance on WinServer, will be setup as a DNS with an address of 192.168.1.1.
SQLAlias2, which will point to WinServer\Instance1, will be setup as a new Host (A) record in DNS with an address of 192.168.1.2.
When everything has been completed on the DNS side, you need to open up SQL Server Configuration Manager on WinServer and configure the protocols for each instance one at a time, restart the 3 SQL services.
For more information about how to set up aliases on a SQL Server with multiple instances, you can review the similar article.
http://kevine323.blogspot.com/2013/08/setting-up-aliases-on-sql-server-with.html
Regards,
Sofiya Li
Sofiya Li
TechNet Community Support

TF255186: The following SQL Server Reporting Services Instance could not be found

Hi,
I'm trying to install TFS 2013 on a remote SQL RS instance.
Using the TFS 2103 U4 installation
SQL 2012 RS, name instance, Server: SQLProdA, Instance Name COMRS
When I enabled tracing using debugView I see the following output:
[4160] [Error @11:07:10.978] Exception Message: TF255186: The following SQL Server Reporting Services Instance could not be found: COMRS. The server name is: SQLProdA. (type TfsAdminException)
Any ideas what the issue is?
Thanks,
reuvy

Hi Charles,
Thanks for the help. I already saw those links, and am already trying with the format. As I wrote above:
Server: SQLProdA, Instance Name COMRS
So I wrote in the box "SQLProdA\COMRS" (without quotes of course) and I still keep getting that error.
I don't know if it matters, but although this is indeed a named instance, nonetheless, the path to the report server uses the default url (ie.
http://servername/reports) as opposed to the name instance version (ie.
http://servername_instance/reports) as mentioned by your link and this post:
https://msdn.microsoft.com/en-us/library/bb552341.aspx
But, I checked with Fiddler on the server and didn't see it trying to even access the link so I don't think it is related. I saw with Process Monitor that it is indeed trying to access via the network resources on SQLProdA, so I know it's trying.
I have noticed something in the past, and wondered if this could be the issue, that for example if I have Management Studio 2014 installed, I cannot connect to a Reporting Services instance which is 2012. Only when Management Studio 2012 is installed
and being used can I connect. I wondered if this possibly could be related, that maybe the API or something else which the installer is using is missing some component to connect to the RS instance.
Just in case, I already installed both the SQL 2012 and 2014 Client Tools Connectivity (although I first installed 2014, and then 2012).
Do you think this could be the issue? If not, do you possibly have any other leads?
Thanks,
Reuvy

SCCM central site and primary site use the same SQL SERVER with two Instance.

Hi Guys,
I want deploy SCCM 2012 central site and primary site in my domain. But Only one Sql server for me. Any one can tell me how to install the central site server and primary site server with the same SQL SERVER with two instance.
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
Sean Xiao
TechNet Community Support

Although you can install like the configuration you said above, we do not recommend you do it this way. If your SQL box has problems, all the data will go away and you will not have data redundancy.
You need to configure the different SQL Port and SQL Broke service port e.g.
SQL port 4023 SQL Broke Service port 4022 for CAS instance
SQL port 4024 SQL Broke Service port 4021 for PRI instance
Juke Chou
TechNet Community Support
I agree with Johan and this configuration should not be used. But I want to clarify that the default ports for "SQL port" (actually, SQL over TCP) is 1433 and the SQL Broker Service uses 4022. The configuration above should work but the "correct" would be
to use 1433 and 4022 for the CAS and 10434 and 4023 for the Primary :)
You can read more about Network Ports used by Configuration Manager here
http://technet.microsoft.com/en-us/library/hh427328.aspx#BKMK_CommunicationPorts
/Tim
Tim Nilimaa | Blog: http://infoworks.tv | Twitter: @timnilimaa

SQL Server 2012 Express Instance is Not Discovered

I have a single SQL Server 2012 Express instance that is the backend database for a small door security application. I just noticed after having deployed the OpsMgr agent months ago that it never discovered the SQL instance. The SQL instance
is, as stated, Express, and it's the only Express instance I have. Is that why it is not discovered? All the documentation I found seems to indicate the opposite -- that Express is discovered and there are steps you can take to exclude Express
instances. I have no overrides set to exclude any instance or any database.
- System Center Operations Manager 2012 RTM (no SP1, no R2)
- SQL Server 2012 MP version 6.3.173.1
- SQL Server is Windows Server 2012
- SQL Server 2012 Express running on a Hyper-V VM. Instance is named DOORSERVER\Eclipse
- Agent is installed and other discoveries seem to be working fine
- No discovery errors in the event log related to SQL, although there is one about the Windows Server 2008 discovery not being able to start, but I'm on Windows Server 2012, so I am guessing that's okay?
- No overrides are set on the discovery
- Discovery has found every other SQL Server 2012 instance (standard and enterprise editions)

Well, just realized I didn't have the latest MP. Upgrading to 6.4.1.0 version of the SQL MP fixed the discovery issue.

How to hide not all but a specific database on a SQL Server 2008 R2 instance?

Hello everyone,
I need help from all the SQL Server database security experts out there. Any solution/help or work-around will be really appreciated. Here is the scenario; our client is using our application which is a windows forms application
having in backend as a database under SQL Server 2008 R2 instance. We have successfully installed the SQL Server software with mixed mode authentication on client side, our application is running smoothly and everything is working fine. Our database on which
application is running is quite intuitive, in the sense, all employees information is stored in EmployeeMaster and all departments information is stored in DepartmentMaster and so on. It consists of more than 500 such tables, stored-procedures and views. We
have encrypted stored-procedures and views, problem is only with tables.
We don't want table structure to be visible to anybody in SSMS (or tables must be hidden from all the users) but at the same time the tables should be accessible from the application. And we don't want to go with the option of encrypting
the tables data and changing the names of all the tables to T001,T002..etc. as that is not feasible. And one last thing, we cannot restrict 'sa' login's password, it has to be shared with the client.
Regards,
Sumit R. Santani

Also, will you please enlighten me more on what you said as "couple of choices" if I want to lock out plain users only?
Assuming that you are selling a solution to a client, it's more an issue for your client's IT department, that do want their users to connect with Excel or SSMS.
Anyway, I have a brief overview here:
http://www.sommarskog.se/grantperm.html#Othermethods
Again my question on that is how much reliable will be that license agreement?
That depends on the lawyer you engage to write the license agreement.
How would I come to know what they are doing with our database?
Trust. Trust is extremely important. It is very difficult to make business if you don't trust people.
That said, there are basically two reasons you want to hide the application from the client. One is protecting intellectual property. To this end, I know of nothing else than trust. And maybe after all, your application is not so fantastic that it is worth
stealing anyway.
The other reason is that you don't want the client to change it, and then open a free support case when he has messed up. To this end there are some technical approaches you can take to detect such tampering. For instance, you can sign all stored procedures
with certificates using ADD SIGNATURE WITH SIGNED BLOB, and then ship only the public key of the certificate. This permits SQL Server to verify the signature, but the client cannot change the signature and sign it with that certificate, because the private
key is not available to them.
Erland Sommarskog, SQL Server MVP, [email protected]

Can a SQL Server Failover Cluster Instance (FCI) be Implemented Between Two Hyper-V Hosted Virtual Machines?

I haven't had the opportunity to implement a SQL Server Failover Cluster Instance (FCI) for over 10 years and that was done with two physical, identical database servers way back in the day of Windows Server 2003 and SQL Server 2000 (old school).
Can a SQL Server 2008 R2 Failover Cluster Instance (FCI) be implemented between two Hyper-V hosted virtual machines? The environment in question already has Windows Server 2012 R2 Hyper-V hosts in place, so I'm just looking to see if this is even
possible and/or supported when utilizing virtual machines.
The client in question is currently using SQL Server 2008 R2 instances running on Win2008R2, Win2012, and Win2012R2, but I'd also be interested how this can be done or not with SQL Server 2012 or 2014 as well. Thanks in advance.
Bill Thacker

Yes, it can be done with Hyper-V guests. In fact, with Windows Server 2012 R2 Hyper-V, guests can use the Shared VHDX feature for shared storage used by Windows clusters. The guests can run Windows Server 2008 and higher provided that the Hyper-V Integration
Services are installed to support Shared VHDX. The only challenge here is making the Hyper-V hosts highly available as well, running it on WSFC.
Edwin Sarmiento SQL Server MVP | Microsoft Certified Master
Blog |
Twitter | LinkedIn
SQL Server High Availability and Disaster Recover Deep Dive Course

What is the recommended static port range for SQL Server 2008 to SQL Server 2014 named instance?

I want to assign a static port to SQL Server 2008 to SQL Server 2014 named instance. Should the port be greater than 49151? The following links give contradicting information:
https://msdn.microsoft.com/en-us/library/ms177440(v=sql.105).aspx
Avoid numbers greater than 49151 which Windows might select for other purposes.
https://technet.microsoft.com/en-us/library/ms345327(v=sql.100).aspx
Port numbers should be assigned from numbers 49152 through 65535
Thanks..

I would still pick a port number below the ephemeral list (dynamic port usage [41952-65535]) as it'll reduce the chances of having a port collision when SQL Server starts up.
Also, I'd stick to lower numbers if possible (<25,000) as some firewalls skew higher port numbers to be more malicious (if heuristics are used).
-Sean
The views, opinions, and posts do not reflect those of my company and are solely my own. No warranty, service, or results are expressed or implied.

Unable to set (ssl) certificate on a SQL Server 2012 clustered instance

Hello everyone!
I'm trying to encrypt the SQL Server communication with SSL but I can't add the certificate in the configuration manager. I've found and tried a lot of different explaination but none of them worked. I'll described what I've done and hope someone will point
out what I'm missing.
Here is my situation:
- SQL Server 2012 Enterprise Edition. Instance name = INSTANCE, FQDN = SQINSTANCE.mydomain.com. The instance is running under a customized service account: mydomain\sql_sa
- Two cluster nodes running Win Server 2008R2: NODE1.mydomain.com and NODE2.mydomain.com. Cluster itself is CLUSTER.mydomain.com
What I've done:
1) Asked the team in charge to generate a certificate issued to "SQINSTANCE.mydomain.com" with aliases to "NODE1.mydomain.com", "NODE2.mydomain.com" and "CLUSTER.mydomain.com". I get a certificate with "p7b"
as extension
2) Connect on "NODE2.mydomain.com" with account "mydomain\sql_sa". Opened MMC and added the certificate under "Personnal" folder. I tried to add it with "Current user" and "Local computer" settings. Saw both
on internet since I use a specific service account
3) Get the thumbprint of the certificate and add it under HKLM\Software\Microsoft\Microsoft SQL Server\MSSQL11.INSTANCE\MSSQLServer\SuperSocketNetLib\Certificate. (I triple checked to remove blanks or special characters)
4) Reboot the node
5) Open the SQL Server Configuration Manager, go to the network properties. Certificate does not appear in the list
I tried to check with certutil and saw the certificate in the output. Some guys talked about some private key but I don't see this particularity in my situation. I tried to check if the certificate is valid and, according to the criterias, it is.
Does anyone can help me with this?

Hi,
Are you sure you've got the certificate correct? http://msdn.microsoft.com/en-us/library/ms191192.aspx
To use encryption with a failover cluster, you must install the server certificate with the fully qualified DNS name of the virtual server
on all nodes in the failover cluster. For example, if you have a two-node cluster, with nodes named test1.<your
company>.com and test2.<your
company>.com, and you have a virtual server named virtsql, you need to install a certificate for virtsql.<your
company>.com on both nodes. You can set the value of the ForceEncryptionoption
toYes
In your case, shouldn't it be created for CLUSTER.mydomain.com?
Thanks, Andrew
My blog...

Crystal Reports 9 and SQL Server 2005 default parameter values

We're using Crystal Reports 9 and upgraded from SQL Server 2000 to SQL Server 2005.
I'm noticing a very weird problem which I wonder if anyone else has experienced (and hopefully found a resolution for). It appears that in using Crystal with SQL Server 2005 stored procedures, if we have default parameter values in the stored procedures, the default parameter values get completely ignored if you pass in a NULL value from Crystal!
For example, if you have a stored procedure that begins like this:
ALTER Procedure [dbo].[StoredProcedure]
@Param1 VarChar(200) = '',
@Param2 VarChar(200) = ''
AS ...
both @Param1 and @Param2 have a default value of an empty string, and therefore should become empty strings if nothing (NULL values) gets passed in for them.
But, like I said, what I'm finding is that with Crystal calling the stored procedure with NULL @Param1 and @Param2 values, they never become empty strings, but rather remain as NULLs.
This was never a problem with SQL 2000.
Very perplexing. Anyone else every experience this?
Thank you.

Please ignore my earlier post -- answered my own question.
NULL parameter values do not get replaced by default values in SQL -- that is normal behavior in both SQL 2000 and SQL 2005. Just goes to show, that no many how many years programming experience you have, you can still get tripped up sometimes : (

SQL Server Express 2008 instance fails to start

I've installed SQL Server Express with a named instance 'SQLSERVER2'. I was able to connect to it and reference it in the management studio. There was a problem though with Visual Studio 9 when running an ASP.NET web application that required connecting to the same instance. So, I went into the configuration manager to change the security level of the instance from network to local service. The change went through but could not restart the instance. That is what has created my next round of problems. I can't go in and change it back to network because the instance is permanently stopped. I cannot start it with the services manager. How can I fix this?
Here is the connection log:
2009-12-21 11:36:32.20 Server      Microsoft SQL Server 2008 (RTM) - 10.0.1600.22 (Intel X86)
Jul 9 2008 14:43:34
Copyright (c) 1988-2008 Microsoft Corporation
Express Edition with Advanced Services on Windows NT 5.1 <X86> (Build 2600: Service Pack 3)
2009-12-21 11:36:32.50 Server      (c) 2005 Microsoft Corporation.
2009-12-21 11:36:32.51 Server      All rights reserved.
2009-12-21 11:36:32.51 Server      Server process ID is 21856.
2009-12-21 11:36:32.51 Server      Authentication mode is MIXED.
2009-12-21 11:36:32.53 Server      Logging SQL Server messages in file 'c:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS2\MSSQL\Log\ERRORLOG'.
2009-12-21 11:36:32.89 Server      This instance of SQL Server last reported using a process ID of 3216 at 12/18/2009 6:06:56 PM (local) 12/19/2009 2:06:56 AM (UTC). This is an informational message only; no user action is required.
2009-12-21 11:36:32.89 Server      Registry startup parameters:
-d c:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS2\MSSQL\DATA\master.mdf
-e c:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS2\MSSQL\Log\ERRORLOG
-l c:\Program Files\Microsoft SQL Server\MSSQL10.SQLEXPRESS2\MSSQL\DATA\mastlog.ldf
2009-12-21 11:36:33.26 Server      SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2009-12-21 11:36:33.29 Server      Detected 2 CPUs. This is an informational message; no user action is required.
2009-12-21 11:36:35.15 Server      Using dynamic lock allocation. Initial allocation of 2500 Lock blocks and 5000 Lock Owner blocks per node. This is an informational message only. No user action is required.
2009-12-21 11:36:36.64 Server      Node configuration: node 0: CPU mask: 0x00000003 Active CPU mask: 0x00000003. This message provides a description of the NUMA configuration for this computer. This is an informational message only. No user action is required.
2009-12-21 11:36:37.42 spid6s      Starting up database 'master'.
2009-12-21 11:36:38.98 spid6s      FILESTREAM: effective level = 0, configured level = 0, file system access share name = 'SQLEXPRESS2'.
2009-12-21 11:36:39.40 spid6s      SQL Trace ID 1 was started by login "sa".
2009-12-21 11:36:39.50 spid6s      Starting up database 'mssqlsystemresource'.
2009-12-21 11:36:39.59 spid6s      The resource database build version is 10.00.1600. This is an informational message only. No user action is required.
2009-12-21 11:36:40.14 spid10s     Starting up database 'model'.
2009-12-21 11:36:40.17 spid6s      Server name is 'USER-F19E13BA9B\SQLEXPRESS2'. This is an informational message only. No user action is required.
2009-12-21 11:36:40.56 spid6s      Informational: No full-text supported languages found.
2009-12-21 11:36:40.57 spid6s      Starting up database 'msdb'.
2009-12-21 11:36:40.60 Server      Error: 17190, Severity: 16, State: 1.
2009-12-21 11:36:40.60 Server      FallBack certificate initialization failed with error code: 1.
2009-12-21 11:36:40.70 Server      Unable to initialize SSL encryption because a valid certificate could not be found, and it is not possible to create a self-signed certificate.
2009-12-21 11:36:40.71 Server      Error: 17182, Severity: 16, State: 1.
2009-12-21 11:36:40.71 Server      TDSSNIClient initialization failed with error 0x80092004, status code 0x80. Reason: Unable to initialize SSL support. Cannot find object or property.
2009-12-21 11:36:40.71 Server      Error: 17182, Severity: 16, State: 1.
2009-12-21 11:36:40.71 Server      TDSSNIClient initialization failed with error 0x80092004, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. Cannot find object or property.
2009-12-21 11:36:40.71 Server      Error: 17826, Severity: 18, State: 3.
2009-12-21 11:36:40.71 Server      Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error log.
2009-12-21 11:36:40.71 Server      Error: 17120, Severity: 16, State: 1.
2009-12-21 11:36:40.71 Server      SQL Server could not spawn FRunCM thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

Hi,
This problem can occur if the new Service Account does not have a profile on the machine. To resolve the issue connect to the SQL Server machine using the New Service account. This will create a profile for the user.
SQL Server creates a self-generated certificate if a certificate is not explicitly specified and/or is not installed. This information is saved in the profile for the SQL Server service account. If the profile has not been created then SQL cannot register the self-generated certificate.
If there are any more questions, please let me know.
Thanks.
***Xiao Min Tan***Microsoft Online Community***
What 'New Service account' are you referring to? SQL Server Express resides on my PC where I'm logged on as administrator. I don't know what you mean by connecting to the server. I only know about connecting to the database instance which is the root of the this problem because it can't be started. Sorry for my confusion...

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

[Forum FAQ] The Reporting Server cannot be reinstalled on a same SQL Server Reporting Service instance

Symptom: Sometimes, when you want to reinstall the Reporting Server Role for Operation Manager 2012,
but you may encounter an issue that the Reporting Server Role cannot be reinstalled after you successfully uninstall it. When you check the System Center Operation Manager installation log, you can find the following error as shown in Figure 1.
Figure 1: Reporting Server Role cannot be reinstalled
It seems that the SQL Server Reporting Service has not been configured properly. When you open Reporting Services Configuration Manager to check the settings, the settings seem fine though.
Even you recreate Reporting Service Database, the error remains.
After reviewing the OpsMgrSetupWizard.log, we get the following errors when wizard try to connect to SQL Server Reporting Instance (Figure 2).
[07:24:05]: Error: :CheckHttpAddressResponse failed: Threw Exception.Type: System.Net.WebException, Exception Error Code: 0x80131509, Exception.Message:
The remote server returned an error: (500) Internal Server Error.
[07:24:05]: Error: :StackTrace: at System.Net.HttpWebRequest.GetResponse() at Microsoft.EnterpriseManagement.OperationsManager.Setup.ReportingComponent.CheckHttpResponseFromSRSUrl(String
httpSite)
Figure 2: Error Log -1
It indicates the Reporting Service encounters an internal error. The Website cannot handle the request. So you may check the Reporting Service log which is located in C:\Users\Administrator.SCOM2012\AppData\Local\SCOM\LOGS
and the following errors may be found (Figure 3).
library!ReportServer_0-18!1448!03/30/2014-02:53:23:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException:
Unable to load assembly Microsoft.EnterpriseManagement.Reporting.Security, Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: The report server has encountered a configuration error. ---> System.IO.FileNotFoundException:
Could not load file or assembly 'Microsoft.EnterpriseManagement.Reporting.Security' or one of its dependencies. The system cannot find the file specified.
File name: 'Microsoft.EnterpriseManagement.Reporting.Security'
Figure 3: Error Log -2
Reason: After the Reporting Server is installed on a SSRS instance, the Reporting Server of SCOM
needs to modify the web.config and rsreportserver.config file to add its own assembly to make the Reporting Server work. But it does not change it back when Reporting Server is uninstalled. So the assembly cannot be loaded and the SSRS cannot respond
our requests.
Resolution: When the Reporting Server is installed, the old web.config and rsreportsserver.config
files will be backed up to web.config1 and rsreportsserver.config1. So you just need to change the files’ name back, then try to install Reporting Server of SCOM again. Everything would go smoothly.
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

Hi AakashGhare,
According to your error message, SQL Server 2008 databases are version 655. SQL Server 2008 R2 databases are 661. When you are trying to attach an 2008 R2 database (v. 661) to an 2008 instance and this is not supported. As other post, once the database has
been upgraded to an 2008 R2 version, it cannot be downgraded. You'll have to either upgrade your 2008 SP2 instance to R2, or you have to copy out the data in that database into an 2008 database (such as using the data migration wizard).
In addition, if you want to use a Windows Batch file code and command to automatically login to SQL Server, detach database and attach a new one database, there is a similar details about batch code for attaching database to a new database, you can refer
to this article.
http://notesbyparth.wordpress.com/2012/06/29/run-sql-commands-from-windows-batch-file-or-attachdetach-database-automatically-using-batch-script/
Regards,
Sofiya Li
Sofiya Li
TechNet Community Support

Configure SSL SQL Server 2012 Cluster Instance

Hi,
I am trying to configure a SSL Certificate on a named clustered instance but i can't
This is the errorlog message
2014-12-11 14:28:51.49 spid10s Error: 17182, Severity: 16, State: 1.
2014-12-11 14:28:51.49 spid10s TDSSNIClient initialization failed with error 0xd, status code 0x38. Reason: An error occurred while obtaining or using the certificate for SSL. Check settings in Configuration
Manager. The data is invalid.
2014-12-11 14:28:51.49 spid10s Error: 17182, Severity: 16, State: 1.
2014-12-11 14:28:51.49 spid10s TDSSNIClient initialization failed with error 0xd, status code 0x1. Reason: Initialization failed with an infrastructure error. Check for previous errors. The data is invalid.
2014-12-11 14:28:51.49 spid10s Error: 17826, Severity: 18, State: 3.
2014-12-11 14:28:51.49 spid10s Could not start the network library because of an internal error in the network library. To determine the cause, review the errors immediately preceding this one in the error
log.
2014-12-11 14:28:51.50 spid10s Error: 17120, Severity: 16, State: 1.
2014-12-11 14:28:51.50 spid10s SQL Server could not spawn FRunCommunicationsManager thread. Check the SQL Server error log and the Windows event logs for information about possible related problems.

Hi Jame,
According to your description, you encountered the error when you were trying to configure a named clustered instance to use SSL certificate.
Based on my research, the error 17182 "TDSSNIClient initialization failed with error 0xd, status code 0x38" occurs specifically because of the fact that the string under Certificate value cannot be properly converted back to a valid thumbprint
of the certificate.
A common root cause for these symptoms is an invisible character that may have been inadvertently added to the certificate's Thumbprint value, when it gets copied out of the Certificates snap-in's rich-edit control in MMC. For example, if the thumbprint
contains the Unicode character, then it may cause this issue, the following similar issue is for your reference:
http://blogs.msdn.com/b/sqljourney/archive/2013/07/23/when-using-ssl-sql-failover-cluster-instance-fails-to-start-with-error-17182.aspx
For more details and the resolution about this issue, please refer to the following article:
https://support.microsoft.com/kb/2023869?wa=wsignin1.0
If you have any question, please feel free to let me know.
Regards,
Jerry Li

JDBC Connection String for MS Sql Server 2000 with Instance Name

Hi All,
I am having problems connecting to a MS Sql Server 2000 database using MSSqlServer4
driver when the database server has an Instance Name. If the database server has
no instance name then I am able to connect using the connection string
connection=jdbc:weblogic:mssqlserver4:hansa:1433
But when I have the MS Sql Server DB with an instance name such as "TestInstance",
then I am unable to connect with any of the connection strings given below
connection=jdbc:weblogic:mssqlserver4:hansa\TestInstance:1433 or
connection=jdbc:weblogic:mssqlserver4:hansa\\TestInstance:1433 or
connection=jdbc:weblogic:mssqlserver4:hansa:TestInstance:1433 or
connection=jdbc:weblogic:mssqlserver4:hansa:1433:TestInstance
Can anybody help me in resolving this issue. Appreciate your help.
Thanks in advance.
Vikram

Vikram wrote:
Hi All,
I am having problems connecting to a MS Sql Server 2000 database using MSSqlServer4
driver when the database server has an Instance Name. If the database server has
no instance name then I am able to connect using the connection string
connection=jdbc:weblogic:mssqlserver4:hansa:1433
But when I have the MS Sql Server DB with an instance name such as "TestInstance",
then I am unable to connect with any of the connection strings given below
connection=jdbc:weblogic:mssqlserver4:hansa\TestInstance:1433 or
connection=jdbc:weblogic:mssqlserver4:hansa\\TestInstance:1433 or
connection=jdbc:weblogic:mssqlserver4:hansa:TestInstance:1433 or
connection=jdbc:weblogic:mssqlserver4:hansa:1433:TestInstance
Can anybody help me in resolving this issue. Appreciate your help.Hi. No type-4 jdbc driver is going to be able to use a name for a DBMS instance.
Let's assume you have two DBMS instances running on the machine hansa. One
of them may be listening for tcp connections on port 1433, but the other must not.
The other most be listening on some other port number you have chosen.
Therefore, to choose which DBMS instance you want to connect to, use the
working URL you have, and switch the port number as desired.
Joe Weinstein
>
>
Thanks in advance.
Vikram

SQL Server Non default Instance

Similar Messages

Maybe you are looking for