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.
Monday, January 16, 2006
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.
Monday, August 08, 2005
System Error No List
System Error Codes (0-499)
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/debug/base/system_error_codes__0-499_.asp
Example:
ERROR_DISK_FULL112
There is not enough space on the disk.
Microsoft Product Support's Reporting Tools
The Microsoft Product Support Reporting Tool facilitates the gathering of critical system and logging information used in troubleshooting support issues. The reporting tool DOES NOT make any registry changes or modifications to the operating system. There are 8 specialty versions, one for each of the following support scenario categories: Alliance, Directory Services (not for Windows NT 4.0), Networking, Clustering, SQL, Software Update Services, MDAC and Base/Setup/Storage/Print/Performance. Each version gathers some of the same basic information but there are specific reports unique to each of the support scenario categories
Link :
http://www.microsoft.com/downloads/details.aspx?FamilyId=CEBF3C7C-7CA5-408F-88B7-F9C79B7306C0&displaylang=en
Tuesday, August 02, 2005
SQL Server Agent not starting
SQL Server Agent on SQL Server 2000 not started.
There are One SQL Server Service account and one connection setting for the serivce account this need to be checked for any password change and accont change if not windows authentication
It almost relevant of "http://support.microsoft.com/default.aspx?scid=kb;en-us;237604".
From Event Viewer
Event Type: Error
Event Source: SQLSERVERAGENT
Event Category: Service Control
Event ID: 103
Date: 30/07/2005
Time: 4:01:50 PM
User: N/A
Computer: AAUNSW047
Description:
SQLServerAgent could not be started (reason: Unable to connect to server '(local)'; SQLServerAgent cannot start).
Output on SQL Agent when tries "SQLAgent -c -v " from the command prompt
2005-07-30 16:01:50 - ? [094] SQLServerAgent started from command line
2005-07-30 16:01:50 - ! [298] SQLServer Error: 18456, Login failed for user 'sa'. [SQLSTATE 28000]
2005-07-30 16:01:50 - ! [000] Unable to connect to server '(local)'; SQLServerAgent cannot start
2005-07-30 16:01:50 - ? [098] SQLServerAgent terminated (normally)
There are One SQL Server Service account and one connection setting for the serivce account this need to be checked for any password change and accont change if not windows authentication
It almost relevant of "http://support.microsoft.com/default.aspx?scid=kb;en-us;237604".
From Event Viewer
Event Type: Error
Event Source: SQLSERVERAGENT
Event Category: Service Control
Event ID: 103
Date: 30/07/2005
Time: 4:01:50 PM
User: N/A
Computer: AAUNSW047
Description:
SQLServerAgent could not be started (reason: Unable to connect to server '(local)'; SQLServerAgent cannot start).
Output on SQL Agent when tries "SQLAgent -c -v " from the command prompt
2005-07-30 16:01:50 - ? [094] SQLServerAgent started from command line
2005-07-30 16:01:50 - ! [298] SQLServer Error: 18456, Login failed for user 'sa'. [SQLSTATE 28000]
2005-07-30 16:01:50 - ! [000] Unable to connect to server '(local)'; SQLServerAgent cannot start
2005-07-30 16:01:50 - ? [098] SQLServerAgent terminated (normally)
SQL Server 2000 Analysis Services - INF: Permissions That You Must Have to Administer an OLAP Server
2147221466 : Your permissions on the server computer do not allow you to administer this OLAP server.Error: Path/File access error
SQL Server 2000 Analysis Services - INF: Permissions That You Must Have to Administer an OLAP Server
SQL Server 2000 Analysis Services - INF: Permissions That You Must Have to Administer an OLAP Server
Thursday, July 14, 2005
Dynamic Memory Setting on SQL Server
This is given in SQL Server 2000 BOL.
When an instance of SQL Server starts, it typically acquires 8 to 12 MB of memory to complete the initialization process. After the instance has finished initializing, it acquires no more memory until users connect to it and start generating a workload. The instance then keeps acquiring memory as required to support the workload. As more users connect and run queries, SQL Server acquires the additional memory required to support the demand. The instance will keep acquiring memory until it reaches its memory allocation target, it will not free any memory until it reaches the lower limit of the target.
To acquire as much memory as possible without generating excess paging I/O, each instance of SQL Server sets a target of acquiring memory until free physical memory on the computer is in the range of 4 MB to 10 MB. This range was chosen because testing has shown that Windows NT and Windows 2000 have minimal memory swapping until the memory allocations equal the available physical memory minus 4 MB. An instance of SQL Server that is processing a heavy workload keeps the free physical memory at the lower end (4 MB) of the range; an instance that is processing a light workload keeps the free memory at the higher end of the range (10 MB). An instance of SQL Server will vary its target as the workload changes. As more users connect and generate more work, the instance will tend to acquire more memory to keep the available free memory down at the 4 MB limit.
As the workload lightens, the instance will adjust its target towards 10 MB of free space, and will free memory to the operating system. Keeping the amount of free space between 10 MB and 4 MB keeps Windows NT or Windows 2000 from paging excessively, while at the same time allowing SQL Server to have the largest buffer cache possible that will not cause extra swapping."
When an instance of SQL Server starts, it typically acquires 8 to 12 MB of memory to complete the initialization process. After the instance has finished initializing, it acquires no more memory until users connect to it and start generating a workload. The instance then keeps acquiring memory as required to support the workload. As more users connect and run queries, SQL Server acquires the additional memory required to support the demand. The instance will keep acquiring memory until it reaches its memory allocation target, it will not free any memory until it reaches the lower limit of the target.
To acquire as much memory as possible without generating excess paging I/O, each instance of SQL Server sets a target of acquiring memory until free physical memory on the computer is in the range of 4 MB to 10 MB. This range was chosen because testing has shown that Windows NT and Windows 2000 have minimal memory swapping until the memory allocations equal the available physical memory minus 4 MB. An instance of SQL Server that is processing a heavy workload keeps the free physical memory at the lower end (4 MB) of the range; an instance that is processing a light workload keeps the free memory at the higher end of the range (10 MB). An instance of SQL Server will vary its target as the workload changes. As more users connect and generate more work, the instance will tend to acquire more memory to keep the available free memory down at the 4 MB limit.
As the workload lightens, the instance will adjust its target towards 10 MB of free space, and will free memory to the operating system. Keeping the amount of free space between 10 MB and 4 MB keeps Windows NT or Windows 2000 from paging excessively, while at the same time allowing SQL Server to have the largest buffer cache possible that will not cause extra swapping."
SQL Server 2000 Standard Backup failure
Backup job created using SQL Server Maintanence plan fail with the below error intermittently
"Executes as user: Domain\sqladmin sqlmaint.exe failed. [SQLSTATE 42000] [Error 22029]. The step failed"
Below are the error message found on SQL server Errror log.
BACKUP failed to complete the command BACKUP DATABASE [USER_DB_01] TO DISK = N'E:\MSSQL\BACKUP\USER_DB_01\USER_DB_01_db_200507092100.BAK' WITH INIT , NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT
BackupMedium::ReportIoError: write failure on backup device 'E:\MSSQL\BACKUP\USER_DB_01\USER_DB_01_db_200507092100.BAK'. Operating system error 112(error not found).
Internal I/O request 0x53A97468: Op: Write, pBuffer: 0x154A0000, Size: 983040, Position: 3927840256, UMS: Internal: 0x103, InternalHigh: 0x0, Offset: 0xEA1E1600, OffsetHigh: 0x0, m_buf: 0x154A0000, m_len: 983040, m_actualBytes: 0, m_errcode: 112, BackupFile: E:\MSSQL\BACKUP\USER_DB_01\USER_DB_01_db_200507092100.BAK
"Executes as user: Domain\sqladmin sqlmaint.exe failed. [SQLSTATE 42000] [Error 22029]. The step failed"
Below are the error message found on SQL server Errror log.
BACKUP failed to complete the command BACKUP DATABASE [USER_DB_01] TO DISK = N'E:\MSSQL\BACKUP\USER_DB_01\USER_DB_01_db_200507092100.BAK' WITH INIT , NOUNLOAD , NOSKIP , STATS = 10, NOFORMAT
BackupMedium::ReportIoError: write failure on backup device 'E:\MSSQL\BACKUP\USER_DB_01\USER_DB_01_db_200507092100.BAK'. Operating system error 112(error not found).
Internal I/O request 0x53A97468: Op: Write, pBuffer: 0x154A0000, Size: 983040, Position: 3927840256, UMS: Internal: 0x103, InternalHigh: 0x0, Offset: 0xEA1E1600, OffsetHigh: 0x0, m_buf: 0x154A0000, m_len: 983040, m_actualBytes: 0, m_errcode: 112, BackupFile: E:\MSSQL\BACKUP\USER_DB_01\USER_DB_01_db_200507092100.BAK
DTS Package Creation
Question on , who can create DTS and save the DTS packages?
What are the privileges and rights that required for user to create a DTS package?
Answer is on the below link.
http://support.microsoft.com/?id=282463
What are the privileges and rights that required for user to create a DTS package?
Answer is on the below link.
http://support.microsoft.com/?id=282463
Subscribe to:
Posts (Atom)