http://www.clusterhelp.com/
http://www.msmvps.com/clustering
http://www.nw-america.com
Wednesday, August 09, 2006
Monday, June 26, 2006
Error: 5180, Severity: 22, State: 1
Error: 5180, Severity: 22, State: 1
Could not open FCB for invalid file ID 0 in database '%s'. Table or database may be corrupted.
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q276043
Could not open FCB for invalid file ID 0 in database '%s'. Table or database may be corrupted.
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q276043
Friday, June 16, 2006
TargetServersRole
Use this "TargetServersRole" available on SQL Server 2000 SP3 and above to grant users who requires to view the all the jobs listed on SQL Server for a normal user.
Use msdb
Use msdb
EXEC sp_addsrvrolemember 'Corporate\HelenS', 'TargetServersRole'
Friday, June 09, 2006
Logshipping vs Database Mirroring
Applies to : SQL Server 2005
With Log Shipping:
Data Transfer: T-Logs are backed up and transferred to secondary server
Transactional Consistency: All committed and un-committed are transferred
Server Limitation: Can be applied to multiple stand-by servers
Failover: Manual Failover Duration: Can take more than 30 mins
Role Change: Role change is manual
Client Re-direction: Manual changes required
With Database Mirroring:
Data Transfer: Individual T-Log records are transferred using TCP endpoints
Transactional Consistency: Only committed transactions are transferred
Server Limitation: Can be applied to only one mirror server
Failover: AutomaticFailover
Duration: Failover is fast, sometimes <>
Role Change: Role change is fully automatic
Client Re-direction: Fully automatic as it uses .NET 2.0
With Log Shipping:
Data Transfer: T-Logs are backed up and transferred to secondary server
Transactional Consistency: All committed and un-committed are transferred
Server Limitation: Can be applied to multiple stand-by servers
Failover: Manual Failover Duration: Can take more than 30 mins
Role Change: Role change is manual
Client Re-direction: Manual changes required
With Database Mirroring:
Data Transfer: Individual T-Log records are transferred using TCP endpoints
Transactional Consistency: Only committed transactions are transferred
Server Limitation: Can be applied to only one mirror server
Failover: AutomaticFailover
Duration: Failover is fast, sometimes <>
Role Change: Role change is fully automatic
Client Re-direction: Fully automatic as it uses .NET 2.0
Wednesday, May 24, 2006
BCP Error on SQLState = S1000, NativeError = 0
When trying on the below BCP Command
bcp master..syslogins out D:\MSSQL\Backup\PrimaryLogship\syslogins.dat -N -S SQLServer -U sa -P password
getting the error message as
SQLState = S1000, NativeError = 0
Error = [MS][ODBC SQL Server Driver] Unable to open BCP host data-file
Resolution:
The problem occured because of "Incorrect Folder Name"
bcp master..syslogins out D:\MSSQL\Backup\PrimaryLogship\syslogins.dat -N -S SQLServer -U sa -P password
getting the error message as
SQLState = S1000, NativeError = 0
Error = [MS][ODBC SQL Server Driver] Unable to open BCP host data-file
Resolution:
The problem occured because of "Incorrect Folder Name"
Thursday, April 06, 2006
Where to see Windows Error Message nos?
Server: Msg 3202, Level 16, State 1, Line 1
1) Status = 64 Write on 'c:\temp.dat' failed, status = 64
2) Status = 112 Write on 'c:\temp.dat' failed, status = 112
It can be found at:
D:\Documents and Settings\pz5qrt>net HELPMSG 112
There is not enough space on the disk.
1) Status = 64 Write on 'c:\temp.dat' failed, status = 64
2) Status = 112 Write on 'c:\temp.dat' failed, status = 112
It can be found at:
D:\Documents and Settings\pz5qrt>net HELPMSG 112
There is not enough space on the disk.
A SQL Server cluster resource goes to a "failed" state when you try to bring the resource online in SQL Server 2000
When you try to bring a SQL Server cluster resource online for a virtual instance of Microsoft SQL Server 2000, you may notice the following behavior:
The SQL Server cluster resource goes to a "failed" state and does not come online.
You receive a combination of the following error messages on the computer that owns the SQL Server cluster resource.
Error message 1An event that is similar to the following is in the system event log:
Date: 08/05/2004 Time: 1:11:19 AM Source: ClusSvc Category: Failover Mgr Type: Error Event ID: 1069 User: N/A Computer: Description: Cluster resource 'SQL Server ()' in Resource Group '' failed. Error message 2An error message that is similar to the following is in the Cluster log file:
00000644.00000944::2003/11/30-18:11:30.360 SQL Server: [sqsrvres] Unable to read the 'VirtualServerName' property. Error: d.00000644.00000944::2003/11/30-18:11:30.360 SQL Server : [sqsrvres] OnlineThread: Error d bringing resource online.Error message 3Error messages that are similar to the following are in the SQL Server error log file:
2003-11-30 17:00:37.27 server Error: 17826, Severity: 18, State: 1 2003-11-30 17:00:37.27 server Could not set up Net-Library 'SSNETLIB'.. 2003-11-30 17:00:37.27 spid13 Starting up database 'SPB'. 2003-11-30 17:00:37.27 spid12 Starting up database 'BD_MTA'. 2003-11-30 17:00:37.27 spid14 Starting up database 'BD_SPF'. 2003-11-30 17:00:37.27 server Error: 17059, Severity: 18, State: 0 2003-11-30 17:00:37.27 server Operating system error -1073723998: .. 2003-11-30 17:00:37.27 server Unable to load any netlibs. 2003-11-30 17:00:37.27 server SQL Server could not spawn FRunCM thread.
CAUSE
The resource-specific registry keys that correspond to the SQL Server cluster resource that you are trying to bring online are missing. This problem also occurs if the values that correspond to the resource-specific registry keys are not correct.
RESOLUTION
Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.To resolve this problem, you must manually re-create the resource-specific registry keys that correspond to the SQL Server cluster resource. To do this, follow these steps:
1.
Click Start, click Run, type Regedit, and then click OK.
2.
In Registry Editor, locate and select the following registry key:HKEY_LOCAL_MACHINE\Cluster\Resources\\Parameters
3.
Create the following registry values in the Parameters registry key:For a default instance of SQL Server:
•
InstanceNameValue Name: InstanceNameValue Type: REG_SZ Value Data: MSSQLSERVER
•
VirtualServerNameValue Name: VirtualServerNameValue Type: REG_SZValue Data:For a named instance of SQL Server:
•
InstanceNameValue Name: InstanceNameValue Type: REG_SZ Value Data:
•
VirtualServerNameValue Name: VirtualServerNameValue Type: REG_SZValue Data:
4.
Quit Registry Editor.After you create the resource-specific registry keys, you can bring the SQL Server cluster resource online successfully.If you notice that a SQL Server Agent cluster resource cannot be brought online, you must create the same set of resource-specific keys that correspond to the SQL Server Agent cluster resource.
http://support.microsoft.com/?kbid=883732
The SQL Server cluster resource goes to a "failed" state and does not come online.
You receive a combination of the following error messages on the computer that owns the SQL Server cluster resource.
Error message 1An event that is similar to the following is in the system event log:
Date: 08/05/2004 Time: 1:11:19 AM Source: ClusSvc Category: Failover Mgr Type: Error Event ID: 1069 User: N/A Computer:
00000644.00000944::2003/11/30-18:11:30.360 SQL Server
2003-11-30 17:00:37.27 server Error: 17826, Severity: 18, State: 1 2003-11-30 17:00:37.27 server Could not set up Net-Library 'SSNETLIB'.. 2003-11-30 17:00:37.27 spid13 Starting up database 'SPB'. 2003-11-30 17:00:37.27 spid12 Starting up database 'BD_MTA'. 2003-11-30 17:00:37.27 spid14 Starting up database 'BD_SPF'. 2003-11-30 17:00:37.27 server Error: 17059, Severity: 18, State: 0 2003-11-30 17:00:37.27 server Operating system error -1073723998: .. 2003-11-30 17:00:37.27 server Unable to load any netlibs. 2003-11-30 17:00:37.27 server SQL Server could not spawn FRunCM thread.
CAUSE
The resource-specific registry keys that correspond to the SQL Server cluster resource that you are trying to bring online are missing. This problem also occurs if the values that correspond to the resource-specific registry keys are not correct.
RESOLUTION
Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.To resolve this problem, you must manually re-create the resource-specific registry keys that correspond to the SQL Server cluster resource. To do this, follow these steps:
1.
Click Start, click Run, type Regedit, and then click OK.
2.
In Registry Editor, locate and select the following registry key:HKEY_LOCAL_MACHINE\Cluster\Resources\
3.
Create the following registry values in the Parameters registry key:For a default instance of SQL Server:
•
InstanceNameValue Name: InstanceNameValue Type: REG_SZ Value Data: MSSQLSERVER
•
VirtualServerNameValue Name: VirtualServerNameValue Type: REG_SZValue Data:
•
InstanceNameValue Name: InstanceNameValue Type: REG_SZ Value Data:
•
VirtualServerNameValue Name: VirtualServerNameValue Type: REG_SZValue Data:
4.
Quit Registry Editor.After you create the resource-specific registry keys, you can bring the SQL Server cluster resource online successfully.If you notice that a SQL Server Agent cluster resource cannot be brought online, you must create the same set of resource-specific keys that correspond to the SQL Server Agent cluster resource.
http://support.microsoft.com/?kbid=883732
Wednesday, March 29, 2006
SQL Server Proxy Error Messages
If the SQL proxy account not set up the below error message would appearMsg 50001, Level 1, State 50001xpsql.cpp: Error 997 from GetProxyAccount on line 472
When SQL Server startup account does not have the 'Local Admin' privilegesMsg 50001, Level 1, State 50001xpsql.cpp: Error 997 from GetProxyAccount on line 472
When the SQL Server Startup account does not have the"Replace Process level Token" Privileges on Local security policy ,
Msg 50001, Level 1, State 50001xpsql.cpp: Error 1314 from CreateProcessAsUser on line 504
When the 'SQL Sever proxy account does not exist or deleted from the Windows.Msg 50001, Level 1, State 50001xpsql.cpp: Error 1326 from LogonUserW on line 488
When SQL Server startup account does not have the 'Local Admin' privilegesMsg 50001, Level 1, State 50001xpsql.cpp: Error 997 from GetProxyAccount on line 472
When the SQL Server Startup account does not have the"Replace Process level Token" Privileges on Local security policy ,
Msg 50001, Level 1, State 50001xpsql.cpp: Error 1314 from CreateProcessAsUser on line 504
When the 'SQL Sever proxy account does not exist or deleted from the Windows.Msg 50001, Level 1, State 50001xpsql.cpp: Error 1326 from LogonUserW on line 488
Wednesday, March 22, 2006
DMZ - DeMilitarized Zone
Computer slang used for a protected network that sits between the Internet and the corporate network.
Sometimes called a perimeter network.
A DMZ is a computer network that is accessible from two other computer networks that have no direct contact with each other. Often, one of these networks is the Internet and the other is a local, internal network. There is no direct connection between the Internet and the local network, but both of them can access an intermediate network, a demilitarized zone. DMZs are often used for special servers, such as web servers, which must be accessible from two separate networks.
Sometimes called a perimeter network.
A DMZ is a computer network that is accessible from two other computer networks that have no direct contact with each other. Often, one of these networks is the Internet and the other is a local, internal network. There is no direct connection between the Internet and the local network, but both of them can access an intermediate network, a demilitarized zone. DMZs are often used for special servers, such as web servers, which must be accessible from two separate networks.
Tuesday, March 21, 2006
SQL Server Proxy Account
George,
Who require proxy access ?
This will allow jobs scheduled by non-admin users (such as Bank staff) to properly execute DTS packages.
SQL Server Agent proxy accounts allow SQL Server users who do not belong to the sysadmin fixed server role to execute xp_cmdshell and own SQL Server Agent jobs. The administrators can assign appropriate security permissions to the proxy account to control the ability of these jobs to access resources in the network.
Why they needed?
1. SQL Proxy accounts are required to enable general users to schedule and execute SQL jobs for DTS packages (ETL).
2. In SQL Server 2000, a domain user cannot run the xp_cmdshell extended stored procedure even when the user has permissions
3. To create CmdExec and ActiveScript jobs belonging to someone other than a SQL Server administrator.
4. SQL Server Agent jobs also must execute in the security context of a Windows account. If the job is owned by a member of the sysadmin fixed server role, the job executes using the Windows account under which the SQL Server service is running. If the job owner is not in sysadmin, the job executes using the SQL Server Agent proxy account.
The following Microsoft knowledge base article explains what is required to execute a DTS package from an SQL Server job. This will allow jobs scheduled by non-admin users (such as Bank staff) to properly execute DTS packages.
http://support.microsoft.com/?kbid=269074
Who require proxy access ?
This will allow jobs scheduled by non-admin users (such as Bank staff) to properly execute DTS packages.
SQL Server Agent proxy accounts allow SQL Server users who do not belong to the sysadmin fixed server role to execute xp_cmdshell and own SQL Server Agent jobs. The administrators can assign appropriate security permissions to the proxy account to control the ability of these jobs to access resources in the network.
Why they needed?
1. SQL Proxy accounts are required to enable general users to schedule and execute SQL jobs for DTS packages (ETL).
2. In SQL Server 2000, a domain user cannot run the xp_cmdshell extended stored procedure even when the user has permissions
3. To create CmdExec and ActiveScript jobs belonging to someone other than a SQL Server administrator.
4. SQL Server Agent jobs also must execute in the security context of a Windows account. If the job is owned by a member of the sysadmin fixed server role, the job executes using the Windows account under which the SQL Server service is running. If the job owner is not in sysadmin, the job executes using the SQL Server Agent proxy account.
The following Microsoft knowledge base article explains what is required to execute a DTS package from an SQL Server job. This will allow jobs scheduled by non-admin users (such as Bank staff) to properly execute DTS packages.
http://support.microsoft.com/?kbid=269074
Monday, January 16, 2006
SQLServer Services not auto starting after reboot
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7000
Date: 12/01/2006
Time: 4:15:30 AM
User: N/A
Description:
The MSSQLSERVER service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7001
Date: 12/01/2006
Time: 4:15:30 AM
The SQLSERVERAGENT service depends on the MSSQLSERVER service which failed to start because of the following error: The service did not respond to the start or control request in a timely fashion.
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7009
Date: 12/01/2006
Time: 4:15:30 AM
Description:
Timeout (30000 milliseconds) waiting for the MSSQLSERVER service to connect.
What caused this error:Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 5719
Date: 12/01/2006
Time: 4:15:05 AM
Description:
This computer was not able to set up a secure session with a domain controller in domain AU due to the following:
There are currently no logon servers available to service the logon request.
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.
ADDITIONAL INFO
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
Event Source: Service Control Manager
Event Category: None
Event ID: 7000
Date: 12/01/2006
Time: 4:15:30 AM
User: N/A
Description:
The MSSQLSERVER service failed to start due to the following error:
The service did not respond to the start or control request in a timely fashion.
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7001
Date: 12/01/2006
Time: 4:15:30 AM
The SQLSERVERAGENT service depends on the MSSQLSERVER service which failed to start because of the following error: The service did not respond to the start or control request in a timely fashion.
Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7009
Date: 12/01/2006
Time: 4:15:30 AM
Description:
Timeout (30000 milliseconds) waiting for the MSSQLSERVER service to connect.
What caused this error:Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 5719
Date: 12/01/2006
Time: 4:15:05 AM
Description:
This computer was not able to set up a secure session with a domain controller in domain AU due to the following:
There are currently no logon servers available to service the logon request.
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.
ADDITIONAL INFO
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.
Sunday, December 04, 2005
SQL Server Locking detail from Sysperfinfo
--select getdate()
go
select getdate(),counter_name,instance_name,cntr_value from sysperfinfo
where object_name ='SQLServer:Locks'
and counter_name in ('Average Wait Time (ms)','Lock Wait Time (ms)','Lock Waits/sec' )
and instance_name = '_Total'
WAITFOR DELAY '0:01:00'
---select getdate()
select getdate(), counter_name,instance_name,cntr_value from sysperfinfo
where object_name ='SQLServer:Locks'
and counter_name in ('Average Wait Time (ms)','Lock Wait Time (ms)','Lock Waits/sec' )
and instance_name ='_Total'
go
select getdate(),counter_name,instance_name,cntr_value from sysperfinfo
where object_name ='SQLServer:Locks'
and counter_name in ('Average Wait Time (ms)','Lock Wait Time (ms)','Lock Waits/sec' )
and instance_name = '_Total'
WAITFOR DELAY '0:01:00'
---select getdate()
select getdate(), counter_name,instance_name,cntr_value from sysperfinfo
where object_name ='SQLServer:Locks'
and counter_name in ('Average Wait Time (ms)','Lock Wait Time (ms)','Lock Waits/sec' )
and instance_name ='_Total'
Tuesday, November 15, 2005
Transfer Logins
BUG: SQL 6.5 Logins upgraded to SQL 7.0 and subsequently moved to SQL 2000 through CDW cannot log in
http://support.microsoft.com/default.aspx?scid=kb;en-us;285025
Microsoft Knowledge Base Article - 331451
PRB: Copy Database Wizard Does Not Copy Server Roles When it Transfers Logins
-------------------------------------
Microsoft Knowledge Base Article - 240872
HOW TO: Resolve Permission Issues When You Move a Database Between Servers That Are Running SQL Server
.-------------------------------------
Microsoft Knowledge Base Article - 246133
INF: How To Transfer Logins and Passwords Between SQL ServersHas a script to transfer SIDs as well.
-------------------------------------
Yelena
http://support.microsoft.com/default.aspx?scid=kb;en-us;285025
Microsoft Knowledge Base Article - 331451
PRB: Copy Database Wizard Does Not Copy Server Roles When it Transfers Logins
-------------------------------------
Microsoft Knowledge Base Article - 240872
HOW TO: Resolve Permission Issues When You Move a Database Between Servers That Are Running SQL Server
.-------------------------------------
Microsoft Knowledge Base Article - 246133
INF: How To Transfer Logins and Passwords Between SQL ServersHas a script to transfer SIDs as well.
-------------------------------------
Yelena
Tuesday, November 08, 2005
Wednesday, September 28, 2005
Transaction Log space for DBCC DBREINDEX
1.The log space required by DBCC DBREINDEX is roughly equivalent to the number of index pages multiplied by 8 KB.
2. You can use DBCC SHOWCONTIG to determine the number of pages in a given index
3.When in full recovery mode, DBCC DBREINDEX logs images of each index page
Diff between DBReindex and DBCC Showcontig
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/ss2kidbp.mspx#EFAA
2. You can use DBCC SHOWCONTIG to determine the number of pages in a given index
3.When in full recovery mode, DBCC DBREINDEX logs images of each index page
Diff between DBReindex and DBCC Showcontig
http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/ss2kidbp.mspx#EFAA
Wednesday, September 14, 2005
Migrating OLAP Repository database from the Access to SQL Server
Note By default, the OLAP repository database is :\Program Files\Microsoft Analysis Services\Bin\Msmdrep.mdb
More on : http://support.microsoft.com/kb/829738/
You Receive an Error Message When You Try to Register or Connect to an Analysis Services Computer as a Domain User
Cannot connect to the repository.
Analysis server:
Error:
Could not use ''; file already in use.
More on : http://support.microsoft.com/kb/829738/
You Receive an Error Message When You Try to Register or Connect to an Analysis Services Computer as a Domain User
Cannot connect to the repository.
Analysis server:
Error:
Could not use ''; file already in use.
Thursday, September 08, 2005
SQL Serve Memory Monitoring Parameters
Memory: Available Bytes
Memory: Pages/sec
Process: Working Set ( SQLServer )
SQL Server: Buffer Manager: Buffer Cache Hit Ratio
SQL Server: Buffer Manager: Total Pages
SQL Server: Memory Manager: Total Server Memory (KB)
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_perfmon_8x0l.asp
Memory: Pages/sec
Process: Working Set ( SQLServer )
SQL Server: Buffer Manager: Buffer Cache Hit Ratio
SQL Server: Buffer Manager: Total Pages
SQL Server: Memory Manager: Total Server Memory (KB)
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/adminsql/ad_perfmon_8x0l.asp
Monday, September 05, 2005
Comparing SQL Server Databases
PowerDesigner, it’s a modeling tool from Sybase.
1.Just generate the SQL definition for the databases from inside the SQL Server and then import them to the PowerDesigner.
2. Once you have imported both databases in the PowerDesigner you can do many things.
3. You can compare the definitions and the PowerDesigner will generate a complete report with the differences between the two databases. The report will include tables, Keys, Indexes, views … etc
1.Just generate the SQL definition for the databases from inside the SQL Server and then import them to the PowerDesigner.
2. Once you have imported both databases in the PowerDesigner you can do many things.
3. You can compare the definitions and the PowerDesigner will generate a complete report with the differences between the two databases. The report will include tables, Keys, Indexes, views … etc
Wednesday, August 24, 2005
Saturday, August 13, 2005
Unable to connect to Citrix Server from some Workstations
Root Cause:
When Citrix client try to connect to Citrix Server, Server not able to issue client license. (Its not able to generate Client license key on Client computer HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing\Store Registry hive)
Workaround:
Open regedit.exe from client workstation Go to "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing\Store" Delete all the keys start with 'LIC' (It will remove existing Terminal Services client license key) Try to login to Citrix Server. Citrix Server will reissue new client license.
When Citrix client try to connect to Citrix Server, Server not able to issue client license. (Its not able to generate Client license key on Client computer HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing\Store Registry hive)
Workaround:
Open regedit.exe from client workstation Go to "HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSLicensing\Store" Delete all the keys start with 'LIC' (It will remove existing Terminal Services client license key) Try to login to Citrix Server. Citrix Server will reissue new client license.
Subscribe to:
Posts (Atom)