Tag: Event 1004

Event ID 1004 — PLA Data Collection Status

PCIS Support Team Leave a comment

Event ID 1004 — PLA Data Collection Status

Updated: August 5, 2011

Applies To: Windows Server 2008 R2

Performance Logs and Alerts (PLA) provides advanced scheduling and logging of performance data. It is used by Windows Reliaibility and Performance Monitor and by non-Microsoft applications. Performance Logs and Alerts depends on successful collection of performance counter data to carry out its logging and notification functions.

Event Details

Product: Windows Operating System
ID: 1004
Source: Microsoft-Windows-Diagnosis-PLA
Version: 6.1
Symbolic Name: PLA_EVENTLOG_DCS_START_FAILED
Message: Data collector set %1 failed to start as %3 with error code %4.

Resolve
Check the reason the Data Collector Set failed to start

If a Data Collector Set failed to start, the error message will include specific details about the reason for the failure.

If a four-digit or five-digit Windows Error Code is included, you can find the explanation of the error code on the Web at http://go.microsoft.com/fwlink/?LinkID=83027.

Verify

You can use Windows Reliability and Performance Monitor to verify that netowkr performance counters are properly collected and displayed in a Performance Monitor graph. In addition, you can use the typeperf command to get a list of the available counters on the local system.

Membership in the local Administrators group is required to complete these procedures.

View counters in Performance Monitor

To view counters in Performance Monitor:

  1. On the computer where you want to view counters, click Start. In the Start Search text box, type perfmon.exe, and then press ENTER.
  2. In the navigation pane, expand Monitoring Tools, and then click Performance Monitor.
  3. Click the Add button to open a list of available performance counters.
  4. In the Add Counters dialog box, you can click Help for more information on adding counters. When you have finished adding counters to the list, click OK.
  5. Verify that the performance counters you selected are displayed in the Performance Monitor graph.

View a list of counters using the typeperf command

To view a list of counters at the command prompt:

  1. Click Start, click All Programs, and click Accessories. Right-click Command Prompt, and click Run as administrator.
  2. At the command prompt, type typeperf -qx and press ENTER.
  3. Verify that the performance counter list contains expected values.

Related Management Information

PLA Data Collection Status

Management Infrastructure

Related:

Event ID 1004 — Windows Installer Application Installation

PCIS Support Team Leave a comment

Event ID 1004 — Windows Installer Application Installation

Updated: December 16, 2008

Applies To: Windows Server 2008 R2

Windows Installer is used to install applications on a computer.

Event Details

Product: Windows Installer – Unicode
ID: 1004
Source: MsiInstaller
Version: 5.0
Symbolic Name: EVENTLOG_TEMPLATE_COMPONENT_DETECTION
Message: Detection of product ‘%1’, feature ‘%2’, component ‘%3’ failed. The resource ‘%4’ does not exist.

Resolve
Review the system log file

Windows Installer encountered an error while installing, updating, or removing an application. For more information about the error, you will need to open Event Viewer and examine the System log file.

To review the system log file for Windows Installer events:

  1. Click Start, point to Administrative Tools, and then click Event Viewer.
  2. In the navigation pane, find the System event log.
  3. In the Actions pane, click Filter current log…
  4. In the Filter Current Log dialog box, select the Filter tab and then select MsiInstaller from the Event Sources drop-down.
  5. Review the most recent Windows Installer events to determine the cause of the issue. In addition to the Windows Installer events, you should also review the other system events to determine if a related issue may be the cause of the Windows Installer error.
  6. If you cannot resolve the issue based on the information in the event log, try reinstalling the application.

Note: If Windows Installer logging is not enabled, no information will be available in Event Viewer. For more information about Windows Installer logging, see http://go.microsoft.com/fwlink/?LinkId=136341.

Verify

You can use Programs and Features to verify an application is installed, uninstall applications, and change the application’s configuration by adding or removing options. If the application is not listed, it may not be configured properly or written for a different version of Windows. Reinstalling the application may resolve a configuration problem. To reinstall the application, consult the information that came with the application.

To verify the application is installed:

  1. Click Start, and then click Control Panel.
  2. Double-click Programs and Features.
  3. Verify the application appears in the list of installed programs.

Note: Only applications that are written for Windows will appear in Programs and Features. If you don’t see the application listed and you want to uninstall the application, check the information that came with your software, or go to the manufacturer’s Web site. Most programs install themselves in the C:\Program Files folder. Check this folder because some programs also include an uninstall program that you can use to remove the software.

Related Management Information

Windows Installer Application Installation

Windows Installer Service

Related:

Event ID 1004 — Terminal Services Client Access License (TS CAL) Availability

PCIS Support Team Leave a comment

Event ID 1004 — Terminal Services Client Access License (TS CAL) Availability

Updated: January 5, 2012

Applies To: Windows Server 2008

A terminal server must be able to contact (discover) a Terminal Services license server in order to request Terminal Services client access licenses (TS CALs) for users or computing devices that are connecting to the terminal server. In addition, the Terminal Services licensing mode configured on a terminal server must match the type of TS CALs available on the license server.

Note:  A terminal server running Windows Server 2008 can only communicate with a license server running Windows Server 2008.

Event Details

Product: Windows Operating System
ID: 1004
Source: Microsoft-Windows-TerminalServices-RemoteConnectionManager
Version: 6.0
Symbolic Name: EVENT_CANNOT_ISSUE_LICENSE
Message: The terminal server cannot issue a client license. It was unable to issue the license due to a changed (mismatched) client license, insufficient memory, or an internal error. Further details for this problem may have been reported at the client’s computer.

Diagnose

This error might be caused by one of the following conditions:

  • The licensing mode for the terminal server does not match the type of TS CALs installed on the license server.
  • The RDP encryption levels on the terminal server and the client are not compatible.
  • The certificate on the terminal server is corrupted.

The licensing mode for the terminal server does not match the type of TS CALs installed on the license server

To perform this procedure, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.

To determine the licensing mode for the terminal server:

  1. On the terminal server, open Terminal Services Configuration. To open Terminal Services Configuration, click Start, point to Administrative Tools, point to Terminal Services, and then click Terminal Services Configuration.
  2. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
  3. In the left pane, click Licensing Diagnosis.
  4. Review the following information in Licensing Diagnosis:
    • Under Terminal Server Configuration Details, note the licensing mode for the terminal server.
    • Under Terminal Services License Server Information, note the type of TS CALs installed on any license server that is listed as discovered. Information about the type of TS CALs installed on a license server is listed under License Server Configuration Details, which is displayed when you click a license server listed as discovered under Terminal Services License Server Information.
  5. If the licensing mode for the terminal server does not match the type of TS CALs installed on the license server, see the section titled “Specify the licensing mode for the terminal server.”

The RDP encryption levels on the terminal server and the client are not compatible

To perform this procedure, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.

To determine the RDP encryption level compatibility:

  1. On the terminal server, open Terminal Services Configuration. To open Terminal Services Configuration, click Start, point to Administrative Tools, point to Terminal Services, and then click Terminal Services Configuration.
  2. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
  3. Under Connections, right-click the connection (for example, RDP-Tcp), and then click Properties.
  4. On the General tab, note the value of Encyption level. For more information about encryption levels, see “Configure Server Authentication and Encryption Levels” in the Terminal Services Configuration Help in the Windows Server 2008 Technical Library (http://go.microsoft.com/fwlink/?LinkId=101637).
  5. On the client computer, start Remote Desktop Connection. To start Remote Desktop Connection, click Start, click Run, type mstsc.exe, and then press ENTER.
  6. Click the icon in the upper-left corner of the Remote Desktop Connection dialog box, and then click About. Look for the phrase “Maximum encryption strength” in the About Remote Desktop Connection dialog box. This value is the maximum encryption strength supported by the version of Remote Desktop Connection running on the computer.
  7. If the maximum encryption strength supported by the version of Remote Desktop Connection running on the client computer is not supported by the encryption level configured on the terminal server, see the section titled “Change the RDP encryption level on the terminal server.”

The certificate on the terminal server is corrupted

If the licensing mode for the terminal server matches the type of TS CALs installed on the license server and the RDP settings on the terminal server and the client are compatible, the certificate on the terminal server might be corrupted. To resolve this issue, see the section titled “Delete the appropriate registry subkey.”

Resolve

To resolve this issue, use the resolution that corresponds to the cause you identified in the Diagnose section. After performing the resolution, see the Verify section to confirm that the feature is operating properly

Cause

Resolution

The licensing mode for the terminal server does not match the type of TS CALs installed on the license server

Specify the licensing mode for the terminal server

The RDP encryption levels on the terminal server and the client are not compatible

Change the RDP encryption level on the terminal server

The certificate on the terminal server is corrupted

Delete the appropriate registry subkey

Specify the licensing mode for the terminal server

To resolve this issue, specify the Terminal Services licensing mode on the terminal server.

The Terminal Services licensing mode determines the type of Terminal Services client access licenses (TS CALs) that a terminal server will request from a license server on behalf of a client connecting to the terminal server. Although there is a licensing grace period during which no license server is required, after the grace period ends, clients must receive a valid TS CAL issued by a license server before they can log on to a terminal server.

Important:  The Terminal Services licensing mode configured on a terminal server must match the type of TS CALs available on the license server.

To perform this procedure, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.

To specify the Terminal Services licensing mode:

  1. On the terminal server, open Terminal Services Configuration. To open Terminal Services Confiiguration, click Start, point to Administrative Tools, point to Terminal Services, and then click Terminal Services Configuration.
  2. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
  3. Under Licensing, double-click Terminal Services licensing mode.
  4. Select either Per Device or Per User, depending on your environment. For more information about the two options, see “Specify the Terminal Services Licensing Mode” in the Terminal Services Configuration Help in the Windows Server 2008 Technical Library (http://go.microsoft.com/fwlink/?LinkId=101638).
  5. Click OK, and then click OK.

Note:  You can also specify the Terminal Services licensing mode for a terminal server by using Group Policy.

  • To specify the Terminal Services licensing mode for a terminal server by using Group Policy, enable the Set Terminal Services licensing mode Group Policy setting. This Group Policy setting is located in Computer Configuration\Administrative Templates\Windows Components\Terminal Services\Terminal Server\Licensing. Note that the Group Policy setting will take precedence over the setting configured in Terminal Services Configuration.
  • To configure the Group Policy setting in Active Directory Domain Services (AD DS), use the Group Policy Management Console (GPMC). To configure the Group Policy setting locally on a terminal server, use the Local Group Policy Editor. For more information about configuring Group Policy settings, see either the Local Group Policy Editor Help (http://go.microsoft.com/fwlink/?LinkId=101633) or the GPMC Help (http://go.microsoft.com/fwlink/?LinkId=101634) in the Windows Server 2008 Technical Library.

Change the RDP encryption level on the terminal server

To resolve this issue, change the RDP encryption level on the terminal server to a level that is supported by the version of Remote Desktop Connection that is running on the client computer.

By default, Terminal Services connections are encrypted at the highest level of security available (128-bit). However, some older versions of the Terminal Services client do not support this high level of encryption. If your network contains such legacy clients, you can set the encryption level of the connection to send and receive data at the highest encryption level supported by the client.

To perform this procedure, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.

To change the RDP encryption level:

  1. On the terminal server, open Terminal Services Configuration. To open Terminal Services Configuration, click Start, point to Administrative Tools, point to Terminal Services, and then click Terminal Services Configuration.
  2. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
  3. Under Connections, right-click the connection (for example, RDP-Tcp), and then click Properties.
  4. On the General tab, change the value of Encyption level to a level that is appropriate for the version of Remote Desktop Connection that is running on the client computer. For more information about encryption levels, see “Configure Server Authentication and Encryption Levels” in the Terminal Services Configuration Help in the Windows Server 2008 Technical Library (http://go.microsoft.com/fwlink/?LinkId=101637).

When you change the encryption level, the new encryption level takes effect the next time a user logs on. If you require multiple levels of encryption on one terminal server, install multiple network adapters and configure each adapter separately.

Note:  You can also change the RDP encryption level on the terminal server by using Group Policy.

  • To set the RDP encryption level for the terminal server by using Group Policy, enable the Set client connection encryption level Group Policy setting. This Group Policy setting is located in Computer Configuration\Administrative Templates\Windows Components\Terminal Services\Terminal Server\Security. Note that the Group Policy setting will take precedence over the setting configured in Terminal Services Configuration.
  • To configure the terminal server to use FIPS as the encryption level by using Group Policy, enable the System cryptography: Use FIPS compliant algorithms for encryption, hashing and signing Group Policy setting. This Group Policy setting is located in Computer Configuration\Windows Settings\Security Settings\Local Policies\Security Options. Note that this Group Policy setting will take precedence over the setting configured in Terminal Services Configuration and takes precedence over the Set client connection encryption level policy setting.
  • To configure the Group Policy setting in Active Directory Domain Services (AD DS), use the Group Policy Management Console (GPMC). To configure the Group Policy setting locally on a terminal server, use the Local Group Policy Editor. For more information about configuring Group Policy settings, see either the Local Group Policy Editor Help (http://go.microsoft.com/fwlink/?LinkId=101633) or the GPMC Help (http://go.microsoft.com/fwlink/?LinkId=101634) in the Windows Server 2008 Technical Library.

Delete the appropriate registry subkey

To resolve this issue, delete the MSLicensing registry subkey on the client computer, restart the client computer, and then try again to connect remotely to the terminal server from the client computer. If the issue persists, delete the Certificate, X509 Certificate, X509 Certificate2, and X509 Certificate ID registry entries on the terminal server, restart the terminal server, and then try again to connect to the terminal server from the client computer.

Delete the MSLicensing registry subkey

To perform this procedure on the client computer, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.

To delete the MSLicensing registry subkey:

Caution:  Incorrectly editing the registry might severely damage your system. Before making changes to the registry, you should back up any valued data.

  1. On the client computer, open Registry Editor. To open Registry Editor, click Start, click Run, type regedit, and then click OK.
  2. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
  3. Locate the HKEY_LOCAL_MACHINE\Software\Microsoft\MSLicensing registry subkey.
  4. Click MSLicensing.
  5. Before deleting the MSLicensing subkey, back up the subkey. To back up the subkey, do the following:
    1. On the Registry menu, click Export Registry File.
    2. In the File name box, type mslicensingbackup, and then click Save. If you need to restore this registry subkey, double-click mslicensingbackup.reg.
  6. To delete the MSLicensing subkey, on the Edit menu, click Delete, and then click Yes.
  7. Close Registry Editor, and then restart the client.
  8. After the client computer is restarted, try again to connect remotely to the terminal server from the client computer.

Delete the appropriate registry entries on the terminal server

If the issue persists, delete the Certificate, X509 Certificate, X509 Certificate2, and X509 Certificate ID registry entries on the terminal server.

To perform this procedure on the terminal server, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.

To delete the appropriate registry entries:

Caution:   Incorrectly editing the registry can severely damage your system. Before making changes to the registry, you should back up any valued data on the computer.

  1. On the terminal server, open Registry Editor. To open Registry Editor, click Start, click Run, type regedit, and then click OK.
  2. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
  3. Locate the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Terminal Server\RCM registry subkey.
  4. Click RCM.
  5. Before deleting the subkeys, back up the RCM subkey. To back up the subkey, do the following:
    1. On the Registry menu, click Export Registry File.
    2. In the File name box, type tsrcm, and then click Save. If you need to restore this registry subkey, double-click tsrcm.reg.
  6. To delete the Certificate, X509 Certificate, X509 Certificate2, and X509 Certificate ID registry entries, right-click each entry, click Delete, and then click Yes.
  7. Close Registry Editor, and then restart the terminal server.
  8. After the terminal server is restarted, try again to connect remotely to the terminal server from the client computer.

If the issue persists, do the following:

  1. On the client computer, back up and then delete the MSLicensing registry key and its subkeys.
  2. On the terminal server, back up and then delete the Certificate, X509 Certificate, X509 Certificate2, and X509 Certificate ID registry entries.
  3. Deactivate and then reactivate the license server.  For information about deactivating and reactivating a license server, see the topic “Managing TS Licensing” in the TS Licensing Manager Help in the Windows Server 2008 Technical Library (http://go.microsoft.com/fwlink/?LinkId=101645).
  4. Restart the terminal server and the client computer and then try again to connect remotely to the terminal server from the client computer.

Verify

To verify that the terminal server can discover (contact) a Terminal Services license server with the appropriate type of Terminal Services client access licenses (TS CALs), use Licensing Diagnosis in Terminal Services Configuration.

To perform this procedure, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.

To use Licensing Diagnosis in Terminal Services Configuration:

  1. On the terminal server, open Terminal Services Configuration. To open Terminal Services Configuration, click Start, point to Administrative Tools, point to Terminal Services, and then click Terminal Services Configuration.
  2. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
  3. In the left pane, click Licensing Diagnosis.
  4. Under Terminal Server Configuration Details, the value for Number of TS CALs available for clients should be greater than 0.

Related Management Information

Terminal Services Client Access License (TS CAL) Availability

Terminal Services

Related:

Event ID 1004 — IIS Web Site Availability

PCIS Support Team Leave a comment

Event ID 1004 — IIS Web Site Availability

Updated: January 20, 2010

Applies To: Windows Server 2008

Internet Information Services (IIS) Web sites that use HTTP rely on several important IIS components for their availability. The Windows Process Activation Service (WAS), the World Wide Publishing Service (W3SVC), the HTTP service, all must be running correctly. In addition, a properly running application pool must be available for the Web site’s applications. If any of these components is not functioning, the Web site will not be available.

Event Details

Product: Internet Information Services
ID: 1004
Source: Microsoft-Windows-IIS-W3SVC
Version: 7.0
Symbolic Name: W3SVC_EVENT_BINDING_FAILURE_GENERIC
Message: The World Wide Web Publishing Service (WWW Service) did not register the URL prefix %1 for site %2. The site has been disabled. The data field contains the error number.

Resolve
Add or edit site bindings

Ensure that the site has bindings with a valid port and IP address configured, and that the IP address and port configured for this Web site are not already being used by another site or entity. Only one Web site can be bound to a particular IP/port pairing at one time. After you add or edit bindings, you may have to restart the Web site, and, in some cases, the HTTP service.

To perform these procedures, you must have membership in Administrators, or you must have been delegated the appropriate authority.

Add or edit site bindings

To add or edit site bindings, follow these steps:

  1. Click Start, click Control Panel, and then click Administrative Tools.
  2. Right-click Internet Information Services (IIS) Manager and select Run as administrator.
  3. In the Connections Pane, select the Web site that you have to configure.
  4. In the Actions pane, click Bindings…
  5. To modify an existing binding, select the binding and click Edit.
  6. To add a new binding, click Add…
  7. After you have set the unique bindings for the site, click OK, then click Close.

Restart the site

If necessary, restart the site by following these steps:

  1. Click Start, click Control Panel, and then click Administrative Tools.
  2. Right-click Internet Information Services (IIS) Manager and select Run as administrator.
  3. In the Connections Pane, select the Web site that you have to configure.
  4. In the Actions pane, click Stop to stop the site.
  5. In the Actions pane, click Start to restart the site.

Stop and restart the HTTP service

In some cases, you may also have to stop and restart the HTTP service:

  1. Open an elevated Command Prompt window. Click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
  2. Type net stop HTTP /y.
  3. Type net start w3svc. This will also start the HTTP service.
  4. Start any other services that were stopped when the HTTP service and W3SVC were shut down.

Verify

To verify that a Web site is started, you can use either IIS Manager or the appcmd command line utility.

To perform these procedures, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To verify that the Web site is started by using the appcmd command line utility:

  1. Open an elevated Command Prompt window. Click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
  2. Change the directory to %SystemDrive%\Windows\System32\inetsrv.
  3. Run the following command: appcmd.exe list site -site.name:”Site Name”. If the Web site is started, the output will resemble the following:

        SITE “Default Web Site” (id:1,bindings:http/*:80:,state:Started)

To verify that the Web site is started by using IIS Manager:

  1. Click Start, click Control Panel, and then click Administrative Tools.
  2. Right-click Internet Information Services (IIS) Manager and select Run as administrator.
  3. In the Connections pane, expand the computer name.
  4. In the Connections pane, click the Sites node.
  5. In Features View, look for the Web site name. The Web site status will be indicated under the Status column. If the Web site is started and is using the HTTP protocol, Started(http) will appear.

Related Management Information

IIS Web Site Availability

Internet Information Services (IIS) 7.0

Related:

The DHCP service failed to initialize the database. The following error occurred: %1

PCIS Support Team Leave a comment
Details
Product: Windows Operating System
Event ID: 1004
Source: DHCP
Version: 5.0
Component: DHCP
Symbolic Name: EVENT_SERVER_INIT_DATABASE_FAILE
Message: The DHCP service failed to initialize the database. The following error occurred: %1
   
Explanation

This event record indicates that the DHCP database is corrupted.
   
User Action

Remove the corrupted database and replace it with a clean backup copy. Additional information on restoring the DHCP database can be found in the Windows 2000 Resource Kit.

Related:

The local server couldn’t be found. Microsoft Exchange can’t update the Active Directory Application Mode (ADAM) credentials. The exception is %1. Make sure that the service account used by the Microsoft Exchange EdgeSync service has permission to access the local Exchange server object in the Active Directory directory service. Also make sure that the FQDN of the computer matches the FQDN attribute of the server object in Active Directory.

PCIS Support Team Leave a comment
Details
Product: Exchange
Event ID: 1004
Source: MSExchange Message Security
Version: 8.0
Symbolic Name: LocalServerNotFound
Message: The local server couldn’t be found. Microsoft Exchange can’t update the Active Directory Application Mode (ADAM) credentials. The exception is %1. Make sure that the service account used by the Microsoft Exchange EdgeSync service has permission to access the local Exchange server object in the Active Directory directory service. Also make sure that the FQDN of the computer matches the FQDN attribute of the server object in Active Directory.
   
Explanation

This Error event indicates that because Microsoft Exchange cannot locate the local server, it cannot update the credentials that are used by the Microsoft Exchange EdgeSync service to authenticate to the Active Directory Application Mode (ADAM) directory service. The EdgeSync replication account credentials are used by the Hub Transport server to authenticate to ADAM during the EdgeSync synchronization process. The credentials are stored on the Exchange server object in the Active Directory directory service. The Microsoft Exchange EdgeSync service must periodically update these credentials so that they do not expire. The Microsoft Exchange EdgeSync service cannot locate the Hub Transport server in Active Directory to update the credentials. For more information, see Understanding Edge Subscription Credentials.
   
User Action

To resolve this error, do one or more of the following:

  • Verify that the service account that is used by the Microsoft Exchange EdgeSync service has permission to access the local Exchange server object in Active Directory.

  • Verify that the fully-qualified domain name (FQDN) for the local server is the same as the FQDN attribute of the server object in Active Directory.

  • Review other related Error and Warning events in the Application log. These related events may help you find the root cause of this error.

  • If the recommended steps do not resolve this error, contact Microsoft Customer Support Services. For more information about how to contact support, visit the Microsoft Help and Support Web site.

If you are not already doing so, consider running the tools that Microsoft Exchange offers to help administrators analyze and troubleshoot their Exchange environment. These tools can help you make sure that your configuration is in line with Microsoft best practices. They can also help you identify and resolve performance issues, improve mail flow, and better manage disaster recovery scenarios. Go to the Toolbox node of the Exchange Management Console to run these tools now. For more information about these tools, see Toolbox in the Exchange Server 2007 Help.

Related:

Server for NFS is not configured for either Active Directory Lookup or User Name Mapping. Users will not be able to access NFS shares on this server.

PCIS Support Team Leave a comment
Details
Product: Windows Operating System
Event ID: 1004
Source: nfssvr
Version: 5.2.3790.1830
Message: Server for NFS is not configured for either Active Directory Lookup or User Name Mapping. Users will not be able to access NFS shares on this server.
   
Explanation

For UNIX users to access files on a Windows computer through Server for NFS, they must be associated with Windows user accounts.  Active Directory Lookup and User Name Mapping enable Server for NFS to lookup a corresponding Windows user accounts when UNIX users access Server for NFS file shares. If Server for NFS is not configured to lookup UNIX users via Active Directory Lookup or User Name Mapping (Server for NFS only needs one of the two), then Server for NFS cannot provide file access to users.

Cause

In Control Panel, double-click Administrative Tools, then double-click Microsoft Services for NFS. Click Microsoft Services for NFS. In the Action menu, click Properties. If Microsoft Services for NFS is not configured for Active Directory Lookup or User Name Mapping, both fields will be blank (Microsoft Services for NFS needs only one of the two).
   
User Action

If Active Directory Lookup and User Name Mapping are not configured, consult the online help for more information. Once configured, specify the domain for Active Directory Lookup or enter the computer name or IP address of the User Name Mapping server.

Related:

failed to start.

PCIS Support Team Leave a comment
Details
Product: Exchange
Event ID: 1004
Source: MSExchangeSA
Version: 6.5.6940.0
Component: Microsoft Exchange System Attendant
Message: <service name> failed to start.
   
Explanation

An error occurred in the initialization of Microsoft Exchange System Attendant service (Mad.exe). The Error Code in the event ID will usually reveal the reason why the SA is unable to start. This event might also be accompanied by Events 2064, 2072, and so on.

  • Global catalog server cannot be contacted. (Investigate why this is so.)
  • The name of the Windows 2000 server running Exchange has been changed.
  • Kerberos Key Distribution Center (KDC) service may have been disabled.
  • The Manage Auditing and Security Logs permission for the Exchange Enterprise Servers group may be missing.
   
User Action
  • Ensure that the global catalog can be contacted. This is more of a networking issue and could involve enabling/changing firewall ports, and so on.
  • Change the name of the Windows 2000 server to reflect what is in Active Directory.
  • Start the KDC Service and set it to Automatic Startup.
  • Run SETUP/DOMAINPREP to assign the Manage Auditing and Security Logs permission to the Exchange Enterprise Servers Group.

Related:

Unable to start the Microsoft Exchange Information Store. Disk is full.

PCIS Support Team Leave a comment
Details
Product: Exchange
Event ID: 1004
Source: MSExchangeIS Public Store
Version: 6.0
Component: Information Store
Symbolic Name: msgidFailedStartFull
Message: Unable to start the Microsoft Exchange Information Store. Disk is full.
   
Explanation
An administrator can observe disk space usage on the drive containing the Information Store by using System Monitor and Performance Logs and Alerts.The LogicalDisk object, along with the % Free Space and Free Megabytes counters, monitor and trigger alerts when disk space is low. Increasing log files can cause the directory or information store to run out of operating space.
   
User Action
Do one of the following:Write the log files to a different drive. Change the location where the directory or information store transaction logs are written.Back up the Exchange server. Use the Windows Backup utility bundled with Microsoft Exchange Server to perform either a normal (full) or incremental online backup of the server. The Backup utility automatically deletes transaction logs that are no longer needed because they are committed to disk. If you never run the Backup utility, log files continue to grow. Correctly delete log files periodically. When the directory and information stores run, you find log files of the Edb*.log form in both the Exchsrvr\Dsadata and Exchsrvr\Mdbdata directories. Microsoft Exchange Server uses these log files to commit data to disk. Also, these log files are necessary to perform incremental and differential backups using the Windows Backup utility. The Edb*.log files can be deleted after the directory and information store services have been shut down. If the log files are deleted when the services are still running, you can jeopardize data integrity. When the services are stopped, the transactions in these log files are committed to the main database file on disk (Dir.edb for the directory, and Priv.edb and Pub.edb for the information store). When this data is committed, the log files are no longer needed. Follow the steps below to correctly delete log files: 1.Stop all Microsoft Exchange Server services.2. Make a backup copy of the Edb*.log files in both the Exchsrvr\Dsadata and the Exchsrvr\Mdbdata directories. Copy them to an alternate location on the hard drive or to the tape backup.3. Delete all the Edb*.log files in both the Exchsrvr\Dsadata and Exchsrvr\Mdbdata directories.4. Restart all the Microsoft Exchange Server services (in particular, the directory and information store services).5. If these services do not start, restore the Dsadata and Mdbdata subdirectories from tape or hard disk. Restart the services again.6. If the services start, delete the backup copy of the Dsadata and Mdbdata subdirectories.If you delete the Edb*.log files in the manner described above, incremental and differential backups of the directory and information stores are no longer valid or possible. You can only perform a normal type (full) backup.

Related:

service name failed to start.

PCIS Support Team Leave a comment
Details
Product: Exchange
Event ID: 1004
Source: MSExchangeSA
Version: 6.5.0000.0
Message: service name failed to start.
   
Explanation
An error occurred in the initialization of Microsoft Exchange System Attendant service (MAD). The Error Code in the Event ID will usually reveal the reason why the SA is unable to start. This event might also be accompanied by Events 2064, 2072, etc.

  1. Global Catalog Server cannot be contacted. (Investigate why this is so.)
  2. The name of the Windows 2000 Server running Exchange has been

    changed.

  3. Kerberos Key Distribution Center (KDC) service may have been disabled.
  4. The Manage Auditing and Security Logs permission for the Exchange Enterprise Servers group may be missing.
   
User Action
  1. Ensure that the GC can be contacted. This is more of a networking issue

    and might involve enabling/changing firewall ports, and so on.

  2. Change the name of the Windows 2000 machine to reflect what is in Active Directory.
  3. Start the KDC Service and set it to Automatic Startup.
  4. Run SETUP/DOMAINPREP to assign the Manage Auditing and Security Logs permission to the Exchange Enterprise Servers Group.

Related: