Tuesday, January 14, 2014

The user running validate, does not have permissions to create computer objects in the 'somedomain.com' domain.

This one of the common problem occurring while building a SQL Server Cluster , this is basically due to lack of permission for the SQL Service Account To Fix the issue follow the following steps:

STEPS:
=====

1. Make sure that you know the name that the cluster will have, and the name of
the user account that will be used by the person who creates the cluster. (Note
that you can use that account to perform this procedure.)
2. On a domain controller, click Start, click Administrative Tools, and then click
Active Directory Users and Computers. If the User Account Control dialog box
appears, confirm that the action it displays is what you want, and then click
Continue.
3. In the console tree, right-click Computers or the default container in which
computer accounts are created in your domain. Computers is located in Active
Directory Users and Computers/domain node/Computers.
4. Click New and then click Computer.
5. Type the name that will be used for the failover cluster, in other words, the
cluster name that will be specified in the Create Cluster wizard, and then click
OK.
6. Right-click the account that you just created, and then click Disable Account.
If prompted to confirm your choice, click Yes.
The account must be disabled so that when the Create Cluster wizard is run, it can
confirm that the account it will use for the cluster is not currently in use by an
existing computer or cluster in the domain.
7. On the View menu, make sure that Advanced Features is selected.
When Advanced Features is selected, you can see the Security tab in the properties
of accounts (objects) in Active Directory Users and Computers.
8. Right-click the folder that you right-clicked in step 3 , and then click
Properties.
9. On the Security tab, click Advanced.
10. Click Add, click Object Types and make sure that Computers is selected, and
then click OK. Then, under Enter the object name to select, type the name of the
computer account you just created, and then click OK. If a message appears, saying
that you are about to add a disabled object, click OK.
11. In the Permission Entry dialog box, locate the Create Computer objects
permission, and make sure that the Allow check box is selected.
12. Click OK until you have returned to the Active Directory Users and Computers
snap-in.
13. If you are using the same account to perform this procedure as will be used to
create the cluster, skip the remaining steps. Otherwise, you must configure
permissions so that the user account that will be used to create the cluster has
full control of the computer account you just created:
14. On the View menu, make sure that Advanced Features is selected.
15. Right-click the computer account you just created, and then click Properties.
16. On the Security tab, click Add. If the User Account Control dialog box appears,
confirm that the action it displays is what you want, and then click Continue.
17. Use the Select Users, Computers, or Groups dialog box to specify the user
account that will be used when creating the cluster. Then click OK.
18. Make sure that the user account that you just added is selected, and then, next
to Full Control, select the Allow check box.



Wednesday, November 20, 2013

SQL Server 2005 Installation Failure with Windows Installer installed the product. Product Name: Microsoft Office 2003 Web Components. Product Version: 11.0.6558.0. Product Language: 1033. Installation success or error status: 1635. MainEngineThread is returning 1635 + OWC11SP3.MSP + Microsoft Office 2003 Web Components -- Installation failed.

Today i was working on an installation failure ,For SQL Server 2005 in Windows Sever 2003, I was reviewing the logs and from the logs .

FROM THE LOGS:
==============

MSI (s) (D0:54) [19:29:01:692]: Unable to create a temp copy of patch 'OWC11SP3.msp'.
MSI (s) (D0:54) [19:29:01:692]: Searching provided command line patches for patch code {34E1EB8F-BDB2-475C-BD80-A86217C41B4D}
MSI (s) (D0:54) [19:29:01:692]: Note: 1: 1708
MSI (s) (D0:54) [19:29:01:692]: Product: Microsoft Office 2003 Web Components -- Installation failed.
MSI (s) (D0:54) [19:29:01:692]: Windows Installer installed the product. Product Name: Microsoft Office 2003 Web Components. Product Version: 11.0.6558.0. Product Language: 1033. Installation success or error status: 1635.
MSI (s) (D0:54) [19:29:01:692]: MainEngineThread is returning 1635

I got stumbled with the issue, and i was researching a lot and finally fixed the issue.

STEPS FOLLOWED:
===============
1.Downloaded the OWC from http://www.microsoft.com/en-us/download/details.aspx?id=22276.
2.Tried to install the OWC.
3.Installation Failed an so identified that there is problem with the previous installation and it was corrupted.
4.Took a backup of the Registry.
5.Renamed the Registry Key HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Products\90404A0900063D11C8EF10054038389C
to HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Products\OLD_90404A0900063D11C8EF10054038389C.
6. Reinstalled the OWC.
7.Restarted the SQL Installation and it completed successfully.

Hope this finds Interesting.

Saturday, November 16, 2013

Error result: -2058354685, Result facility code: 1360,Result error code: 3

Today i was working on a hot fix installation failure, and to fix the issue i checked the logs and from the logs

2013-11-16 16:48:59 Slp:
2013-11-16 16:48:59 Slp: Error result: -2058354685
2013-11-16 16:48:59 Slp: Result facility code: 1360
2013-11-16 16:48:59 Slp: Result error code: 3

To resolve the issue i did the following troubleshooting steps.

ACTION PLAN:
=============

  • Uninstall The patch for the all the components of SQL Server.
  • Took the Backup Of Registry.
  • Modify the value for the Registry Key MPT_AGENT_CORE_CNI Under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\Configuration State from 4 to 1.
  • Rebooted the server.
  • Checked if the build Number has change to 10.50.2500.
  • Stopped SQL SERVER and WMI Interface.
  • Re install the patch.
  • But the Above steps failed with the same error message.
  • Stopped Windows Management Instrumentation Service and the other dependencies on it.
  • Renamed the file  perf-MSSQL10_50.MSSQLSERVER in the location c:\windows\system32 and c:\windows\SysWOW64 to old_perf-MSSQL10_50.MSSQLSERVER.
  • Ran the setup again and asked for a reboot and the server was rebooted.
  • Started the setup again and it ran successfully.

Tuesday, November 5, 2013

Error: 9004 Severity: 21 State: 1

Today i saw a DB was in Recovery state and i wanted to check why it was in recovery state for a log time, so i checked the SQL Error Log and from the Error log i found the below error Message.

ERROR MESSAGE:
==============
An error occurred while processing the log for database 'X'.  If possible restore from backup. If a backup is not available<c/> it might be necessary to rebuild the log.

11/04/2013 21:17:29,spid17s,Unknown,Error: 9004<c/> Severity: 21<c/> State: 1.

CAUSE:
======

The Transaction Log File is Corrupted.

Resolution :
========

Fix the corruption by restoring from the latest backup or Rebuild the log file.

Can not rename the database name because it is published or it is a distribution database used by replication. (Microsoft SQL Server, Error: 18855

Today i was on a corruption issue, and i had to rename a database and when attempted to restore the database i got the below error message.

Error Message:

 ==================================
Can not rename the database name because it is published or it is a distribution database used by replication. (Microsoft SQL Server, Error: 18855.

Cause:
====

The newly Created the database is a part of replication confirmed this from the column IS_PUBLISHED of sys.databases system view.

Resolution:
=======

Fixed the issue by Removing the Replication from the database by issuing the below command .

sp_removedbreplication @dbname=name of the db.

Thursday, October 24, 2013

DRIVES NOT LISTING ON SSMS WHILE CREATING MAINTENANCE PLAN

The Recently added Luns(added as drives from windows) were not getting listed in the cluster SQL Server.
When I tried backing up the database through scripts mentioning the newly added drives the backup was successful.When We we tried to create  a maintenance plan , I was not able to see the drives from there.

FROM SSMS New query window I issued XP_FIXDRIVES , I was able to see all the drives including the newly added drives .

To fix the issue ,

  • From the Cluster administrator brought the newly created drives offline.
  • Brought the SQL Services offline.
  • From the properties of SQL Services -->Dependencies -->Modify-->Added the drives.
  • Brought the SQL Services online.
  • Disconnected the Management Studio and connected back to Management  Studio.

Now I again tried to create maintenance plan, I was able to see the Drives Successfully.