Upgrating SQL Server 2008 R2 SP2 to SQL Server 2014 Standard "UpgradeFeatureSpecificRules: KJRTMUpgradeBlockRule"
I've been searching for HOURS how to resolve this issue:
I am trying to upgrade SQL Server 2008 R2 (Express Edition with advanced services) to SQL SERVER 2014 Standard edition, my first issue was to update the 2008 R2 to Service pack 2 on the first FEATURE RULE TEST, at this time on it's keep saying this:
======================================================================================
Rule Check Result
Rule "SQL Server 2008 R2 Service pack 2 or later is requered for upgrade.: failed.
This SQL Server 2008 R2 features that have been selected to be upgraded to SQL Server 2014 are not at the require service pack. To continue with this upgrade, install SQL Server 2008 Service Pack 2 or lager to the selected instance and the shared features.
=====================================================================================
This is the Configuration Report issue:
Microsoft SQL Server 2014 - System Configuration Check Report
UpgradeFeatureSpecificRules: SQL Server 2014 Setup configuration checks for rules group 'UpgradeFeatureSpecificRules'
KJRTMUpgradeBlockRule
Checks if the currently selected SQL Server 2008 R2 features to upgrade are at the supported service pack. Failed The SQL Server 2008 R2 features that have been selected to be upgraded to SQL Server 2014 are not at the
required service pack. To continue with this upgrade, install SQL Server 2008 Service Pack 2 or later to the selected instance and the shared features.
====================================================================================
I try after hours and finally did install the Upgrade Advisor and got not issues, the last choice I was to uninstall the Management Studio because in other upgrade express versions got blocked, but in this new version of SQL Server 2014 I don't see any way
out!!!
Thanks.
Hi again
This is the scenario:
-I have installed the SQL SERVER 2008 R2 With Advanced services (version 10.50.1600.1), and now my guest decide to upgrade to an STARNDARD version which nowadays Microsoft is offering the 2014 version.
-As all IT Support and DBA I try to upgrade to SQL 2014 to check and see with requirements were missing or updates. The first check report only ask to upgrade to SQL SERVER 2008 R2 SP2 (version 10.51.2500.0) which I found in the optional update list and
resolved immediately with the Windows Update service.
-Finally, I realise doing the discovery report (suggested in the last post) is that Windows update only download the service pack 2 for SQL Server 2008 instead of the 2008 R2 (I downloaded manually) then the version was upgrade to 10.52.4000.0
Next time I might download the updates manually and not loosing a lot hours with Windows Update, another point very important is that when SQL Server 2008 R2 is installed, create the Microsoft SQL Server 2008 folder at all programas in the Startup menu:
with the SQL Server Installation Center, but there is not one R2, when you execute this one just show the 2008 installed features.
Now we are on 12.0.2000.8
Thanks anyway and all of you for your interest!!!
Similar Messages
-
Upgrade to SP3 from sql server 2008 R2 SP2 and SharePoint server 2010 known issues
Hi Guys,
We are planning to upgrade SQL server to SP3 from 2008 R2 SP2 and would like to known if there are any known issues with SharePoint 2010 server and office web apps.
Though I was searching blogs and forums and could not find any noteworthy but wanted to look if any noted SharePoint issues after the upgrade.
VMHi Venu,
There should no issue for SharePoint 2010 with install SP3 for SQL2008R2 (also like comments mentioned in article below), I searched from internal and internet, there seems no document/article mentioned the known issue for SharePoint about this, you can
back up your environment and test the SP3 in a test environment before touching the production environment.
https://habaneroconsulting.com/insights/SharePoint-SQL-Server-Support-Matrix#.VSTY-nkfr4Y
http://blogs.msdn.com/b/glsmall/archive/2014/12/03/list-of-fixes-in-sql-server-2008-r2-sp3.aspx
Thanks
Daniel Yang
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected] -
Cannot find service {0}. Parameter name: SQLWriter SQL Express 2008 R2 SP2
Hi, installing SQL Express 2008 R2 SP2 onto Windows Server 2012 R2. I had previously removed SQL Express 2012 due to failed install due to incompatibility with our SAN. (I had uninstalled it via Programs & Features,
and also by following Shanky's tips. http://social.technet.microsoft.com/wiki/contents/articles/24364.sql-server-troubleshooting-could-not-find-database-engine-startup-handle-error-during-installation.aspx).
This is what's in Detail log:
014-10-07 13:12:00 Slp: Parameter 5 : SqlEngineConfigAction_install_confignonrc
2014-10-07 13:12:00 Slp: Parameter 6 : 0x50806C41
014-10-07 13:12:01 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141007_122920\Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_
2014-10-07 13:12:01 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141007_122920\Registry_SOFTWARE_Microsoft_Windows_CurrentVersion_Uninstall.reg_
2014-10-07 13:12:01 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\MSSQLServer to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141007_122920\Registry_SOFTWARE_Microsoft_MSSQLServer.reg_
2014-10-07 13:12:01 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Wow6432Node\Microsoft\Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141007_122920\Registry_SOFTWARE_Wow6432Node_Microsoft_Microsoft SQL
Server.reg_
2014-10-07 13:12:01 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141007_122920\Registry_SOFTWARE_Wow6432Node_Microsoft_Windows_CurrentVersion_Uninstall.reg_
2014-10-07 13:12:01 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Wow6432Node\Microsoft\MSSQLServer to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20141007_122920\Registry_SOFTWARE_Wow6432Node_Microsoft_MSSQLServer.reg_
2014-10-07 13:12:02 Slp: Cannot find service {0}.
The SqlEngineConfigAction_install_confignonrc part is what is in the background before the
Cannot find service {0}. Parameter name: SQLWriter pops up.
And in Event Viewer:
Log Name: Application
Source: Microsoft-Windows-RestartManager
Date: 10/7/2014 1:11:48 PM
Event ID: 10010
Task Category: None
Level: Warning
Keywords:
User: SYSTEM
Computer:
Description:
Application 'C:\31f53f2e988a36f2c31e\x64\setup100.exe' (pid 688) cannot be restarted - Application SID does not match Conductor SID..
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-RestartManager" Guid="{0888E5EF-9B98-4695-979D-E92CE4247224}" />
<EventID>10010</EventID>
<Version>0</Version>
<Level>3</Level>
<Task>0</Task>
<Opcode>0</Opcode>
<Keywords>0x8000000000000000</Keywords>
<TimeCreated SystemTime="2014-10-07T20:11:48.532980400Z" />
<EventRecordID>4538</EventRecordID>
<Correlation />
<Execution ProcessID="732" ThreadID="2548" />
<Channel>Application</Channel>
<Computer></Computer>
<Security UserID="S-1-5-18" />
</System>
<UserData>
<RmUnsupportedRestartEvent xmlns="http://www.microsoft.com/2005/08/Windows/Reliability/RestartManager/">
<RmSessionId>0</RmSessionId>
<Pid>688</Pid>
<FullPath>C:\31f53f2e988a36f2c31e\x64\setup100.exe</FullPath>
<DisplayName>Managed SQL Server Installer</DisplayName>
<AppVersion>0</AppVersion>
<AppType>5</AppType>
<TSSessionId>2</TSSessionId>
<Status>67108865</Status>
<Reason>1</Reason>
</RmUnsupportedRestartEvent>
</UserData>
</Event>
Found one article saying you can get this if previous version not fully removed, and to do a repair of the previous version, but as I said I uninstalled it and followed all steps for cleanup, so nothing to repair.Here is the ERRORLOG file from C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log. At the bottom I am seeing the error you said before was a SAN issue. I had hoped that issue was only with
SQL 2012, but it appears it is even with 2008?
If that is still the issue, I'm trying to understand if by the articles, if the SAN conflict is an OS issue or an SQL issue? In other words, is it because the OS is Server 2012? Or would this still occur if I install SQL
2008 on Server 2008 R2? I don't know that they will be willing to upgrade the SAN, and I don't really want to fool with a .VHD (virtual disk) as a workaround speaks of.
If you're asking if I did this from your article: select startup account for Database Engine services as NT Authority\SYSTEM
, I don't recall what I did this last time. I was doing that the last few days, but I think I didn't switch it to that once, just to see if I would have success. I don't know if that was this last time or not when I switched it.
Is there anywhere I can check that after the fact?
014-10-08 12:53:09.84 Server Microsoft SQL Server 2008 R2 (SP2) - 10.50.4000.0 (X64)
Jun 28 2012 08:36:30
Copyright (c) Microsoft Corporation
Express Edition (64-bit) on Windows NT 6.2 <X64> (Build 9200: )
2014-10-08 12:53:09.84 Server (c) Microsoft Corporation.
2014-10-08 12:53:09.84 Server All rights reserved.
2014-10-08 12:53:09.84 Server Server process ID is 2640.
2014-10-08 12:53:09.84 Server System Manufacturer: 'IBM', System Model: 'IBM System x -[7870AC1]-'.
2014-10-08 12:53:09.84 Server Authentication mode is WINDOWS-ONLY.
2014-10-08 12:53:09.84 Server Logging SQL Server messages in file 'c:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG'.
2014-10-08 12:53:09.84 Server This instance of SQL Server last reported using a process ID of 2848 at 10/8/2014 10:56:44 AM (local) 10/8/2014 5:56:44 PM (UTC). This is an informational message only; no user action is required.
2014-10-08 12:53:09.84 Server Registry startup parameters:
-d c:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\master.mdf
-e c:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Log\ERRORLOG
-l c:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA\mastlog.ldf
2014-10-08 12:53:09.84 Server Command Line Startup Parameters:
-m SqlSetup
-f
-Q
-q SQL_Latin1_General_CP1_CI_AS
-T 4022
-T 4010
-T 3659
-T 3610
-T 902
-d c:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Template Data\master.mdf
-l c:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Template Data\mastlog.ldf
2014-10-08 12:53:09.86 Server Warning: The server instance was started using minimal configuration startup option (-f). Starting an instance of SQL Server with minimal configuration places the server in single-user mode automatically.
After the server has been started with minimal configuration, you should change the appropriate server option value or values, stop, and then restart the server.
2014-10-08 12:53:09.86 Server SQL Server is starting at normal priority base (=7). This is an informational message only. No user action is required.
2014-10-08 12:53:09.86 Server Detected 16 CPUs. This is an informational message; no user action is required.
2014-10-08 12:53:10.00 Server Perfmon counters for resource governor pools and groups failed to initialize and are disabled.
2014-10-08 12:53:10.01 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.
2014-10-08 12:53:10.01 Server Lock partitioning is enabled. This is an informational message only. No user action is required.
2014-10-08 12:53:10.03 Server Node configuration: node 0: CPU mask: 0x00000000000000ff:0 Active CPU mask: 0x00000000000000ff:0. This message provides a description of the NUMA configuration for this computer. This is an informational
message only. No user action is required.
2014-10-08 12:53:10.05 Server Support for distributed transactions was not enabled for this instance of the Database Engine because it was started using the minimal configuration option. This is an informational message only. No
user action is required.
2014-10-08 12:53:10.06 spid7s Warning ******************
2014-10-08 12:53:10.06 spid7s SQL Server started in single-user mode. This an informational message only. No user action is required.
2014-10-08 12:53:10.06 spid7s Starting up database 'master'.
2014-10-08 12:53:10.08 spid7s Error: 5178, Severity: 16, State: 1.
2014-10-08 12:53:10.08 spid7s Cannot use file 'c:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Template Data\master.mdf' because it was originally formatted with sector size 4096 and is now on a volume with sector
size 2097152. Move the file to a volume with a sector size that is the same as or smaller than the original sector size.
2014-10-08 12:53:10.09 spid7s Error: 5178, Severity: 16, State: 1.
2014-10-08 12:53:10.09 spid7s Cannot use file 'c:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Template Data\master.mdf' because it was originally formatted with sector size 4096 and is now on a volume with sector
size 2097152. Move the file to a volume with a sector size that is the same as or smaller than the original sector size.
2014-10-08 12:53:10.09 spid7s Error: 5178, Severity: 16, State: 1.
2014-10-08 12:53:10.09 spid7s Cannot use file 'c:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Template Data\mastlog.ldf' because it was originally formatted with sector size 4096 and is now on a volume with
sector size 2097152. Move the file to a volume with a sector size that is the same as or smaller than the original sector size.
2014-10-08 12:53:10.09 spid7s Error: 5178, Severity: 16, State: 1.
2014-10-08 12:53:10.09 spid7s Cannot use file 'c:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\Template Data\mastlog.ldf' because it was originally formatted with sector size 4096 and is now on a volume with
sector size 2097152. Move the file to a volume with a sector size that is the same as or smaller than the original sector size. -
Frequenet dead locks in SQL Server 2008 R2 SP2
Hi,
We are experiencing frequent dead locks in our application. We are using MSSQL Server 2008 R2 SP2 version. When our application is configured for 5-6 app servers, this issue is occurring frequently.
But, when the same application is used with the MSSQL Server 2008 R2 or SQL Server 2012, we don't see the dead lock issue. From the error lock and sql trace, the error message is thrown for the database table JobLock. We have a stored procedure to insert/update
for the above table when the job moves from one service to other. The same procedure works fine when used with the 2008 R2 and SQL Server 2012 Version.
Is the above issue related to the hotfix from the below url?
http://support.microsoft.com/kb/2703275
Following error message is seen frequently in the log file.
INFO : 03/24/2014 10:26:30:290 PM: [00007900:00005932] [Xerox.ISP.Workflow.ManagedActivity.PersistInTransaction] System.Data.SqlClient.SqlException (0x80131904): Transaction (Process ID 62) was deadlocked on lock resources with another process and has been
chosen as the deadlock victim. Rerun the transaction.
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
at System.Data.SqlClient.TdsParser.TryRun(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj, Boolean& dataReady)
at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString)
at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async, Int32 timeout, Task& task, Boolean asyncWrite, SqlDataReader ds)
at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, TaskCompletionSource`1 completion, Int32 timeout, Task& task, Boolean asyncWrite)
at System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(TaskCompletionSource`1 completion, String methodName, Boolean sendToPipe, Int32 timeout, Boolean asyncWrite)
at System.Data.SqlClient.SqlCommand.ExecuteNonQuery()
at Microsoft.Practices.EnterpriseLibrary.Data.Database.DoExecuteNonQuery(DbCommand command)
at Microsoft.Practices.EnterpriseLibrary.Data.Database.ExecuteNonQuery(DbCommand command, DbTransaction transaction)
at Xerox.ISP.DataAccess.Data.Utility.ExecuteNonQuery(TransactionManager transactionManager, DbCommand dbCommand)
at Xerox.ISP.DataAccess.Data.SqlClient.SqlActivityProviderBase.ActivityReady(TransactionManager transactionManager, Int32 start, Int32 pageLength, Nullable`1 ActivityID, Nullable`1 JobId, String ContentUrl, Nullable`1 PrevWorkStep, Nullable`1
CurrentWorkStep, String Principal, Nullable`1 Status, Nullable`1 ServerID, String HostName, Nullable`1 LockUserID, Nullable`1& ErrorCode, Byte[]& Activity_TS)
at Xerox.ISP.DataAccess.Domain.ActivityBase.ActivityReady(Nullable`1 ActivityID, Nullable`1 JobId, String ContentUrl, Nullable`1 PrevWorkStep, Nullable`1 CurrentWorkStep, String Principal, Nullable`1 Status, Nullable`1 ServerID, String HostName,
Nullable`1 LockUserID, Nullable`1& ErrorCode, Byte[]& Activity_TS, Int32 start, Int32 pageLength)
at Xerox.ISP.DataAccess.Domain.ActivityBase.ActivityReady(Nullable`1 ActivityID, Nullable`1 JobId, String ContentUrl, Nullable`1 PrevWorkStep, Nullable`1 CurrentWorkStep, String Principal, Nullable`1 Status, Nullable`1 ServerID, String HostName,
Nullable`1 LockUserID, Nullable`1& ErrorCode, Byte[]& Activity_TS)
at Xerox.ISP.Workflow.ManagedActivity.<>c__DisplayClass2f.<ActivityReady>b__2d()
at Xerox.ISP.Workflow.ManagedActivity.PersistInTransaction(Boolean createNew, PersistMethod persist)
ClientConnectionId:9e44a64f-5014-4634-9cee-4581e1b9c299
I look forward to the suggestions to get the issue resolved. Your input is much appreciated.
Thanks,
Keshava.If you are having deadlock trouble in your SQL Server instance, this recipe demonstrates how to make sure deadlocks are logged to the SQL ServerManagement Studio SQL log appropriately using
the DBCC TRACEON, DBCC TRACEOFF, and DBCC TRACESTATUS commands. These functions enable, disable, and check the status of trace flags.
To determine the cause of a deadlock, we need to know
the resources involved and the types of locks acquired and requested. For this kind of information, SQL Server provides
Trace Flag 1222 (this flag supersedes 1204, which was frequently used in earlier versions of SQL Server.)
DBCCTRACEON(1222,
-1);
GO
With this flag enabled, SQL Server will provide output in the form of a deadlock graph, showing the executing statements
for each session, at the time of the deadlock; these are the statements that were blocked and so formed the conflict or cycle that led to the deadlock.
Be aware that it is rarely possible to guarantee that deadlocks will never occur. Tuning for deadlocks
primarily involves minimizing the likelihood of their occurrence. Most of the techniques for minimizing the occurrence of deadlocks are similar to the general techniques for minimizing blocking problems. -
Data Committed instead of Rollback after Deadlock Error in SQL Server 2008 R2 (SP2)
We're having a strange issue which is occurring only with one Customer having SQL Server 2008 R2 (SP2).
Basically we have multiple threads uploading data and when an error occurs (like deadlock or any other error). The deadlock victim (process/transaction) is rolledback (from .NET). However the rollback command is not reaching SQL Server as it doesn't show
in the trace (through SQL Profiler).
To make things worse, not only the transaction is not being rolled back but the INSERTs executed before the error are being somehow committed, leaving the database in an inconsistent state.
This is only produced in one environment.
Any idea what the issue could be?All statements are executed with in a Transaction. Under the same scenario this code works perfectly fine for 1000s of customers. Only one customer has this issue.
You need to capture profiler to check transaction scope.
Balmukund Lakhani
Please mark solved if I've answered your question, vote for it as helpful to help other users find a solution quicker
This posting is provided "AS IS" with no warranties, and confers no rights.
My Blog |
Team Blog | @Twitter
| Facebook
Author: SQL Server 2012 AlwaysOn -
Paperback, Kindle -
SMS_SRS_REPORTING_POINT - Error retrieving folders with SCCM 2012 and SQL Server 2008 R2 SP2
Hi:
According to all the Reporting Services logs my Reporting Point was setup correctly. When I try and run any report I see the entries below in the srsrp.log on the SQL Server. The report names show up in the Console but when I right any of the
listed reports I get errors and no report runs.
I am running SQL Server 2008 R2 SP2 on a remote server. SQL is installed on its own server. There is no firewall between the Configuration Manager server and SQL Server.
Thanks.
Mark
(!) Error retrieving folders - [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.)]. SMS_SRS_REPORTING_POINT
1/25/2013 9:15:07 AM 4532 (0x11B4)
No folder configuration information found.
SMS_SRS_REPORTING_POINT 1/25/2013 9:15:07 AM
4532 (0x11B4)
Next security configuration at [1/25/2013 9:22:42 AM]
SMS_SRS_REPORTING_POINT 1/25/2013 9:15:07 AM
4532 (0x11B4)
Root Folder exists
SMS_SRS_REPORTING_POINT 1/25/2013 9:15:07 AM
4532 (0x11B4)
Successfully checked that the SRS web service is healthy on server DBSCCM.LOCAL
SMS_SRS_REPORTING_POINT 1/25/2013 9:15:07 AM
4532 (0x11B4)
Waiting for changes for 1 minutes
SMS_SRS_REPORTING_POINT 1/25/2013 9:15:07 AM
4532 (0x11B4)
SRSRP registry key change notification triggered.
SMS_SRS_REPORTING_POINT 1/25/2013 9:15:16 AM
4532 (0x11B4)
Waiting for changes for 1 minutes
SMS_SRS_REPORTING_POINT 1/25/2013 9:15:16 AM
4532 (0x11B4)
Timed Out...
SMS_SRS_REPORTING_POINT 1/25/2013 9:16:16 AM
4532 (0x11B4)
Reporting Services URL from Registry [http://dbsccm/ReportServer/ReportService2005.asmx]
SMS_SRS_REPORTING_POINT 1/25/2013 9:16:16 AM
4532 (0x11B4)
Reporting Services is running
SMS_SRS_REPORTING_POINT 1/25/2013 9:16:16 AM
4532 (0x11B4)
Retrieved datasource definition from the server.
SMS_SRS_REPORTING_POINT 1/25/2013 9:16:16 AM
4532 (0x11B4)
Retrieved datasource definition from the server.
SMS_SRS_REPORTING_POINT 1/25/2013 9:16:16 AM
4532 (0x11B4)
Updating data source {5C6358F2-4BB6-4a1b-A16E-8D96795D8602} at ManagedDesktops_MD1
SMS_SRS_REPORTING_POINT 1/25/2013 9:16:16 AM
4532 (0x11B4)
(!) Error retrieving folders - [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.)]. SMS_SRS_REPORTING_POINT
1/25/2013 9:17:40 AM 4532 (0x11B4)
No folder configuration information found.
SMS_SRS_REPORTING_POINT 1/25/2013 9:17:40 AM
4532 (0x11B4)
Next security configuration at [1/25/2013 9:22:42 AM]
SMS_SRS_REPORTING_POINT 1/25/2013 9:17:40 AM
4532 (0x11B4)
Root Folder exists
SMS_SRS_REPORTING_POINT 1/25/2013 9:17:40 AM
4532 (0x11B4)
Successfully checked that the SRS web service is healthy on server DBSCCM.LOCAL
SMS_SRS_REPORTING_POINT 1/25/2013 9:17:40 AM
4532 (0x11B4)
Waiting for changes for 1 minutes
SMS_SRS_REPORTING_POINT 1/25/2013 9:17:40 AM
4532 (0x11B4)
Timed Out...
SMS_SRS_REPORTING_POINT 1/25/2013 9:18:40 AM
4532 (0x11B4)
Reporting Services URL from Registry [http://dbsccm/ReportServer/ReportService2005.asmx]
SMS_SRS_REPORTING_POINT 1/25/2013 9:18:40 AM
4532 (0x11B4)
Reporting Services is running
SMS_SRS_REPORTING_POINT 1/25/2013 9:18:40 AM
4532 (0x11B4)
Retrieved datasource definition from the server.
SMS_SRS_REPORTING_POINT 1/25/2013 9:18:40 AM
4532 (0x11B4)
Retrieved datasource definition from the server.
SMS_SRS_REPORTING_POINT 1/25/2013 9:18:40 AM
4532 (0x11B4)
Updating data source {5C6358F2-4BB6-4a1b-A16E-8D96795D8602} at ManagedDesktops_MD1
SMS_SRS_REPORTING_POINT 1/25/2013 9:18:40 AM
4532 (0x11B4)Hi:
Windows Firewall is off on both systems.
I can ping the Configuration Manager server from the SQL Server by netbios name, ip address and fully qualified domain name. I can ping the SQL Server from the Configuration Manager server by netbios name, ip address and fully qualified domain
name.
I have uninstalled and installed the Reporting Point Service a couple of times and everything looks fine according to the logs after the install finishes but these errors only appear each time I try and Run a report.
Mark -
I am getting below exception while clicking on new query button in SSMS of SQL server 2008 R2 SP2.
I am thinking to reinstall Complete Management Tools. is it worth to give a try on production server? What can be the fix?
Exception Details-
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.SqlServer.Management.UI.VSIntegration.ShellCodeWindowControl.CreateCWWindow()
at Microsoft.SqlServer.Management.UI.VSIntegration.ShellCodeWindowControl.OnHandleCreated(EventArgs a)
at System.Windows.Forms.Control.WmCreate(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at Microsoft.SqlServer.Management.UI.VSIntegration.ShellTextEditorControl.WndProc(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
************** Loaded Assemblies **************
mscorlib
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v2.0.50727/mscorlib.dll
AppIDPackage
Assembly Version: 10.0.0.0
Win32 Version: 10.50.4000.0 ((KJ_PCU_Main).120628-0827 )
CodeBase: file:///E:/Program%20Files%20(x86)/Microsoft%20SQL%20Server/100/Tools/Binn/VSShell/Common7/IDE/AppIDPackage.DLL
System
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
Microsoft.SqlServer.SqlTools.VSIntegration
Assembly Version: 10.0.0.0
Win32 Version: 10.50.4000.0 ((KJ_PCU_Main).120628-0827 )
CodeBase: file:///E:/Program%20Files%20(x86)/Microsoft%20SQL%20Server/100/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.SqlTools.VSIntegration.DLL
Microsoft.VisualStudio.Shell.Interop
Assembly Version: 7.1.40304.0
Win32 Version: 7.10.6071
CodeBase: file:///C:/Windows/assembly/GAC/Microsoft.VisualStudio.Shell.Interop/7.1.40304.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.Shell.Interop.dll
Microsoft.VisualStudio.OLE.Interop
Assembly Version: 7.1.40304.0
Win32 Version: 7.10.6070
CodeBase: file:///C:/Windows/assembly/GAC/Microsoft.VisualStudio.OLE.Interop/7.1.40304.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.OLE.Interop.dll
System.Windows.Forms
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Windows.Forms/2.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
System.Drawing
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
SqlWorkbench.Interfaces
Assembly Version: 10.0.0.0
Win32 Version: 10.50.1600.1 ((KJ_RTM).100402-1540 )
CodeBase: file:///E:/Program%20Files%20(x86)/Microsoft%20SQL%20Server/100/Tools/Binn/VSShell/Common7/IDE/SqlWorkbench.Interfaces.DLL
Microsoft.SqlServer.SqlTDiagM
Assembly Version: 10.0.0.0
Win32 Version: 10.50.1600.1 ((KJ_RTM).100402-1539 )
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.SqlServer.SqlTDiagM/10.0.0.0__89845dcd8080cc91/Microsoft.SqlServer.SqlTDiagM.dll
Microsoft.SqlServer.Instapi
Assembly Version: 10.0.0.0
Win32 Version: 10.50.1600.1 ((KJ_RTM).100402-1540 )
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.SqlServer.Instapi/10.0.0.0__89845dcd8080cc91/Microsoft.SqlServer.Instapi.dll
EnvDTE
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.1826 (QFE.050727-1800)
CodeBase: file:///C:/Windows/assembly/GAC/EnvDTE/8.0.0.0__b03f5f7f11d50a3a/EnvDTE.dll
Microsoft.VisualStudio.Shell
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1826 (QFE.050727-1800)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualStudio.Shell/2.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.Shell.dll
Microsoft.VisualStudio.Shell.Interop.8.0
Assembly Version: 8.0.0.0
Win32 Version: 8.0.50727.1826 (QFE.050727-1800)
CodeBase: file:///C:/Windows/assembly/GAC/Microsoft.VisualStudio.Shell.Interop.8.0/8.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.Shell.Interop.8.0.dll
Microsoft.SqlServer.Management.SDK.SqlStudio
Assembly Version: 10.0.0.0
Win32 Version: 10.50.1600.1 ((KJ_RTM).100402-1540 )
CodeBase: file:///E:/Program%20Files%20(x86)/Microsoft%20SQL%20Server/100/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.Management.SDK.SqlStudio.DLL
Microsoft.DataWarehouse.SQM
Assembly Version: 10.0.0.0
Win32 Version: 10.50.4000.0 ((KJ_PCU_Main).120628-0827 )
CodeBase: file:///E:/Program%20Files%20(x86)/Microsoft%20SQL%20Server/100/Tools/Binn/VSShell/Common7/IDE/Microsoft.DataWarehouse.SQM.DLL
Microsoft.SqlServer.Management.SqlStudio.Explorer
Assembly Version: 10.0.0.0
Win32 Version: 10.50.4000.0 ((KJ_PCU_Main).120628-0827 )
CodeBase: file:///E:/Program%20Files%20(x86)/Microsoft%20SQL%20Server/100/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.Management.SqlStudio.Explorer.DLL
Microsoft.SqlServer.Management.Controls
Assembly Version: 10.0.0.0
Win32 Version: 10.50.1600.1 ((KJ_RTM).100402-1540 )
CodeBase: file:///E:/Program%20Files%20(x86)/Microsoft%20SQL%20Server/100/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.Management.Controls.DLL
System.Configuration
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Configuration/2.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
System.Xml
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Xml/2.0.0.0__b77a5c561934e089/System.Xml.dll
ObjectExplorer
Assembly Version: 10.0.0.0
Win32 Version: 10.50.4000.0 ((KJ_PCU_Main).120628-0827 )
CodeBase: file:///E:/Program%20Files%20(x86)/Microsoft%20SQL%20Server/100/Tools/Binn/VSShell/Common7/IDE/ObjectExplorer.DLL
System.Design
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Design/2.0.0.0__b03f5f7f11d50a3a/System.Design.dll
Microsoft.SqlServer.Management.UserSettings
Assembly Version: 10.0.0.0
Win32 Version: 10.50.4000.0 ((KJ_PCU_Main).120628-0827 )
CodeBase: file:///E:/Program%20Files%20(x86)/Microsoft%20SQL%20Server/100/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.Management.UserSettings.DLL
SqlMgmt
Assembly Version: 10.0.0.0
Win32 Version: 10.50.4000.0 ((KJ_PCU_Main).120628-0827 )
CodeBase: file:///E:/Program%20Files%20(x86)/Microsoft%20SQL%20Server/100/Tools/Binn/VSShell/Common7/IDE/SqlMgmt.DLL
Microsoft.SqlServer.Management.Sdk.Sfc
Assembly Version: 10.0.0.0
Win32 Version: 10.50.4000.0 ((KJ_PCU_Main).120628-0827 )
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.SqlServer.Management.Sdk.Sfc/10.0.0.0__89845dcd8080cc91/Microsoft.SqlServer.Management.Sdk.Sfc.dll
ConnectionDlg
Assembly Version: 10.0.0.0
Win32 Version: 10.50.4000.0 ((KJ_PCU_Main).120628-0827 )
CodeBase: file:///E:/Program%20Files%20(x86)/Microsoft%20SQL%20Server/100/Tools/Binn/VSShell/Common7/IDE/ConnectionDlg.DLL
Microsoft.VisualStudio
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1826 built by: QFE
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualStudio/2.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.dll
System.Drawing.Design
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Drawing.Design/2.0.0.0__b03f5f7f11d50a3a/System.Drawing.Design.dll
Microsoft.VisualStudio.Designer.Interfaces
Assembly Version: 1.0.5000.0
Win32 Version: 1.1.4322.573
CodeBase: file:///C:/Windows/assembly/GAC/Microsoft.VisualStudio.Designer.Interfaces/1.0.5000.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.Designer.Interfaces.dll
Microsoft.SqlServer.RegSvrEnum
Assembly Version: 10.0.0.0
Win32 Version: 10.50.1600.1 ((KJ_RTM).100402-1539 )
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.SqlServer.RegSvrEnum/10.0.0.0__89845dcd8080cc91/Microsoft.SqlServer.RegSvrEnum.dll
Microsoft.SqlServer.Management.Reports
Assembly Version: 10.0.0.0
Win32 Version: 10.50.4000.0 ((KJ_PCU_Main).120628-0827 )
CodeBase: file:///E:/Program%20Files%20(x86)/Microsoft%20SQL%20Server/100/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.Management.Reports.DLL
Microsoft.SqlServer.Management.SqlStudio.Migration
Assembly Version: 10.0.0.0
Win32 Version: 10.50.1600.1 ((KJ_RTM).100402-1540 )
CodeBase: file:///E:/Program%20Files%20(x86)/Microsoft%20SQL%20Server/100/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.Management.SqlStudio.Migration.DLL
Microsoft.SqlServer.Smo
Assembly Version: 10.0.0.0
Win32 Version: 10.50.4000.0 ((KJ_PCU_Main).120628-0827 )
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.SqlServer.Smo/10.0.0.0__89845dcd8080cc91/Microsoft.SqlServer.Smo.dll
Microsoft.NetEnterpriseServers.ExceptionMessageBox
Assembly Version: 10.0.0.0
Win32 Version: 10.50.1600.1 ((KJ_RTM).100402-1539 )
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.NetEnterpriseServers.ExceptionMessageBox/10.0.0.0__89845dcd8080cc91/Microsoft.NetEnterpriseServers.ExceptionMessageBox.dll
System.Data
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_32/System.Data/2.0.0.0__b77a5c561934e089/System.Data.dll
Microsoft.SqlServer.Management.SqlStudio
Assembly Version: 10.0.0.0
Win32 Version: 10.50.1600.1 ((KJ_RTM).100402-1540 )
CodeBase: file:///E:/Program%20Files%20(x86)/Microsoft%20SQL%20Server/100/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.Management.SqlStudio.DLL
Accessibility
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Accessibility/2.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
Microsoft.SqlServer.ConnectionInfo
Assembly Version: 10.0.0.0
Win32 Version: 10.50.4000.0 ((KJ_PCU_Main).120628-0827 )
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.SqlServer.ConnectionInfo/10.0.0.0__89845dcd8080cc91/Microsoft.SqlServer.ConnectionInfo.dll
Microsoft.SqlServer.Management.RegisteredServers
Assembly Version: 10.0.0.0
Win32 Version: 10.50.1600.1 ((KJ_RTM).100402-1539 )
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.SqlServer.Management.RegisteredServers/10.0.0.0__89845dcd8080cc91/Microsoft.SqlServer.Management.RegisteredServers.dll
Microsoft.SqlServer.SqlClrProvider
Assembly Version: 10.0.0.0
Win32 Version: 10.50.1600.1 ((KJ_RTM).100402-1539 )
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.SqlServer.SqlClrProvider/10.0.0.0__89845dcd8080cc91/Microsoft.SqlServer.SqlClrProvider.dll
8h2zzgtz
Assembly Version: 10.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
Microsoft.SqlServer.SString
Assembly Version: 10.0.0.0
Win32 Version: 10.50.1600.1 ((KJ_RTM).100402-1539 )
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.SqlServer.SString/10.0.0.0__89845dcd8080cc91/Microsoft.SqlServer.SString.dll
0seaoek4
Assembly Version: 10.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
Microsoft.SqlServer.Diagnostics.STrace
Assembly Version: 10.0.0.0
Win32 Version: 10.50.1600.1 ((KJ_RTM).100402-1539 )
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.SqlServer.Diagnostics.STrace/10.0.0.0__89845dcd8080cc91/Microsoft.SqlServer.Diagnostics.STrace.dll
System.Transactions
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.4927 (NetFXspW7.050727-4900)
CodeBase: file:///C:/Windows/assembly/GAC_32/System.Transactions/2.0.0.0__b77a5c561934e089/System.Transactions.dll
System.EnterpriseServices
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_32/System.EnterpriseServices/2.0.0.0__b03f5f7f11d50a3a/System.EnterpriseServices.dll
Microsoft.SqlServer.SqlEnum
Assembly Version: 10.0.0.0
Win32 Version: 10.50.4000.0 ((KJ_PCU_Main).120628-0827 )
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.SqlServer.SqlEnum/10.0.0.0__89845dcd8080cc91/Microsoft.SqlServer.SqlEnum.dll
Microsoft.SqlServer.BatchParserClient
Assembly Version: 10.0.0.0
Win32 Version: 10.50.1600.1 ((KJ_RTM).100402-1539 )
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.SqlServer.BatchParserClient/10.0.0.0__89845dcd8080cc91/Microsoft.SqlServer.BatchParserClient.dll
Microsoft.SqlServer.BatchParser
Assembly Version: 10.0.0.0
Win32 Version: 2009.0100.1600.01 ((KJ_RTM).100402-1540 )
CodeBase: file:///C:/Windows/assembly/GAC_32/Microsoft.SqlServer.BatchParser/10.0.0.0__89845dcd8080cc91/Microsoft.SqlServer.BatchParser.dll
msvcm80
Assembly Version: 8.0.50727.4940
Win32 Version: 8.00.50727.4940
CodeBase: file:///C:/Windows/WinSxS/x86_microsoft.vc80.crt_1fc8b3b9a1e18e3b_8.0.50727.4940_none_d08cc06a442b34fc/msvcm80.dll
Microsoft.SqlServer.Dmf
Assembly Version: 10.0.0.0
Win32 Version: 10.50.4000.0 ((KJ_PCU_Main).120628-0827 )
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.SqlServer.Dmf/10.0.0.0__89845dcd8080cc91/Microsoft.SqlServer.Dmf.dll
Microsoft.SqlServer.PolicyEnum
Assembly Version: 10.0.0.0
Win32 Version: 10.50.1600.1 ((KJ_RTM).100402-1539 )
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.SqlServer.PolicyEnum/10.0.0.0__89845dcd8080cc91/Microsoft.SqlServer.PolicyEnum.dll
ObjectExplorerReplication
Assembly Version: 10.0.0.0
Win32 Version: 10.50.1600.1 ((KJ_RTM).100402-1540 )
CodeBase: file:///E:/Program%20Files%20(x86)/Microsoft%20SQL%20Server/100/Tools/Binn/VSShell/Common7/IDE/ObjectExplorerReplication.DLL
Microsoft.SqlServer.Sqm
Assembly Version: 10.0.0.0
Win32 Version: 10.50.1600.1 ((KJ_RTM).100402-1540 )
CodeBase: file:///E:/Program%20Files%20(x86)/Microsoft%20SQL%20Server/100/Tools/Binn/VSShell/Common7/IDE/Microsoft.SqlServer.Sqm.DLL
ihzu3zbs
Assembly Version: 10.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System/2.0.0.0__b77a5c561934e089/System.dll
System.Management
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.5420 (Win7SP1.050727-5400)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/System.Management/2.0.0.0__b03f5f7f11d50a3a/System.Management.dll
SQLEditors
Assembly Version: 10.0.0.0
Win32 Version: 10.50.4000.0 ((KJ_PCU_Main).120628-0827 )
CodeBase: file:///E:/Program%20Files%20(x86)/Microsoft%20SQL%20Server/100/Tools/Binn/VSShell/Common7/IDE/SQLEditors.DLL
Microsoft.VisualStudio.TextManager.Interop
Assembly Version: 7.1.40304.0
Win32 Version: 7.10.6070
CodeBase: file:///C:/Windows/assembly/GAC/Microsoft.VisualStudio.TextManager.Interop/7.1.40304.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.TextManager.Interop.dll
Microsoft.SqlServer.Management.MultiServerConnection
Assembly Version: 10.0.0.0
Win32 Version: 10.50.1600.1 ((KJ_RTM).100402-1539 )
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.SqlServer.Management.MultiServerConnection/10.0.0.0__89845dcd8080cc91/Microsoft.SqlServer.Management.MultiServerConnection.dll
RadLangSvc
Assembly Version: 10.0.0.0
Win32 Version: 10.50.4000.0 ((KJ_PCU_Main).120628-0827 )
CodeBase: file:///E:/Program%20Files%20(x86)/Microsoft%20SQL%20Server/100/Tools/Binn/VSShell/Common7/IDE/RadLangSvc.DLL
Microsoft.VisualStudio.Package.LanguageService
Assembly Version: 2.0.0.0
Win32 Version: 2.0.50727.1826 (QFE.050727-1800)
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.VisualStudio.Package.LanguageService/2.0.0.0__b03f5f7f11d50a3a/Microsoft.VisualStudio.Package.LanguageService.dll
Microsoft.SqlServer.Management.SqlParser
Assembly Version: 10.0.0.0
Win32 Version: 10.50.4000.0 ((KJ_PCU_Main).120628-0827 )
CodeBase: file:///C:/Windows/assembly/GAC_MSIL/Microsoft.SqlServer.Management.SqlParser/10.0.0.0__89845dcd8080cc91/Microsoft.SqlServer.Management.SqlParser.dll
Microsoft.SqlServer.GridControl
Assembly Version: 10.0.0.0
Win32 Version: 10.50.1600.1 ((KJ_RTM).100402-1540 )
CodeBase: file:///C:/Windows/assembly/GAC_32/Microsoft.SqlServer.GridControl/10.0.0.0__89845dcd8080cc91/Microsoft.SqlServer.GridControl.dll
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.Hi,
How many SQL Server instances were installed on the server?
Have you tried to connect this instance from another machine using SQL Server Management Studio?
1. Try the solution by Zack1223 in the link below. Delete the shell folder in C:\Users\<username>\AppData\Roaming\Microsoft\Microsoft SQL Server\100\Tools\ and check the result.
http://social.msdn.microsoft.com/Forums/sqlserver/en-US/dc67c38e-6749-4908-a9a8-d181c12b7e91/sql-server-management-studio-express-2005-keeps-crashing
2. Try to download and install shared management objects to fix this issue. Download here:
http://www.microsoft.com/en-us/download/details.aspx?id=30440
Refer to this thread:
http://social.msdn.microsoft.com/Forums/en-US/sqlsetupandupgrade/thread/9125eaae-13f5-42b1-861f-e81e2b46c1de
Hope it helps.
Tracy Cai
TechNet Community Support -
How to connect sql server 2008 r2 sp2 with vs2013 ultimate?
how to connect sql server 2008 r2 sp2 with visual studio 2013 ultimate?
Hi Shahzad,
>>how to connect sql server 2008 r2 sp2 with visual studio 2013 ultimate?
Based on your issue, if you wan to connect the sql server 2008 r2 sp2 from VS2013 IDE. I suggest you can try the Ammar and darnold924's suggestion to check your issue.
In addition, I suggest you can also refer the following steps to connect the sql server 2008 r2 sp2 with visual studio 2013 ultimate.
Step1: I suggest you can go to VIEW->SQL Server Object Explorer->Right click SQL Server->Add SQL Server.
Step2: After you connect the SQL Server 2008 r2 sp2 fine, I suggest you can go to VIEW->Server Explorer-> right click the Data Connection->Add Connection.
And then you can create the connect string in the Add Connection dialog box.
Hope it help you!
We are trying to better understand customer views on social support experience, so your participation in this interview project would be greatly appreciated if you have time. Thanks for helping make community forums a great place.
Click
HERE to participate the survey. -
Advance features available in sql server 2008 R2 compared with SQL 2008 SP2
Hi,
Can some one brief me the advance features available in sql server 2008 R2 compared with SQL Server 2008 SP2.
I am planning to upgrade my existing sql server 2008 SP2 to sql server 2008 R2, before that i need the advantages to proceed , if the advantages are not suite to my requirements then i will drop out this option.
Please give me the detailed reply for my analysis
hemadriHi Hemadribabu,
There are some new features in SQL Server 2008 Service Pack 2(SP2), including SQL Server utility, Data-tier Application (DAC), Reporting Services in SharePoint Integrated mode and partitioning improvement. Features are supported by the different editions
of SQL Server 2008 R2. For example, the Report Builder 3.0, PowerPivot for excel are available on the SQL Server Datacenter and SQL Server 2008 R2 Parallel Data Warehouse, they can assist you creating business intelligence documents. Here are the Top
new features in SQL Server 2008 R2, including
Report Builder 3.0, SQL Server 2008 R2 Datacenter, SQL Server 2008 R2 Parallel Data Warehouse,
StreamInsight, Master Data Services and so on.
For more information about SQL Server 2008R2 and SQL Server 2008 SP2, you can review the following articles.
http://msdn.microsoft.com/en-us/library/cc645993(v=sql.105).ASPX
https://social.technet.microsoft.com/wiki/contents/articles/1486.microsoft-sql-server-2008-sp2-release-notes.aspx
Regards,
Sofiya Li
Sofiya Li
TechNet Community Support -
HI,
I have installed Cumulative Update 12 for SQL Server 2008 R2 SP2 on my SharePoint instances. This was to resolve a known issue faced with the instance. CU12 helped resolve the issue. My company is rather strict regarding security hotfixes. But I am
not sure if this particular hotfix [Security Hotfix (KB2977319)] is required if the instance has CU12 applied.
Tested this on a Lab server, the installation did run fine, the summary log also stated that the KB is applied. But the Build Number did not change. Hence the doubt.
Overall summary:
Final result: Passed
Exit code (Decimal): 0
Exit message: Passed
Start time: 2014-09-06 10:31:21
End time: 2014-09-06 10:55:49
Requested action: Patch
Instance SPNTSQLTRN overall summary:
Final result: Passed
Exit code (Decimal): 0
Exit message: Passed
Start time: 2014-09-06 10:48:08
End time: 2014-09-06 10:55:45
Requested action: Patch
Package properties:
Description: SQL Server Database Services 2008 R2
ProductName: SQL2008
Type: RTM
Version: 10
SPLevel: 2
KBArticle: KB2977319
KBArticleHyperlink: http://support.microsoft.com/?kbid=2977319
PatchType: QFE
AssociatedHotfixBuild: 0
Platform: x64
PatchLevel: 10.52.4321.0
ProductVersion: 10.52.4000.0
GDRReservedRange: 10.50.4001.0:10.50.4199.0;10.50.4200.0:10.50.4250.0
PackageName: SQLServer2008-KB2977319-x64.exe
Installation location: e:\ac2af22d88ee645b5b32b5c178\x64\setup\
Please inform if I need to apply the hotfix on CU12. Thanks in advance.
John SYes you must install Security update mentioned in KB 2977319 it is important for SQL Server to be patches with this security update. Without this it could allow an attacker to compromise your system and gain control over it.
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it
My Technet Articles -
Microsoft SQL Server 2008 R2 SP2 - Express Download Link Broken
Hello there
I am installing Backup Exec 2014 and during the installation I need to provide the EXE from the "Microsoft® SQL Server® 2008 R2 SP2 - Express" installer (German version). Unfortunately the link is broken, even when I navigate from the download
page to the SQL Express download page (http://www.microsoft.com/de-de/download/details.aspx?id=30438) I always get:
We are sorry, the page you requested cannot be found.
I cannot find the German installer anywhere else in the internet, and as I just had to uninstall the old backup solution to be able to start the installer from the new one it is quite important that I get this file as quick as possible so I can get the backup
running again.
Any idea what I could do or where I could find the installer?
Thanks for you help.
Kind regards
PhilHello Phil,
yes, seems to be broken.
Download 2008 R2 SP1 (http://www.microsoft.com/de-DE/download/details.aspx?id=26729) and apply SP 2 afterwards.
Olaf Helper
[ Blog] [ Xing] [ MVP] -
JTDS not connecting with SQL Server 2008 R2 SP2 + SSL with Java 6 U34-35
Environment:
Windows 7 Pro 32-bit
SQL Server 2008 R2 SP2 (Forced Encryption = Yes, No Certificate provided to server)
Java 6 Update 27-35 and Java 7 Update 2-7
jTDS 1.2.2 and 1.2.6
Under the following setup, our Java application is able to connect to the SQL Server database:
- SQL Server 2008 R2 SP2
- Java 6 Update 27-33 or Java 7 Update 2-5
just switching the JVM to the following would cause the application to be unable to connect to the database:
- Java 6 Update 34 or 35, or Java 7 Update 6 or 7
Browsing through the Java 6 Update 34 release notes, it looks like nothing big was changed, so I'm wondering what has changed with Java 6 U34 and Java 7 U6. I was also looking through a packet sniffer, and indeed the behavior of Java 6 Update 33 and lower was different from Java 6 Update 34 (although I couldn't understand the messages being passed, the number of connections and messages were different).
* This is different from the issue with Java 6 Update 29-30 and Java 7 wherein they were patched for the BEAST SSL vulnerability. That was fixed with the SP2 patch for SQL Server 2008 R2, and for SQL Server 2008 you'd need a hotfix aside from SP3. After patching the server with those updates, Java 6 Update 29-33 and Java 7 U1-5 should be able to connect to the database.
* If I do switch off Force Encryption, all Java versions are able to connect to the database.
Edited by: user1357749 on Oct 12, 2012 1:20 AMHi,
It's four months later, but my colleague and I have reproduced the same behavior in both our commercial product, and a very simple example class. It's exactly as you describe it, where the latest versions of both Java 6 and 7 (and several previous versions) hang during the first jTDS SQL query to the DB (immediately after the SSL and handshake). It also happens with the Microsoft JDBC driver.
If you disable the BEAST SSL fix (-Djsse.enableCBCProtection=false), then the connections work without any problems. So, while this is different from the original BEAST SSL problem and subsequent fix, it really seems like some additional changes were made to the fix in a later Java release that broke things.
My colleague has filed a bug with Oracle, and is awaiting a response. We also filed a bug at the jTDS project (#690 - http://sourceforge.net/p/jtds/bugs/690/) that has simple reproduction steps. A contributer at the jTDS project agrees that this seems to be a problem with the JRE, and is not specific to jTDS.
I hope that Oracle will address this issue soon. We need to periodically update the JRE due to vulnerabilities, and we need to have SSL for our JDBC connections for security reasons. This bug puts us and others in a difficult position. -
Installing SQL Server 2008 R2 SP2 CU 13
Hi,
For one of SQL Server instances the current version is 10.50.4033(SQL Server 2008 R2 SP2 GDR).
Now I am not able to install a cumulative upgrade "2967540 Cumulative update package 13 (CU13)".
"There are no SQL Server instances or shared features that can be updated on this computer"
Is there any patch that I am missing?
SumanHello,
You may get this error when you download the 32-bit version of the update (x86) and you are trying to apply it to a 64-bit
instance of SQL Server.
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com -
Hi everyone,
Following an upgrade to SQL Server 2012 which didn't succeed, someone recommended that I repair my actual SQL Server 2008 R2 SP2 setup. The actual setup I have, which btw is running without any problem, is the following:
SQL Server 2008 R2 SP2 CU1 Express Edition with advanced services (Reporting Services is installed and active)
Visual Studio 2010 SP1 Professionnal Edition
Visual Studio 2008 SP1 Express Edition
Windows VISTA SP2 Ultimate Edition
My request is very simple. Before repairing a SQL setup:
Do I need to stop any services?
Any other thing I should stop, uninstall or else?
Do I launch the repair from the "Control Panel - Install/uninstall program" menu or can I just run the "SQL Server 2008 R2 SP2" setup file I just downloaded from the .NET. I prefer asking because I thought that running
this setup file under administrative rights could help avoiding privilege problems or else?
Hope to hear from someone,
StéphaneHi Samuel,
Thursday. 2 days I didn't hear from anyone. I still can't complete the repair because of this setup file the repair process is asking for. The setup files I could find on my disk:
C:\ProgramData\Microsoft\SQL Server 2008 Express Install\Downloads\SqlExpressWithAdv\SQLEXPRADV_x86_FRA.exe: version is 10.0.1601.1
C:\Users\All Users\Microsoft\SQL Server 2008 Express Install\Downloads\SqlExpressWithAdv\SQLEXPRADV_x86_FRA.exe: version is also 10.0.1601.1
C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\SQLServer2008R2\x86\setup100.exe
version: 10.50.4000.0 date: 2012-06-29
C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Update Cache\KB2494086\QFE\x86\setup100.exe
version: 10.50.1790.0 date: 2011-06-14
C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Update Cache\KB2507770\QFE\x86\setup100.exe
version: 10.50.1777.0 date: 2011-06-10
C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Update Cache\KB2528583\ServicePack\x86\setup100.exe
version: 10.50.2500.0 date: 2011-07-25
C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Update Cache\KB2544793\QFE\x86\setup100.exe
version: 10.50.2769.0 date: 2011-07-27
C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Update Cache\KB2630458\ServicePack\x86\setup100.exe
version: 10.50.4000.0 date: 2013-01-10
The one I recently downloaded from the web - SQLEXPRADV_x86_ENU.exe: version is
10.50.4000.0
Again which one should I choose? One of these or maybe another file?
Really hope to hear from someone!
Stéphane -
Sql server 2008 R2 SP2 -Error: 18056, Severity: 20, State: 29
HI ,
I am getting this error in sql server 2008 R2 SP2 version .
The client was unable to reuse a session with <SPID>, which had been reset for connection pooling. The failure ID is 29. This error may have been caused by an earlier operation failing. Check the error logs for failed
operations immediately before this error message.
I am getting same error messages but only SPID are different as of my knowledge this error will resolve in SP@ version but seeing now so please let me know how to resolve the issue
Thanks!
Regards,
SureshHave you upgraded to cu1 for sp2 yet?
Check this bug - http://support.microsoft.com/kb/2543687
More information -
http://blogs.msdn.com/b/psssql/archive/2013/02/13/breaking-down-18065.aspx
How are you trying to connect? Could you take a look at the physical SQL Server Error log and see if you find any other error?
Check this part of the blog (http://blogs.msdn.com/b/psssql/archive/2010/05/05/error-18056-can-be-unwanted-noise-in-certain-scenarios.aspx)
"If the above error message (note that the state number should reflect 29) is the only message in the SQL Server Errorlog along with no other errors noticed in the environment
(connectivity failures to the SQL instance in question, degraded performance, high CPU usage, Out of Memory errors), then this message can be treated as benign and safely ignored."
Regards, Ashwin Menon My Blog - http:\\sqllearnings.com
Maybe you are looking for
-
How do I save emails that have been sent
on some other service providers, there are files called "sent mail" where those are saved automatically. How do I set up to do that on my yahoo mail account.
-
How to connect smart phone to eprint
How do I connect and print from my android phone
-
Macbook pro trying to download multiple copies of Yosemite
My macbook pro is trying to download two copies of Yosemite, and it is completely gumming up both the computer and my network. How do I stop it? thanks!
-
I have just imported four one hour tapes of HD video. They were taken on a recent safari and were imported into FCE as "Africa 1", "Africa 2" ect. Each has since been automatically subdivided into multiple (over 300) individual clips, "Africa 1-1", "
-
TS1702 I would like to remove an app on my I Phone 4 How do I remove a duplicated app
I have a duplicated App on my I Phone 4. How do I remove it?