Category: Servers
-
Cannot start SQL Server 2005 – Event ID 17190
Environment VMware ESXi 4.0 hostMicrosoft Windows Server 2003 Service Pack 2Microsoft SQL Server 2005 Service Pack 4SQL service account: sql-admin (domain account) Issue Microsoft SQL 2005 server service not running. Starting service manually fails with error message: Windows could not start the SQL Server (MSSQLSERVER) on Local Computer. For more information, review theSystem Event Log.…
-
DHCP service keeps crashing with Event ID 1000
Issue Windows Small Business Server 2008 stopped issuing IP addresses. DHCP service not running. After staring DHCP service manually, it crashes after couple of seconds. Following error is logged in Windows Application Logs: Source: Application ErrorEvent ID: 1000Level: ErrorDescription:Faulting application svchost.exe_DHCPServer, version 6.0.6001.18000, time stamp 0x47919281, faulting module dhcpssvc.dll, version 6.0.6002.18005, time stamp 0x49e090fc, exception…
-
Microsoft IIS 6 – create custom 404 Error Page
Create a new HTML file with your custom 404 Error message. Open IIS Management Console Expand Web Sites, Right Click on your site > Properties Click on Custom Errors tab, select 404 and click Edit Message type select File Click Browse and select your new html file Save changes
-
Find out Exchange 2007 / 2010 Version, Service Pack and Update Rollup
Microsoft Exchange Server Version number is often displayed in a numeric format, e.g Version 8.1 (Build 278.2). It may not look very meaningful at first but it’s easy enough to decode these numbers. Find Exchange version You can find out your Exchange 2007 and 2010 version either using following methods:
-
Microsoft Active Directory – Exchange Extension has encountered a problem and needs to close
Background Windows Server 2003 / 2008 domainWindows Server Active Directory Forest Schema upgraded to Server 2008Member or DC Windows 2003 Servers with Exchange 2003 Management Tools installed Problem Active Directory Users and Computers MMC crashes on Windows Server 2003 machines with Exchange 2003 Management Tools installed. Crash normally occurs after opening a second AD object…
-
Users can’t logon on Terminal Server using mandatory profiles “The filename or extension is too long”
Background Windows Server 2003 / 2008 domain Windows Terminal Server 2003 Terminal Server set to use a mandatory profiles Problem Occasionally users are not able to logon using on the Terminal Server using their Remote Desktop Clients.Thy get error message similar to this: Windows cannot copy file C:\Documents and Settings\tms-profile\Local Settings\Temporary Internet Files\Content.IE5\C6RWUIVV\filenameto location:C:\Documents and…
-
Enable LDAP over SSL (LDAPS) on Windows Sever 2003 Domain Controller
By default LDAP communications are insecure (unencrypted). To enable secure LDAP connections you simply need to install a properly formatted server authentication certificate on the LDAP server. This can be a trusted third party certificate or an internal Active Direcotry certificate issues by your own Certificate Authority (CA). There is no additional configuration required. As…
-
Add first Windows Server 2008 R2 Domain Controller to Server 2003 domain.
Before introducing first Windows Server 2008 R2 domain controller to your Server 2003 domain you must prepare your forest and domain. This is done running ADPREP tool from Windows Server 2008 R2 DVD.Note that you do not need to run adprep if you are merely joining Windows Server 2008 R2 server to the domain as…
-
Windows 2003 Terminal Server – Prevent roaming profile changes from propagating to the server for certain users
Scenario: There a two types of terminal server users and they need to have profiles setup in 2 different ways: First group – use single shared profile located on the network \\Server\ShareName\TMS-Profile. Any changes user makes to the profile are not propagated to the network copy of the profile – every time users log on…
-
Windows cannot log you on because your profile cannot be loaded – Indexing Service (cidaemon.exe) locks files in roaming profiles.
Users started complaining about occasionally having problems logging-on on Windows 2003 Terminal Server via Remote Desktop client. A quick check in Event Viewer Application logs revealed following errors: Source: UserenvEven ID: 1509Type: ErrorDescription:Windows cannot copy file \\server2\tms\profile_path\user\Favorites\File.url. Possible causes of this error include network problems or insufficient security rights. If this problem persists, contact your…
-
VMware vSphere Client error – Error parsing the se…
If you are trying to run older version of VMware vSphere Client on Windows 7, or fully updated Windows XP you may get following errors: VMware vSphere Client error – Error parsing the server “[server]” “clients.xml” file The type initializer for VirtualInfrastructure.Utils.HttpWebRequestProxy’ threw an exception. These errors are caused by an updated Microsoft .NET version.…
-
Logon Failure: The target account name is incorrect
Background Windows Server 2003 domainWindows XP SP3 clients Problem Domain administrator is trying to access remote computer’s file system via UNC administrative share e.g \\computer01\c$Operation fails with error:\\computer01\c$ not accessible you might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions.Logon failure:…