Problem Description:
=======================================================================
Throwing the below error while setting the web service identity in configure report server
System.Runtime.InteropServices.COMException (0x800706B3)
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
at System.Management.ManagementObject.Get()
at ReportServicesConfigUI.WMIProvider.RSReportServerAdmin.SetDatabaseConnection(String server, String database, ConfigurationCredentialsType credsType, String userName, String password)
Troubleshooting steps:
=======================================================================
Checked the reporting services configuration server.
Execution account was enabled. Unchecked it; Specify an execution account checkbox should not be checked.
Created new report server virtual directory and report manager virtual directory through the reporting services configuration server tool.
Windows service identity was set to built in account --- Network service
In Webservice identity; created new app pools for Report Server and Report Manager using reporting services configuration server tool.
If while creating new app pools you get the above error go to encryption keys and hit on delete button.
Once encryption keys are deleted Try recreating the app pools once again and it should create fine without any errors
Resolution:
=======================================================================
Reports coming up fine when we browse http://localhost/reportserver and http://localhost/reports
Tuesday, November 18, 2008
SQL Server does not exist or access denied.
Cause:
=======================================================================
Not enabled protocols on SQLExpress box as well as client box
Firewall blocking issue of port and service
Resolution:
=======================================================================
1. Checked the protocols whether its enabled
2. Ran the command cliconfg from start---Run on local box and enabled both tcp/ip and named pipes
3. Done the same on the SQLExpress box
4. went to SQLServer 2005 Surface area configuration and changed the services and connections set the local and remote connections to use both tcp/ip and named pipes
5. Typed in start---run----firewall.cpl
6. Went to exceptions tab and added the following services to it
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\sqlservr.exe executable program
C:\Program Files\Microsoft SQL Server\90\Shared\sqlbrowser.exe executable program
7. Add the port of SQLExpress 1433 to exception list
8. Restarted the service
9. browsed the application and it was working fine without any errors.
=======================================================================
Not enabled protocols on SQLExpress box as well as client box
Firewall blocking issue of port and service
Resolution:
=======================================================================
1. Checked the protocols whether its enabled
2. Ran the command cliconfg from start---Run on local box and enabled both tcp/ip and named pipes
3. Done the same on the SQLExpress box
4. went to SQLServer 2005 Surface area configuration and changed the services and connections set the local and remote connections to use both tcp/ip and named pipes
5. Typed in start---run----firewall.cpl
6. Went to exceptions tab and added the following services to it
C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Binn\sqlservr.exe executable program
C:\Program Files\Microsoft SQL Server\90\Shared\sqlbrowser.exe executable program
7. Add the port of SQLExpress 1433 to exception list
8. Restarted the service
9. browsed the application and it was working fine without any errors.
Friday, November 14, 2008
Cannot generate SSPI context
How to troubleshoot the "Cannot generate SSPI context" error message
http://support.microsoft.com/kb/811889
Usually this drills down to improper SPN [Service principal Name] Not registered properly
Related Knowledge Base Articles
===========================
Troubleshooting Kerberos Errors
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/technologies/security/tkerberr.mspx
How to enable Kerberos event logging
http://support.microsoft.com/kb/262177
How to troubleshoot the "Cannot generate SSPI context" error message
http://support.microsoft.com/kb/811889
How to make sure that you are using Kerberos authentication when you create a
remote connection to an instance of SQL Server 2005
http://support.microsoft.com/kb/909801/en-us
Security Account Delegation
http://msdn2.microsoft.com/en-us/library/aa905162(SQL.80).aspx
SQL Linked Server Query failed with “Login failed for user …”
http://blogs.msdn.com/sql_protocols/archive/2006/08/10/694657.aspx
Windows 2000 Resource Kit Tool : Setspn.exe
http://www.microsoft.com/downloads/details.aspx?FamilyID=5fd831fd-ab77-46a3-9cfe-ff01d29e5c46&displaylang=en
Windows Server 2003 Service Pack 2 32-bit Support Tools
http://www.microsoft.com/downloads/details.aspx?FamilyID=96a35011-fd83-419d-939b-9a772ea2df90&DisplayLang=en
http://support.microsoft.com/kb/811889
Usually this drills down to improper SPN [Service principal Name] Not registered properly
Related Knowledge Base Articles
===========================
Troubleshooting Kerberos Errors
http://www.microsoft.com/technet/prodtechnol/windowsserver2003/technologies/security/tkerberr.mspx
How to enable Kerberos event logging
http://support.microsoft.com/kb/262177
How to troubleshoot the "Cannot generate SSPI context" error message
http://support.microsoft.com/kb/811889
How to make sure that you are using Kerberos authentication when you create a
remote connection to an instance of SQL Server 2005
http://support.microsoft.com/kb/909801/en-us
Security Account Delegation
http://msdn2.microsoft.com/en-us/library/aa905162(SQL.80).aspx
SQL Linked Server Query failed with “Login failed for user …”
http://blogs.msdn.com/sql_protocols/archive/2006/08/10/694657.aspx
Windows 2000 Resource Kit Tool : Setspn.exe
http://www.microsoft.com/downloads/details.aspx?FamilyID=5fd831fd-ab77-46a3-9cfe-ff01d29e5c46&displaylang=en
Windows Server 2003 Service Pack 2 32-bit Support Tools
http://www.microsoft.com/downloads/details.aspx?FamilyID=96a35011-fd83-419d-939b-9a772ea2df90&DisplayLang=en
An internal error occurred on the report server.
Problem Description:
=======================================================================
Older 2000 server and wanting to move reporting services to SQL 2005
An internal error occurred on the report server. See the error log for more details. (rsInternalError) Get Online Help Key not valid for use in specified state.
Steps:
=======================================================================
1. From Explorer, navigate to x:\Documents and Settings\\Application Data\Microsoft\Crypto\RSA\S-1-5-20. In this case, the folder was C:\Documents and Settings\NetworkService\Application Data\Microsoft\Crypto\RSA\S-1-5-20.
2. Search for files with the pattern "1aedd7b5699f3d6a88e354100b596aae_*". These files represent the Microsoft SQL Server Reporting Services Key Container.
3. Delete these files.
Removing encrypted content, reconfiguring the SQL Server login account, and activating the report server:
rskeymgmt.exe -d
rsconfig.exe -e -s -d -a Windows -u -p -t
now restarted the service
Browsed the reports it works fine.
Restored the backup DB of reportserver and reportservertempdb on the dc02 box
Now pointed the reports to fetch the data from the DC02 Machine using the below command.
rsconfig -c -m -s -d reportserver -a SQL -u SA -p
Resolution:
=======================================================================
Now able to browse the reports after success fully migrating from 2000 to 2005.
=======================================================================
Older 2000 server and wanting to move reporting services to SQL 2005
An internal error occurred on the report server. See the error log for more details. (rsInternalError) Get Online Help Key not valid for use in specified state.
Steps:
=======================================================================
1. From Explorer, navigate to x:\Documents and Settings\
2. Search for files with the pattern "1aedd7b5699f3d6a88e354100b596aae_*". These files represent the Microsoft SQL Server Reporting Services Key Container.
3. Delete these files.
Removing encrypted content, reconfiguring the SQL Server login account, and activating the report server:
rskeymgmt.exe -d
rsconfig.exe -e -s
now restarted the service
Browsed the reports it works fine.
Restored the backup DB of reportserver and reportservertempdb on the dc02 box
Now pointed the reports to fetch the data from the DC02 Machine using the below command.
rsconfig -c -m
Resolution:
=======================================================================
Now able to browse the reports after success fully migrating from 2000 to 2005.
Unable to install SRS2000; Error code 1603
Problem Description:
=======================================================================
Unable to install SRS2000; Error code 1603
Cause:
=======================================================================
Not properly removed the SRS2000.
Need to manually reconfigure it.
Done the below steps as mentioned in the resolution.
Resolution:
=======================================================================
Checked for all the below ones and manually made sure that they are deleted
a. Default locations:
i. C:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services
ii. C:\Program Files\Microsoft SQL Server\80\Tools\Report Designer
iii. C:\Program Files\Microsoft SQL Server\80\Tools\Reporting Services
b. Remove tools items (C:\Program Files\Microsoft SQL Server\80\Tools\Binn)
i. ReportingServices.mof
ii. Rs.exe
iii. RSConfig.exe
iv. RSActivate.exe
v. RSKeyMgmt.exe
vi. ReportingServicesWmi.dll
vii. Resource folders
1. All Languages (DE, ES, etc)
2. 1033
4) Made sure the Virtual Directories were removed.
Removed Report Server dlls
5) Removed Registry Entries
a. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\80\Reporting Services
6) Made sure the Databases were removed.
a. Default names are ReportServer and ReportServerTempDB
After that, we were able to install Reporting Services successfully after following the above steps.
=======================================================================
Unable to install SRS2000; Error code 1603
Cause:
=======================================================================
Not properly removed the SRS2000.
Need to manually reconfigure it.
Done the below steps as mentioned in the resolution.
Resolution:
=======================================================================
Checked for all the below ones and manually made sure that they are deleted
a. Default locations:
i. C:\Program Files\Microsoft SQL Server\MSSQL\Reporting Services
ii. C:\Program Files\Microsoft SQL Server\80\Tools\Report Designer
iii. C:\Program Files\Microsoft SQL Server\80\Tools\Reporting Services
b. Remove tools items (C:\Program Files\Microsoft SQL Server\80\Tools\Binn)
i. ReportingServices.mof
ii. Rs.exe
iii. RSConfig.exe
iv. RSActivate.exe
v. RSKeyMgmt.exe
vi. ReportingServicesWmi.dll
vii. Resource folders
1. All Languages (DE, ES, etc)
2. 1033
4) Made sure the Virtual Directories were removed.
Removed Report Server dlls
5) Removed Registry Entries
a. HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\80\Reporting Services
6) Made sure the Databases were removed.
a. Default names are ReportServer and ReportServerTempDB
After that, we were able to install Reporting Services successfully after following the above steps.
SQLState: S0001, Message: The server failed to resume the transaction. Desc:3600000000
Problem Description:
=======================================================================
When web based java application is connecting to SQL server 2005 backend through JDBC, they are getting error message
SQLState: S0001, Message: The server failed to resume the transaction. Desc:3600000000., Vendor Error Code: 3971
Cause:
=======================================================================
Here are the scenarios that you might get this error message (“failed to resume the transaction”):
• A nested stored procedure is called
• Stored procedure returns output parameters
• A deadlock occurs. After waiting, the stored procedure is executed again and receives "failed to resume transaction"
Workaround/Resolution:
=======================================================================
Here is some of the work around being prescribed since we have started seeing the issue:
1) Use PreparedStatement in lieu of Statement. This ensures that outstanding TDS packets are parsed when close() is called.
2) Call Statement.getMoreResults() and Statement.getUpdateCount() until those functions indicate there are no more results to be processed. This ensures that all outstanding TDS packets are parsed.
=======================================================================
When web based java application is connecting to SQL server 2005 backend through JDBC, they are getting error message
SQLState: S0001, Message: The server failed to resume the transaction. Desc:3600000000., Vendor Error Code: 3971
Cause:
=======================================================================
Here are the scenarios that you might get this error message (“failed to resume the transaction”):
• A nested stored procedure is called
• Stored procedure returns output parameters
• A deadlock occurs. After waiting, the stored procedure is executed again and receives "failed to resume transaction"
Workaround/Resolution:
=======================================================================
Here is some of the work around being prescribed since we have started seeing the issue:
1) Use PreparedStatement in lieu of Statement. This ensures that outstanding TDS packets are parsed when close() is called.
2) Call Statement.getMoreResults() and Statement.getUpdateCount() until those functions indicate there are no more results to be processed. This ensures that all outstanding TDS packets are parsed.
Questions on Subscriptions and Jobs in SSRS
Articles:
=======================================================================
http://msdn2.microsoft.com/en-us/library/aa237763(SQL.80).aspx---Managing Subscriptions
http://msdn2.microsoft.com/en-us/library/aa237786(sql.80).aspx---Subscription Overview
http://msdn2.microsoft.com/en-us/library/aa237767(SQL.80).aspx---Creating, Modifying, and Deleting Subscriptions
http://msdn2.microsoft.com/en-us/library/aa237758(SQL.80).aspx---Using Role-Based Security
http://msdn2.microsoft.com/en-us/library/aa225485(SQL.80).aspx---New Role Assignment / Edit Role Assignment Page
http://msdn2.microsoft.com/en-us/library/ms190387.aspx---User-Schema Separation
http://msdn2.microsoft.com/en-us/library/ms188676.aspx---Ownership Chains
=======================================================================
http://msdn2.microsoft.com/en-us/library/aa237763(SQL.80).aspx---Managing Subscriptions
http://msdn2.microsoft.com/en-us/library/aa237786(sql.80).aspx---Subscription Overview
http://msdn2.microsoft.com/en-us/library/aa237767(SQL.80).aspx---Creating, Modifying, and Deleting Subscriptions
http://msdn2.microsoft.com/en-us/library/aa237758(SQL.80).aspx---Using Role-Based Security
http://msdn2.microsoft.com/en-us/library/aa225485(SQL.80).aspx---New Role Assignment / Edit Role Assignment Page
http://msdn2.microsoft.com/en-us/library/ms190387.aspx---User-Schema Separation
http://msdn2.microsoft.com/en-us/library/ms188676.aspx---Ownership Chains
Subscribe to:
Posts (Atom)