Reporting Point over remote multiple instance SQL Server

Hi,
The scenario is the following:
1 CAS SCCM 2012 R2
1 Primary SCCM 2012 R2
1 SQL Server 2012 SP2. 2 Instances. Each instance has Database Engine Services and Reporting Services - Native.
The CAS and Primary installation was OK.
The reporting point for CAS (default SQL instance) installation was OK.
The reporting point for Primary (named SQL instance) installation is not possible. The reports node at SCCM console is empty. Both of the SRS instances was automatically configured, at installation (Install and Configure).
The question is:
Is it possible to use the same SRS to host 2 reporting points? (1 for CAS, 1 for Primary. Each at different instance)
Thanks in advance!

Hi,
At another customer I get the same scenario. They want to use the same server for hosting DBs and reports for CAS site and 2 Primary sites.
The message is:
Site Component Manager detected that site system "\\ECBPPRQSM.MYDOMAIN.NET" is currently in use by ConfigMgr site CAS.
Possible cause: You accidentally configured this site system as part of this site and as part of site CAS.
Solution: Remove this site system from the list of site systems for this site or for site CAS.
The question remains basically the same:
Is it possible to use the same SRS to host 3 reporting points? (1 for CAS, 2 for Primary. Each at different instance)
Thanks in advance!

Similar Messages

Applying Service Pack on multiple instance SQL Server 2008 R2 Cluster and Standalone.

Friends,
Its my first time I am applying Service pack to both Standalone and Clustered SQL 2008 R2 servers. I have multiple instances running on both stand alone and Clustered environment. I don't know how to apply pack with multiple instances. Do I need to apply
the service pack each instance one by one or I can just run the pack to each node of cluster and each box of stand alone server? Will I get any multi instance selection option during the installation process so that I can select multiple instances at once??

When installing service pack for multiple instances in a standalone machine, you just run the installer and it lists all the instances eligible for the update. You could do it one by one or do it at the same time. Doing it at the same time saves time and
energy. If you selected multiple instances then you dont have to do anything else.
In case of cluster, if you have multiple instances then you need to be little careful.
Eg: Assume you have a 2 node cluster Node 1 and Node 2. Two instances Instance 1 active on Node 1 and Instance 2 active on Node 2. What I would do in this case is to first failover any one instance to the passive node. Assume I failed over Instance 2 to
Node 1. Now Node 1 is active node for both instance 1 and instance 2 and Node 2 is passive for both instances. At this point I run the service pack on Node 2. Once patching is done, I reboot the node and then failover the instaces one by one to Node
2. At this point both instances 1 and 2 would get upgraded and will be active in Node2. Now Node 1 is passive and so run the update there. Once the service pack is installed, reboot and then fail back Instance 1 back to Node 1. Note: I would also failover
Instance 2 to Node 1 just to confirm that failover works completely after service pack update.
Regards, Ashwin Menon My Blog - http:\\sqllearnings.com

Multiple instance SQL Server not working between VM's

I'm working with SQL Server 2014 running on Windows Server 2012 R2 Azure VM and having problems connecting to the SQL Server instance from a Windows Server 2012 R2 VM running IIS. The connection string and setup is the same as I have been using for several
years. The main difference is I am now running multiple instances on the SQL Server. Firewall is configured properly, SQL is in mixed authentication mode, configuration is identical to all the servers as ones configured in the past. Would there be anything
in the Virtual Network or in Azure that needs configured?

Is this VM deployed in a Virtual Network? If so, make sure to use static IPs, so that, in case the VM is rebooted, the IP remains constant. If not, this may be the cause of your problem, the IP will change when the VM reboots.
If you've tried to connect to the VM from outside the Virtual Network, then you need to create an endpoint for the SQL port. This needs to be configured for each instance of SQL Server on the VM.

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

Why SCCM 20012 Install fails with remote 64 bit SQL Server but proceeds for remote 32 bit SQL Server

I have the following setup:
AD User accounts
- SQLAdmin (used to run SQL Services i.e. Database Engine)
- SCCMADmin (used to install SCCM 2012)
SPN registered for user account SQLAdmin
setspn -S MSSQLSvc/SQL.Domain_Name:1432 Domain_Naem\SQLAdmin
setspn -S MSSQLSvc/SQL:1432 Domain_Name\SQLAdmin
setspn -S MSSQLSvc/SQL.Domain_Name:1433 Domain_Naem\SQLAdmin
setspn -S MSSQLSvc/SQL:1433 Domain_Name\SQLAdmin
and checked with setspn -L TESTING\SQLAdmin
1 SERVER called SQL
32bit Server with SQL Server 2008 + SP3 + Cumulative Update 6
2 SQL instances - Default (MSSQLSERVER) and
SCCM2012
MSSQLSERVER instance uses TCP port 1433
SCCM2012 Instance users TCP port 1432 (no dynamic ports)
User accounts that have been given public and sysadmin SQL server roles
on both instances are: SQLAdmin, SCCMAdmin, Domain Administrator, Local Administrator and computer account SCCM
Client Protocols TCP enabled (and Named Pipes) (checked via SQL Server Configuration Manager)
Local Administrators Group on this server has members - SQLAdmin, SCCMAdmin, Domain Administrator, Local Administrator and computer account SCCM
Firewall turned on with access allowed on Ports 1432, 1433, 4022,445, and WMI - WMI-in, DCOM-in and ASync-iN builtin rules allowed\enabled.
1 SERVER called SQL3
64bit Server with SQL Server 2008 + SP3 + Cumulative Update 6
2 SQL instances - Default (MSSQLSERVER) and
SCCM2012
MSSQLSERVER instance uses TCP port 1433
SCCM2012 Instance users TCP port 1432 (no dymanic ports)
User accounts that have been given public and sysafmin SQL server roles on both instances are:
SQLAdmin, SCCMAdmin, Domain Administrator, Local Administrator and computer account SCCM
Client Protocols TCP enabled (and Named Pipes) (checked via SQL Server Configuration Manager)
Local Administrators Group on this server has members - SQLAdmin, SCCMAdmin, Domain Administrator, Local Administrator and computer account SCCM
Firewall turned off
1 SERVER called SCCM
64bit Server that is to be the Primary Site Server\MP for SCCM 2012
ODBC link to SQL\SCCM2012,1432
ODBC link to SQL3\SCCM2012,1432
ODBC uses SQL Native Client 10.0 (64 bit)
Both ODBC connections when TESTed pass and suggest connectivity to SQL Servers
Install process doe SCCM2012
Tried to install SCCM 2012 RC2 when logged in to SCCM Server as AD user account
SCCMAdmin, and when utilising the SCCM2012 SQL instance on
32 bit server of SQL install proceeds barring warning about 8GB rec, for SQL Server. Then fails on PKI certificate issue. Installation (chose HTTP for MP). I beleive the PKI failure as install starts is
due to the fact that SCCM 2012 needs its database server to b 64 bit ?
Thus i then tried to install SCCM 2012 RC2 when logged in to SCCM Server as AD user account SCCMAdmin, and
when using the SCCM2012 SQL instance on
64 bit server of SQL install proceeds but fails at checking stage and says:
SQL Server sysadmin rights FAILED SQL3.Domain_Name
Either the user account running Configuration Manager Setup does not have sysadmin SQL Server role permissions on the SQL Server instance selected for site database installation, or the SQL Server instance could not be contacted to verify permissions. Setup
cannot continue.
and
Site System to SQL Server communication WARNING SCCM.Domain_Name
A communication error has been detected between the specified site system and the site database computer. This error can occur when the site database server is offline or if a valid SPN has not been registered in Active Directory Domain Services for the SQL
Server instance hosting the site database. Setup cannot continue.
Why does the install of SCCM 2012 with 32 bit SQL proceed further than the install with 64 bit SQL, with the latter process failing as above error meesages show and yet both servers are set identically (apart from temporary turning off Firewall on the 64
bit server) and during the install the Databse Server specified is accepted ?

Thanks for the reply.
I can connect via ODBC to the the 32 bit SQL Server and the 64 bit SQL Server from the SCCM Server
The SQL Server Unit called SQL3 unit is a 64 bit SQL.
The SQL Server Unit called SQL is only 32 bit, but at least gets past the final checking stage and the error messages about sysadmin rights and Site System to SQL Server communication problem, and then fails with PKI certificate error message.
When trying to install SCCM specifying the 64 bit SQL Server as the Database Server it gives the 2 error messages at the final checking stage of the installation as listed.
So as I said what is confusing is the fact that if the SCCM install uses the remote 32 bit SQL Server it passes the final checking (although fails with PKI certificate message) but the 64 bit SQL Server set up exactly the same apart from the Firewall being
left off for the time being, fails at the final check stage with the 2 listed errors.
If I use a local 64 bit SQL Server the installation is fine.
Still would like to find out what cause the 2 issues for the remote 64 bit SQL Server, when ODBC seems fine, sysadmin rights have been given for the installer account and the SCCM computer account and SPNs have been set for the user account running the SQL
Services.

Not able to access database from a remote machine using SQL Server Management Studio

Hi,
I have a DB_BOX with SQL Server 2008 R2 installed. I can access the databases on the local machine using SQL Server Management Studio but it is not accessible from other machines, though the machines are in same domain.
I have remote enabled on SQL Server box, TCP enabled, firewall off. I checked with IP Address too, all SQL Server services are running.
The SQL Server log shows the message
The requested service has been stopped or disabled and is unavailable at this time. The connection has been closed.
I get the below message in SSMS from remote machine.
Details of error message are
===================================
Cannot connect to DB_BOX.
===================================
A connection was successfully established with the server, but then an error occurred during the login process. (provider: TCP Provider, error: 0 - The specified network name is no longer available.) (.Net SqlClient Data Provider)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=64&LinkId=20476
Server Name: DB_BOX
Error Number: 64
Severity: 20
State: 0
Program Location:
   at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
   at System.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject stateObj, UInt32 error)
   at System.Data.SqlClient.TdsParserStateObject.ReadSni(DbAsyncResult asyncResult, TdsParserStateObject stateObj)
   at System.Data.SqlClient.TdsParserStateObject.ReadNetworkPacket()
   at System.Data.SqlClient.TdsParserStateObject.ReadBuffer()
   at System.Data.SqlClient.TdsParserStateObject.ReadByte()
   at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
   at System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK)
   at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject)
   at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart)
   at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)
   at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
   at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)
   at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup)
   at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
   at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
   at System.Data.SqlClient.SqlConnection.Open()
   at Microsoft.SqlServer.Management.SqlStudio.Explorer.ObjectExplorerService.ValidateConnection(UIConnectionInfo ci, IServerType server)
   at Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()

Sorry, missed the message from the errorlog in the original post. You shouldn't have included that big .Net dump that hid the important facts. :-)
My first Google attempt on that message (which I have never seen before) suggests that the TCP Enpoint is stopped, so try this:
ALTER ENDPOINT [TSQL Default TCP]
STATE=STARTED;
Erland Sommarskog, SQL Server MVP, [email protected]
This solves the problem. Thanks...

DESKI Report using Temp tables in MS- SQL server 2005

Hi,
I am trying to create a Free hand SQL DESKI report using temp tables in MS SQL Server-2005, I am using ODBC connection.
When I run the report, I am getting the error
u201CConnection or SQL sentence error (DA0005) No column or data to fetchu201D
Ex:
Select *
into #t1
from region
select * from #t1
drop table #t1
Please help.
Regards,
Pratik

Pratik, the SQL does not seem right. BTW you can only retreive data via Deski Free hand SQL. Also try to use OLE DB connection.

DI Server - Cannot connect to named instance SQL server database

Hi,
I have developed a small DI server application and want to migrate it to a production server. I keep on getting the Cannot connect to SBOCommon error on login though. I have verified all user names and passwords and the only real difference is that the production environment uses a named instance SQL server eg server\instance setup.
The production DI server will however connect perfectly to the test database (which is NOT a named instance) .
Anyone using DI server against a named instance SQL server or have some other ideas what might cause this?
I use B1WS 1.0 and the version of SBO is 8.00.181..
Jaco

I may have solved the problem, at least partially.
I created a test user with full rights on my test database server and it would also not connect, even though my test database is not a an instance setup.
Then I found this thread [Re: DI Server Always Uses SA to log into MS SQL database even if SOAP packet]
It seems that at my current patch level the user 'sa' is hard coded into the DI server as sql username! I don't have the production server's 'sa' user credentials at present but will test it on Monday. Will also test against 8.8 soon ..

How to enable remote connections in SQL Server 2008

I'm trying to enable remote connections in SQL Server 2008 R2 as described in the following article. I see the error message at the top of the article.
http://blogs.msdn.com/b/walzenbach/archive/2010/04/14/how-to-enable-remote-connections-in-sql-server-2008.aspx
One step in the article describes how to enable TCP/IP in Configuration Manager.  Specifically it says that
'SQL Server NETWORK Configuration' should have TCP/IP enabled.
The issue I've encountered is that my Configuration Manager
is different than what appears in the article. My Configuration Manager shows the following:
SQL Server 2005 Services
SQL Server 2005 Network Configuration (32 bit)
      - Protocols for SQLExpress
SQL Native Client Configuration (32 bit)
       - Client protocols
       - Aliases
Note that I see 'SQL Server 2005 Network Configuration'
rather than that for 2008. When 'Protocols for SQLExpress'
is expanded, there is a TCP/IP setting, but it's disabled and I see an
Access Denied message if I try to enable this.
I also see a TCP/IP setting under Client protocols and successfully enabled this. This uses port 1433 and I configured my firewall to accomodate this port as suggested in the article.
I also followed the other steps in the article, but still don't have remote access to SQL Server 2008 R2. (I can access it from the office.) I'm wondering if this remote access issue is because SQL Server
2008 Network Configuration does not appear in Configuration Manager
and if so, I'm interested in how this might be resolved. (I'm running Windows 7 - 64 bit.)
I'd appreciate any ideas on this. Thanks.

Hello,
Please refer to the following resource.
http://support.microsoft.com/kb/KbView/914277
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com

How to fix a report textbox aggregate expression error in SQL server reporting with multiple datasets?

I have a SQL Server Reporting Services report that has a textbox within a Report with variations of the following expression
=Sum(IiF(Fields!RegisterID.Value = 6000, 1, 0)
and
Iif(Fields!PointID.Value = 500, 1, 0)) / Sum(Iif(Fields!PointID.Value = 500, 1, 0))
I see the following error when I try to preview the report:
The Value expression for the text box ‘Textbox2’ uses an aggregate expression without a scope. A scope is required for all aggregates used outside of a data region unless the report contains exactly one dataset.
What am I missing in this this expression to make it run incorrectly

Can you include dataset name in your sum functions? e.g. Sum(IiF(Fields!RegisterID.Value = 6000, 1, 0)
and
Iif(Fields!PointID.Value = 500, 1, 0)) should include your dataset name as Sum(IiF(Fields!RegisterID.Value = 6000, 1, 0) and Iif(Fields!PointID.Value = 500, 1, 0),"datasetname")Like wise Sum(Iif(Fields!PointID.Value = 500, 1, 0)) should also have dataset name Sum(Iif(Fields!PointID.Value = 500, 1, 0),"datasetname")
Gaur

XL Reporter on SBO2005 SP1 PL10 & MS SQL Server 2005

Hi All,
Has any1 installed XL Reporter on SBO 2005 SP1 that has MS SQL Server 2005???
I keep getting an error....
"Unable to connect to XL Reporter....
User Authentication Failed.
......SQL Server does not exist or access is denied. Cant connect to database provider ........"
Thanks.

Hi Noor
I'm pasting the SAP note for you:
TCP/IP might not be enabled in the SQL Server Configuration Manager
1.Properties for SQL server selected to allow SQL server &
Windows authentication.
- To do this: In SQL server Management studio-Right click on Server -Properties - Security -
choose Allow SQL server & Windows authentication
2. Under Microsoft SQL Server 2005 -> configuration tools ->
Configuration Manager - client protocols - enable the tcp/ip
3.In SQL server configuration manager SQL server 2005 Network configuration - enable the TCP/IP
4. In SQL Server 2005 Surface Area Configuration
- Surface Area Configuration for services and connections
- Expand SQL 2005 - Database Engine - Remote Connections
- Choose Local and remote connections and select using both TCP/IP nad named pipes
5. In SQL Server Management Studio -> Right click on the server instance -> stop the service and start again.
Hope this helps
Daan

Can't remote connect to sql server

I have SQL Sever 2008 R2 on the cluster environment
cluster server name is A
Cluster Node 1 name is A1 (current active one)
Cluster Node2 name is A2
SQL Server name is Ab, default instance, tcp/ip port 1433
I am not able to remote connect to the server. I tried A, A1, Ab and their corresponding IP address, not of them works. Should I change to the SQL Server name to match with the cluster server name? Thanks in advance!

Dont have to change the sql server name.
In a standalone machine when you have a default instance, the sql server name is indeed the server name. But in cluster its the network name that is associated with the virtual ip for SQL.
If you try with either SQL Server Network Name or IP address it should work. If it doesnt work try forcing TCP protocol and the port number in connection and see.
check these blog as well
http://blogs.technet.com/b/mdegre/archive/2011/06/04/resolve-sql-server-connectivity-issues.aspx
http://blogs.msdn.com/b/farukcelik/archive/2007/12/31/basics-first-udl-test.aspx
Regards, Ashwin Menon My Blog - http:\\sqllearnings.com

Virtualised Multi-Instance SQL Server Cluster - Processor Resource Management

Hi - We're in the process of implementing a multi-instance SQL 2014 guest cluster on Windows 2012 R2. To our dismay, it seems that Windows System Resource Manager (WSRM) is deprecated in Windows 2012 R2, so we're now stuck for how best to manage CPU usage
between SQL instances....
As far as I can see, I'm left with two options, but both of these have problems:
1) Use SQL Processor affinity within the guest cluster, with each SQL instance assigned to dedicated v-CPU. However, I'm not certain that setting SQL Processor affinity within a VM will actually have the desired affect!?..
- When there is physical CPU capacity available, I'd hope Hyper-V would provide it to whichever v-CPU is demanding it.
- When VM processor demand exceeds the physical CPU capacity, I'd hope the SQL instances would receive a proportion of the physical CPU time according to the number of v-CPU(s) assigned through the affinity settings.
2) Use a VM (actually 2, because its a 2-node guest cluster) per SQL instance!.. This is not ideal, as we need multiple SQL instances and it would result in have an administrative and performance overhead
Does anyone have any information or thoughts on this? How can we manage a virtualised multi-instance SQL deployment now that WSRM has been deprecated? Help me please!

I'm not sure what are the requirements for each of the 2 VMs in in the SQL guest cluster.
I'm assuming the guest cluster resides on a Hyper-V CSV with at least 2 Hyper-V hosts, and the 2 VMs are configured with Anti-affinity to ensure they never reside on the same Hyper-V host.
I've been able to configure CPU resources to VMs from the standard controls in Hyper-V Manager:
See this blog post
What edition of SQL 2014 you're using?
This matters because of these limitations.
Also consider running SQL Server with Hyper-V Dynamic Memory - see Best Practices
and Considerations
Hyper-V performance tuning - CPU
Hyper-V 2012 Best Practices
Sam Boutros, Senior Consultant, Software Logic, KOP, PA http://superwidgets.wordpress.com (Please take a moment to Vote as Helpful and/or Mark as Answer, where applicable) _________________________________________________________________________________
Powershell: Learn it before it's an emergency http://technet.microsoft.com/en-us/scriptcenter/powershell.aspx http://technet.microsoft.com/en-us/scriptcenter/dd793612.aspx

Reports quit working after upgrade to SQL Server 2008

Folks,
I'm running Visual Studio 2008 (sp1) and recently upgraded to SQL Server 2008. Reports worked fine until after upgrade. Now I get the "Login Failed" error message.
Here is code snippets:
        CrystalDecisions.CrystalReports.Engine.ReportDocument oReport = new   CrystalDecisions.CrystalReports.Engine.ReportDocument();
        TableLogOnInfo LonOnInfo = new TableLogOnInfo();
        TableLogOnInfos crtableLogoninfos = new TableLogOnInfos();
        TableLogOnInfo crtableLogoninfo = new TableLogOnInfo();
        private Tables crTables;
        private Table crTable;
        ConnectionInfo crConnectionInfo = new ConnectionInfo();
            crConnectionInfo.IntegratedSecurity = true;
            crConnectionInfo.ServerName = Properties.Settings.Default.InstanceName + "
Instance";
            crConnectionInfo.DatabaseName = "DATABASE";
            crTables = oReport.Database.Tables;
            for (int i = 0; i < crTables.Count; i++)
                crTable = crTables<i>;
                crtableLogoninfo = crTable.LogOnInfo;
                crtableLogoninfo.ConnectionInfo = crConnectionInfo;
                crTable.ApplyLogOnInfo(crtableLogoninfo);
            oReport.RecordSelectionFormula = xFormula;
            crystalReportViewer1.ReportSource = oReport;
Has anyone had this problem? Any help would be appreciated.
Terry

CR 2008 does not support MS SQL 2008 yet, meaning we have not had time to test it completely and add it to our supported platforms.txt file.
One thing I noticed is you are using trusted authenication:
crConnectionInfo.IntegratedSecurity = true;
Make sure you give access to all users, MS changed the security properties a lot since SQL 2005 and you can't simply log into any database now. If you have a DBA check with that person on how to configure NT Authentication or the Help file. You can also do a quick test and simply use MS SQL Server authentication to confirm if it's a user permission issue.
Try creating a report that doesn't use Integrated Security, check the box off on your data logon prompt in the Designer.

Reporting Services 2012 for SharePoint and SQL Server Agent "Subscriptions and Alerts"

After installing Reporting Services for SharePoint (Denali) in my test farm, I'm trying to configure the "SQL Server Agent" access for Reporting Services. From Central Admin I'm going to the Reporting Service applicaiton configuration screen and selecting
"Provision Subscriptions and Alerts". I've tried both options on this screen. I've manually executed the "download sql script" in SQL Server, as well as entering a user with SQL sys admin rights on the SQL server into the login fields on the screen.
The role and permissions have been created for the application pool service account, but Reporting Services is still trying to connect with the annonymous login because I'm getting the following alert each time I open the "Provision Subscriptions and Alerts"
screen:
Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'
The "status" on the screen still shows "SQL Server Agent State cannot be determined". Has anyone else seen this?
Thanks!!

Thanks for your reply!
1) Looks like the new Reporting Services does not run as a Windows Service so it's not listed in the "Configure Service Accounts" pulldown. As a result, I don't see how to set the service account. It's only assigned to an application pool.
I installed it into an existing application pool and that application pool "is" in the list and has a domain service account already assigned.
2) Which users need to be in here in order to configure the "Provision Subscriptions and Alerts" screen? I already have the farm admin account which is the account I use when running Central Admin.
3) As mentioned in #1, I've installed Reporting Services into an existing application pool with other service apps.
4) This link is for Reporting Services 2008 R2 which is very different install process. But I did follow the SQL Server Reporting Services 2012 RC0 installation instructions and the Reporting Services is functioning correctly with no errors.
I'm just not able to configure the sceduling the alerting with interfaces with the SQL Server Agent.
Thanks!

Reporting Point over remote multiple instance SQL Server

Similar Messages

Maybe you are looking for