manjunathcbhat's blog

The setup has encountered an unexpected error while Setting Internal Properties. The error is: Fatal error during installation

During uninstallation of Microsoft SQL Server 2005 or uninstallation of Microsoft SQL Server Service pack, you may encounter the below error

"The setup has encountered an unexpected error while Setting Internal Properties. The error is: Fatal error during installation"

Create User and assign permission failed for user on ReadOnly RO Database

There will be scenarios due to business needs you have to set your database to ReadOnly(RO) mode. When the database is RO mode, you may sometimes want to create a User on that RO database and assign some permission to it. But this fails giving error "Failed to update database "" because the database is read-only."

This is because when a Database is in ReadOnly Mode, you cannot create user or assign permission to it. To achieve this you need to bring back the database to ReadWrite mode, create user assign permission and then again set the database to RO mode.

General Approach To SQL Server Performance Tuning

General Approach to Performance Tuning

Examine the Nature of Software/Application which uses the SQL Server.

Gather the average number of users/sessions during peak hours/non-peak hours.

Gather/Review the existing hardware

  1. RAM
  2. CPU
  3. Hard Disk
  4. Disk level
  5. Physical server or virtual server

Gather information on various network bandwidth/latency/limitations

Gather the exiting SQL Server Maintenance Plans

Edition Upgrade SQL Server Step by Step Instruction

I was wondering how can I upgrade my SQL Server Edition. Say I have a SQL Server Standard edition installed on one of my Server. Now due to some business needs, I need to upgrade my SQL Server Standard Edition to SQL Server BI Edition. I was able to achieve this and have documented these step by step instruction below. This is for Microsoft SQL Server Edition Upgrade from Standard Edition Installation to BI Edition Installation. This edition Upgrade Does not need any Re-Boot of server until there is any dependency.

The login packet used to open the connection is structurally invalid; the connection has been closed. Please contact the vendor of the client library.[]

There can be many reasons for a Login Failure to SQL Server Instance.

Out of this you may get one as "The login packet used to open the connection is structurally invalid; the connection has been closed. Please contact the vendor of the client library.[]"

This error may occur when The SQL Server computer was unable to process the client login packet. Inside the square braces, will be the IP of the client from which they are trying to login.

ReportServer: Deleting Encryption Key in SQL Server Reporting Services Configuration Manager

Below are the steps to Delete the Encryption Key in SQL Server Reporting Services Configuration.

Before Deleting make sure you have taken a backup of your Current Encryption Keys. Click Here to see the procedure to take a backup if not already.

Reporting Server Error: The report server installation is not initialized

This is another Error related to Reporting Services.

You might come across this error after a fresh New installation of SQL Server Reporting Services or You have restored/Migrated a ReportServer Database as i described in my previous post.

Click Here to Check out the Migration/restoration of ReportServer Databases.

Once you are done with the Migration/Restoration of your ReportServer Databases you might come across this errors.

Pages