SQL SERVER – FIX : Error : Windows Update; Error Code 8000FFFF

At present, I am running Windows Vista Ultimate as OS in my computer. I have installed SQL Server 2008 developer’s version in my computer.

A couple of months back, I learnt that SQL Server Book On-Line (BOL) update has been released. I usually depend on my Windows Update of SQL Server to install all updates in my OS, so I do not have to  bother myself with installing updates manually.

However, this time I was quite taken aback to find that my computer was not updated with the latest updates released by Microsoft. Further, I noticed that my SQL Server Book On-Line is not up to date. This experience was nerve-wracking, as I expected my computer to have all the latest updates. I probed into the matter and found that there was an issue with some previous incomplete updates available with Windows Update. I was getting vexed with the following error every time I tried to run Windows Update.

Windows Update; Error Code 8000FFFF

I attempted to reboot, uninstall antivirus but had no luck fixing this error. I finally sent out an email to my friend who is expert in troubleshooting OS issues.  He sent me some steps to resolve the issue.

Fix/Solution/Workaround:

After I performed the following steps, windows updated started to work normally and I was able to successfully download all SQL Server related updates.

  1. Click on Windows button and search ‘regedit’.
  2. Right click on the regedit and “Run as Administrator” (See Image 1).
  3. Go to HKEY_LOCAL_MACHINE >> COMPONENTS and look for keys described in steps 4, 5 and 6. In the absence of  any  key  go to  the next step (See Image 2).
  4. Find key PendingXmlIdentifier and delete it.
  5. Find key NextQueueEntryIndex and delete it.
  6. Find key AdvancedInstallersNeedResolving and delete it.
  7. Restart the computer.
  8. Once restarted now attempt Windows Updates;  it  should work fine now.

Do let me know if this solution helps you.

Image1
Image2

Reference : Pinal Dave (http://blog.SQLAuthority.com)

About these ads

SQL SERVER – Clear Drop Down List of Recent Connection From SQL Server Management Studio

Quite often it happens that SQL Server Management Studio’s Dropdown box is cluttered with many different SQL Server’s name. Sometime it contains the name of the server which does not exist or developer does not have access to it. It is very easy to clean the list and start over.

Delete mru.dat file from following location.

For SQL Server 2005:
C:\Documents and Settings\<user>\Application Data\Microsoft\Microsoft SQL Server\90\Tools\Shell\mru.dat

If you can not find mru.dat at above location look for mru.dat in following folder.
C:\Documents and Settings\[user]\Application Data\Microsoft\Microsoft SQL Server\90\Tools\ShellSEM\mru.dat

For SQL Server 2008:
C:\Documents and Settings\<user>\Application Data\Microsoft\Microsoft SQL Server\100\Tools\Shell\mru.dat

If you can not find mru.dat at above location look for mru.dat in following folder.
C:\Documents and Settings\[user]\Application Data\Microsoft\Microsoft SQL Server\100\Tools\ShellSEM\mru.dat

If you are using VISTA OS instead of XP OS. Replace C:\Documents and Settings\[user]\Application Data\Microsoft\ with
C:\Users\\AppData\Roaming\Microsoft\ and it should work.

Make sure to take note down any IP address of SQL Server you may need in future.

Watch the video on the same subject:

Reference : Pinal Dave (http://www.SQLAuthority.com)

SQL SERVER – Create Database Error in Windows Vista

I recently receive question from one of the blog reader that he is having problem creating database in Windows Vista. Read original comment here.

I have installed vista ultimate and sql server 2005 developer edition in my computer.I also connect SQL 2005 in window authentication but when I CREATE any database in following query

CREATE DATABASE MANEESH
USE MANEESH

Its give me everytime following error:-
Msg 262, Level 14, State 1, Line 1
CREATE DATABASE permission denied in database ‘master’.
&
Msg 911, Level 16, State 1, Line 1
Could not locate entry in sysdatabases for database ‘maneesh’. No entry found with that name. Make sure that the name is entered correctly.

But i entered name correctly.and i am not making anytype tabels in sql2005. Solve these problem please.

Solution to above problem is very simple and I have already posted solution for this in my earlier article. SQL SERVER 2005 – FIX Error: 18456 : VISTA Windows Authentication

Reference : Pinal Dave (http://blog.SQLAuthority.com)

SQL SERVER 2005 – FIX Error: 18456 : VISTA Windows Authentication

In previous post I have mentioned about SQL SERVER 2005 – Vista Ultimate and SQL Server 2005 DEV Edition. There was one simple issue with the installation. I was not able to login using windows authentication method. I was able to successful login using sa username and password.

I kept on receiving following error.

TITLE: Connect to Server
——————————
Cannot connect to SQLAUTHORITY.
——————————
ADDITIONAL INFORMATION:

Login failed for user ‘SQLAUTHORITY\Pinal’. (Microsoft SQL Server, Error: 18456)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=18456&LinkId=20476

——————————
BUTTONS:
OK
——————————

After a while I realize that this may be due to one needs Administrator rights to do any task in SQL Server. I added the my current login as administrator in SQL Server and next time I was able to login successfully using Windows Authentication.

Following diagrams explains the fix.

1. Error while using Windows Authentication

2. Login using SA username and password and go to Security >> New Login

3. Type In Login Name as ComputerName\UserName

4. Click Server Roles and check sysadmin server role, after that click OK.

5. Now login using Windows Authentication and it should work fine.

Reference : Pinal Dave (http://blog.SQLAuthority.com)

SQL SERVER 2005 – Vista Ultimate and SQL Server 2005 DEV Edition

I have been asked many times before “Does SQL Server Dev edition can be installed on Vista operating system?”

I decided to find out the answer of this myself. I have just got new system which has Vista Ultimate Installed on it. I installed SQL Server 2005 dev edition on it. While installing it suggested that there are few component will not work with Vista and to make them work make sure to install SQL Server 2005 SP2. I was any way planning to install that. Once installation of SQL Server 2005 over, I installed SQL Server 2005 SP2. After restart I ran SQL Server 2005 and it just worked fine.

I am loving the combination of SQL Server 2005 and Vista Ultimate.

Reference : Pinal Dave (http://blog.SQLAuthority.com)

SQLAuthority News – Fix : Remote Desktop Copy Paste Stop Working

Today’s article is not related to SQL Server 100%, however it is quite related to SQL Server, or atleast I found it while working with SQL Server. Just two days ago, while I was working with remote SQL Server using Remote Desktop tool provided by Windows XP. Suddenly, copy/paste feature of windows stop working on remote desktop. I was not able to copy from local machine to remote machine and remote machine to local machine, both ways. I was able to copy/paste from remote machine to remote machine and local machine to local machine.

I thought may be if I restart both the computers it will work (Do not restart your live servers in any case, also restarting is not the solution please read the solution at the end of article). It did not work. I played with few administrative services, again no luck. I was very frustrated for two days as it was very inconvenient to copy/paste and I did not had solution.

After playing with different services and process for a while I found following solution. The solution works perfectly.

First of all go to task manager in remote machine. Go to processes and kill process rdpclip.exe.
After that to go Start >> Run >> type rdpclip.exe and press OK.

This will fix your remote desktop copy/paste issue.

If you want to share files across remote desktop. Follow following instructions.

Go to Remote Desktop Connections >> Options >> Local Resources >> Local Devices >> Turn on Checkbox of Disk drives and click Connect.

I hope today’s article will help users who are facing this problem.

Reference : Pinal Dave (http://www.SQLAuthority.com)