DCOM got error "Logon failure: unknown user name or bad password” Event 1004

DCOM got error "Logon failure: unknown user name or bad password” – why does it appear? How can I fix it?

If the persistent error message appears  in the Event Viewer Logs , follow the instructions below to fix.

 

DCOM got error "Logon failure: unknown user name or bad password." and was unable to logon MYDOMAIN\auser1 in order to run the server: {00020812-0000-0000-C000-000000000046}

 

To find the application name :

Start  >  Run > Find > Regedit > Enter the ID number   “00020812-0000-0000-C000-000000000046”

 In the example ID – it mapped to Microsoft Excel Applications

 To fix the problem:

1) On Windows Server : Go to Start > Programs > Administrative Tools > Component Services

2).Expand the Component Services > Computers > My Computer > COM+ Applications.

3) Select the application  (eg: Microsoft Excel Applications), right click on it and choose "Properties".

4) Click on the “Identity” Tab. On the Identity tab there is a "This user:" radio button which contains the username and password that my Component is using. Change the user login information there and restart the server.

 

 

Read More

SQL Server – How to troubleshoot query timeouts

How to request SQL Server troubleshooting

Troubleshooting Timeout error -2146232060

SQL Server – Troubleshoot connectivity issues with Connectivity Ring Buffer

Event ID 7026 and i8042prt troubleshooting

 

SQL Server - Error 701 - There is insufficient system memory

According to BOL the Error 701 is “SQL Server has failed to allocate sufficient memory to run the query. This can be caused by a variety of reasons including operating system settings, physical memory availability, or memory limits on the current workload. In most cases, the transaction that failed is not the cause of this error.”

 A very common error I see for Bpool memory pressure is the FAIL_PAGE_ALLOCATION 1. It’s for one page i.e. 8 KB.

To find the cause requires to search for a memoryclerk or cachestore which consumes the highest memory.

First step is to identify which memoryclerk or  cachestore is consuming the highest memory.When you inspect the Error Logs , there is normally the DBCC memorystatus output.

 An example of a cachestore with high memory usage at the time of the incident is :

 

CACHESTORE_SQLCP (Total) 
	VM Reserved = 0 KB 
	VM Committed = 0 KB 
	AWE Allocated = 0 KB 
	SM Reserved = 0 KB 
	SM Committed = 0 KB
	SinglePage Allocator = 1473672 KB
	MultiPage Allocator = 400 KB

 

The CACHESTORE_SQLCP stores cache plans for batches or T-SQL statements not in stored procedures, triggers or functions. In practise, these type of statements are used irregulary , although you’ll need to analyse. In this scenario , the CACHESTORE_SQLCP  was using 1.4 GB of physical memory.In the context of the server memory usage this was high.

This query is useful in presenting an overview of the plan cache size

SELECT TOP(5) * FROM 
sys.dm_Exec_cached_plans 
WHERE cacheobjtype = 'Compiled Plan' AND objtype = 'Adhoc' 
AND usecounts = 1 
AND size_in_bytes < 5242880 ORDER BY size_in_bytes DESC

 

There are many different scenarios for Error 701 - There is insufficient system memory, requiring different approaches.

Read More

SQL Server Performance ,memory pressure and memory usage ...

SQL Server – Measuring SQL memory usage - SQL Server DBA

SQL Server – Memory leak detection - SQL Server DBA

Event ID 7026 and i8042prt troubleshooting

Event ID 7026 and i8042prt is a recurring error in the Windows Event Logs. I usually see this error on a server reboot .

It’s normal for a server to not have a keyboard or mouse attached. I usually suppress the error , by creating a headless entry.

 The  errors occurs if you don’t plug in a PS/2 keyboard – which causes the drivers to not move to SYSTEM32\DRIVERS

 

Event Type:	Error
Event Source:	Service Control Manager
Event Category:	None
Event ID:	7026
Date:		20/12/2011
Time:		22:29:40
User:		N/A
Computer:	SERVER1
Description:
The following boot-start or system-start driver(s) failed to load: 
i8042prt

 

Solution 1

 

Plug in the PS\2 keyboard at least once and reboot

 

Solution 2

 

1. Go to Start > Run and put "regedit.exe" and click "Ok";

2. Navigate to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\i8042prt\Parameters in Registry Editor;

3. Add a new REG_DWORD "Headless" and set the value to 1;

4. Reboot the server.

Troubleshooting Event ID 9 - The device, xxxxx, did not respond within the timeout period.

The System logs returned :

 The device, xxxxxxxxxxxxxx, did not respond within the timeout period.

 Some common causes

1)      SCSI controller  firmware

2)      Incorrect transfer settings

3)      SCSI Cabling

4)      Other controllers creating bus contention

 

Record all the device model numbers and firmware revisions, and check with the manufacturer for any known issues.

Under Windows Server 2003, you can view model and firmware revisions for hardware under the following registry location:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Enum

See Also

 Powershell Get-EventLog and Event Log messages

SQL Server - Kerberos and KRB_AP_ERR_MODIFIED

On a routine scan of Event Viewer System, Logs I found this message on 4 different servers  hosting SQL Server installations

 

The kerberos client received a KRB_AP_ERR_MODIFIED error from the server MYCOMPUTER$.  This indicates that the password used to encrypt the kerberos service ticket is different than that on the target server. Commonly, this is due to identically named  machine accounts in the target realm (MY.DOMAIN.NET), and the client realm.   Please contact your system administrator.

 

Why was this occurring?

 

1)      A client was using a DNS CNAME to point traffic to serverB after decommissioning serverA . Removing the CNAME would have resolved the issue

2)      An entry in the /etc/hosts file . After renaming a server and setting up a new one with the same name the host-entry was not updated and so the new server pointed to the IP address of the old one

 

 

See Also

Event ID 40960 Cannot generate SSPI context

Server sudden shutdown unavailable