I was working on setting up a new SQL 2005 Veritas cluster today and came upon this error:
Event Type: Error
Event Source: Had
Event Category: None
Event ID: 11306
Date: 10/20/2008
Time: 1:30:40 PM
User: N/A
Computer: XXXXXXXX
Description:
Did not receive cluster membership, manual intervention may be needed for seeding
What does that mean??
It means you need to drop to a command prompt and do this:
gabconfig -x
That'll reseed the control port and should bring the cluster node back into membership. It worked for me and it'll probably work for you too!
Cheers!
Monday, 20 October 2008
Friday, 9 May 2008
Windows Update and Error 0x8DDD0018 -FIX
I was having a hell of a time trying to get a Windows 2003 R2 Standard x64 server to load the Windows Update site. I was always getting the error: 0x8DDD0018
Sadly, the troubleshooting info at MS focused on starting the BITS service which (seemingly) was working just fine.
Well, I eventually stumbled on the solution. Try this at a command prompt:
regsvr32.exe wuaueng.dll
Presto! Windows Updates should be working for you again :)
Sadly, the troubleshooting info at MS focused on starting the BITS service which (seemingly) was working just fine.
Well, I eventually stumbled on the solution. Try this at a command prompt:
regsvr32.exe wuaueng.dll
Presto! Windows Updates should be working for you again :)
64bit (x64 and Itanium) OLEDB provider for ODBC (MSDASQL) Download!
If you've ever tried to link a 64bit SQL 2005 server to something like Excel or MySQL you know that it just isn't going to happen without MSDASQL .
Well, it's finally out! Get it right from MS here: http://www.microsoft.com/downloads/details.aspx?FamilyID=000364db-5e8b-44a8-b9be-ca44d18b059b&displaylang=en
Here's the description from the MS download:
The Microsoft OLE DB Provider for ODBC (MSDASQL) is a technology that allows applications that are built on OLEDB and ADO (which uses OLEDB internally) to access data sources through an ODBC driver. MSDASQL is an OLEDB provider that connects to ODBC, instead of a database. MSDASQL ships with the Windows operating system, and Windows Server 2008 & Windows Vista SP1 are the first Windows releases to include a 64-bit version of the technology.
Enjoy!!
Well, it's finally out! Get it right from MS here: http://www.microsoft.com/downloads/details.aspx?FamilyID=000364db-5e8b-44a8-b9be-ca44d18b059b&displaylang=en
Here's the description from the MS download:
The Microsoft OLE DB Provider for ODBC (MSDASQL) is a technology that allows applications that are built on OLEDB and ADO (which uses OLEDB internally) to access data sources through an ODBC driver. MSDASQL is an OLEDB provider that connects to ODBC, instead of a database. MSDASQL ships with the Windows operating system, and Windows Server 2008 & Windows Vista SP1 are the first Windows releases to include a 64-bit version of the technology.
Enjoy!!
Tuesday, 1 April 2008
Need to transfer logins from one SQL 2005 instance to another SQL 2005 instance? Here's how!
In SQL 2000 there was a DTS package that could do this. I didn't like DTS and never used it, but it is out there. I used the Microsoft-provided sp_help_revlogin stored procedure instead to do this in 2000, but when I looked at the code I realized it would need an update for 2005.
In 2005 the sys.syslogins view exits, but you really shouldn't use it- you should use sys.server_principals (see books online). So, when I looked at that system view I realized this was really going to take some work... so naturally I Googled! ;)
Anyways, I found out that good-ol' MS had already updated the TSQL that generates sp_help_revlogin (and it's required binary stored proc) and posted it online in KB 918992. I copied the code and it worked just like it always had except that I was able to transfer the logins with SIDs and passwords from one 2005 instance to another instead of a 2000 to 2005 or 2000 to 2000 instance. :)
http://support.microsoft.com/kb/918992
In 2005 the sys.syslogins view exits, but you really shouldn't use it- you should use sys.server_principals (see books online). So, when I looked at that system view I realized this was really going to take some work... so naturally I Googled! ;)
Anyways, I found out that good-ol' MS had already updated the TSQL that generates sp_help_revlogin (and it's required binary stored proc) and posted it online in KB 918992. I copied the code and it worked just like it always had except that I was able to transfer the logins with SIDs and passwords from one 2005 instance to another instead of a 2000 to 2005 or 2000 to 2000 instance. :)
http://support.microsoft.com/kb/918992
Subscribe to:
Posts (Atom)