Configuration Manager 2007 Client Status Reporting
Dear Members I have installed Client status reporting on my SCCM 2007 R2 Server, Now I have to configure the Site Settings for the Database Settings field.How cold i get the information of ConfigMgr SQL server and instance: and ConfigMgr Site database names: please help me...
May 5th, 2010 12:50pm

Navigate to System Status -> Site status -> Sitecode -> Site System Status in the ConfigMgr admin console. You'll find the name of the SQL server and database there.
Free Windows Admin Tool Kit Click here and download it now
May 5th, 2010 1:16pm

Dear Torsten On the Client Status Reporting Tool , Site Database> Database Settings, two feilds i don't have the knowledge please advise, from where can i get the "ConfigMgr SQL server and instance:" and "ConfigMgr site database" details..please help me... from when i can get the details of above mentioned then only i can configure the client status report. thanks very much..
May 5th, 2010 2:31pm

Have you tried what I described? The SQL server and database names can be obtained from there.
Free Windows Admin Tool Kit Click here and download it now
May 5th, 2010 2:39pm

Dear Torsten please advise me... when i configure the client report tools its not running perfectly please find the error from the client reporting tool log file 5/5/2010 4:14:32 AM> Log Created <5/5/2010 4:14:32 AM> Service Starting <5/5/2010 4:14:32 AM> Load Settings <5/5/2010 4:14:32 AM> Done Loading <5/5/2010 4:19:32 AM> Invalid SQL error - 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: 25 - Connection string is not valid) <5/5/2010 4:19:32 AM> Failed to update settings in database <5/5/2010 4:19:32 AM> Load Settings for Daily Task <5/5/2010 4:19:32 AM> Done Loading Daily Task Settings <5/5/2010 4:19:32 AM> Load Settings for Pulse <5/5/2010 4:19:32 AM> Done Loading Pulse Settings <5/5/2010 4:19:32 AM> Schedule is Active Today <5/5/2010 4:19:32 AM> Pulse is not scheduled to run today. Will check schedule tomorrow. <5/5/2010 4:19:32 AM> Load Settings Ping <5/5/2010 4:19:32 AM> Done Loading Ping Settings <5/5/2010 4:19:32 AM> Schedule is Active Today <5/5/2010 4:19:32 AM> Ping will next run on 5/5/2010 2:00:00 PM <5/5/2010 4:20:32 AM> Start to update Client Status Change in database <5/5/2010 4:24:32 AM> Invalid SQL connection error - 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: 25 - Connection string is not valid) <5/5/2010 4:24:32 AM> Daily Task is finished. <5/5/2010 4:25:32 AM> Invalid SQL error - 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: 25 - Connection string is not valid) <5/5/2010 4:25:32 AM> Failed to update settings in database <5/5/2010 4:25:42 AM> Start to update Client Status Change in database <5/5/2010 4:30:42 AM> Invalid SQL error - 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: 25 - Connection string is not valid) <5/5/2010 4:30:42 AM> Failed to update settings in database <5/5/2010 4:30:52 AM> Start to update Client Status Change in database <5/5/2010 4:35:51 AM> Invalid SQL error - 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: 25 - Connection string is not valid) <5/5/2010 4:35:51 AM> Failed to update settings in database <5/5/2010 4:36:01 AM> Start to update Client Status Change in database <5/5/2010 4:41:01 AM> Invalid SQL error - 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: 25 - Connection string is not valid) <5/5/2010 4:41:01 AM> Failed to update settings in database <5/5/2010 4:41:11 AM> Start to update Client Status Change in database <5/5/2010 4:46:11 AM> Invalid SQL error - 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: 25 - Connection string is not valid) <5/5/2010 4:46:11 AM> Failed to update settings in database <5/5/2010 4:46:21 AM> Start to update Client Status Change in database <5/5/2010 4:51:20 AM> Invalid SQL error - 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: 25 - Connection string is not valid) <5/5/2010 4:51:20 AM> Failed to update settings in database <5/5/2010 4:51:30 AM> Start to update Client Status Change in database <5/5/2010 4:56:30 AM> Invalid SQL error - 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: 25 - Connection string is not valid) <5/5/2010 4:56:30 AM> Failed to update settings in database <5/5/2010 4:56:40 AM> Start to update Client Status Change in database <5/5/2010 5:01:40 AM> Invalid SQL error - 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: 25 - Connection string is not valid) <5/5/2010 5:01:40 AM> Failed to update settings in database <5/5/2010 5:01:50 AM> Start to update Client Status Change in database <5/5/2010 5:06:49 AM> Invalid SQL error - 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: 25 - Connection string is not valid) <5/5/2010 5:06:49 AM> Failed to update settings in database <5/5/2010 5:06:59 AM> Start to update Client Status Change in database <5/5/2010 5:11:59 AM> Invalid SQL error - 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: 25 - Connection string is not valid) <5/5/2010 5:11:59 AM> Failed to update settings in database <5/5/2010 5:12:09 AM> Start to update Client Status Change in database <5/5/2010 5:17:09 AM> Invalid SQL error - 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: 25 - Connection string is not valid) <5/5/2010 5:17:09 AM> Failed to update settings in database <5/5/2010 5:17:19 AM> Start to update Client Status Change in database <5/5/2010 5:22:19 AM> Invalid SQL error - 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: 25 - Connection string is not valid) <5/5/2010 5:22:19 AM> Failed to update settings in database <5/5/2010 5:22:29 AM> Start to update Client Status Change in database <5/5/2010 5:27:28 AM> Invalid SQL error - 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: 25 - Connection string is not valid) <5/5/2010 5:27:28 AM> Failed to update settings in database <5/5/2010 5:27:38 AM> Start to update Client Status Change in database <5/5/2010 5:32:38 AM> Invalid SQL error - 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: 25 - Connection string is not valid) <5/5/2010 5:32:38 AM> Failed to update settings in database <5/5/2010 5:32:48 AM> Start to update Client Status Change in database <5/5/2010 5:37:48 AM> Invalid SQL error - 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: 25 - Connection string is not valid) <5/5/2010 5:37:48 AM> Failed to update settings in database <5/5/2010 5:37:58 AM> Start to update Client Status Change in database <5/5/2010 5:42:57 AM> Invalid SQL error - 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: 25 - Connection string is not valid) <5/5/2010 5:42:57 AM> Failed to update settings in database <5/5/2010 5:43:07 AM> Start to update Client Status Change in database <5/5/2010 5:48:07 AM> Invalid SQL error - 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: 25 - Connection string is not valid) <5/5/2010 5:48:07 AM> Failed to update settings in database <5/5/2010 5:48:17 AM> Start to update Client Status Change in database <5/5/2010 5:53:17 AM> Invalid SQL error - 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: 25 - Connection string is not valid) <5/5/2010 5:53:17 AM> Failed to update settings in database <5/5/2010 5:53:27 AM> Start to update Client Status Change in database <5/5/2010 5:58:26 AM> Invalid SQL error - 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: 25 - Connection string is not valid) <5/5/2010 5:58:26 AM> Failed to update settings in database <5/5/2010 5:58:36 AM> Start to update Client Status Change in database <5/5/2010 6:03:36 AM> Invalid SQL error - 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: 25 - Connection string is not valid) <5/5/2010 6:03:36 AM> Failed to update settings in database <5/5/2010 6:03:46 AM> Start to update Client Status Change in database <5/5/2010 6:08:46 AM> Invalid SQL error - 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: 25 - Connection string is not valid) <5/5/2010 6:08:46 AM> Failed to update settings in database <5/5/2010 6:08:56 AM> Start to update Client Status Change in database ================================================== please advise me...
May 5th, 2010 4:19pm

It seems remote connection issue .Try to verify below mention points 1] Enable remote named pipe or tcp: All programs | Microsoft SQL Server 2005| Configuration Tools | SQL Server Surface Area Configuration | Configuration for Services and Connections | Remote Connections, choose either enable TCP or Named Pipe or both. [2] Sql Instance was restarted successfully, check Server ErrorLog, find which tcp port or pipe name server is listening on. [3] netstat -ano | findstr <portnumber> if server enable TCP, and make sure server is listening on the correct port. [4] go to services.msc, find service "SQL Server Browser", enable it and restarted, also, go to SQL Server Configuration Manager, check properties for SQL Browser service, in Advanced tab, make sure it is active. [5] Enable "Fire and Printer Sharing" in Firewall exception list. [6] Add TCP port or sqlservr.exe to Firewall exception list, either add "..\Binn\sqlsevr.exe" or add port. If your server was not started successfully by any reason, it is very helpful to collect info from server logs; also, you can get clear picture of protocols that server is listening on, for eg, if TCP was enabled, you should be able to see which port server is listening on, and if Np was enabled, you can make connection throgh the pipe name. [7] Add Sql Browser service to Firewall exception list, you can either add program " C:\Program Files\Microsoft SQL Server\90\Shared\sqlbrowser.exe" or add UDP port 1434. [8] Make sure if your remote sql Server Instance is a default instance, it must listen on tcp port 1433 and pipe \\.\pipe\sql\query.
Free Windows Admin Tool Kit Click here and download it now
May 6th, 2010 3:35pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics