Event 8197 – Intelligent Systems Monitoring

Event ID 8197 — Windows to UNIX Password Synchronization — Configuration Issues

May 23, 2017May 23, 2017 PCIS Support Team Leave a comment

Event ID 8197 — Windows to UNIX Password Synchronization — Configuration Issues

Updated: December 16, 2008

Applies To: Windows Server 2008 R2

Windows to UNIX Password Synchronization — Configuration Issues indicates the completeness or usability of settings that are configured for Windows to UNIX password synchronization.

When Password Synchronization is properly configured for Windows-to-UNIX synchronization, and a password is changed on a Windows-based computer running Password Synchronization, the Password Synchronization service determines whether the user’s password is to be synchronized on UNIX computers. When the Password Synchronization service is operating normally, and encryption keys in both the UNIX and Windows environments match, it encrypts the password and sends it to the Password Synchronization daemon on each computer with which the Windows-based computer is configured to be synchronized. The daemon then decrypts the password and changes the password on the UNIX host.

Event Details

Product:	Windows Identity Management for UNIX
ID:	8197
Source:	Microsoft-Windows-IDMU-PSync
Version:	6.0
Symbolic Name:	MSG_ERROR_CONNECTING_HOST
Message:	Error in connecting to host at the specified port. %rhost = %1 %rport = %2 %rPlease verify that the host is up and is running SSOD on the specified port. Windows Sockets error is in the message data.

Resolve
Check SSOD

Verify that the UNIX host computer is operational, and that the UNIX host is running the single sign-on daemon (SSOD) on the specified port. A Windows Sockets error is logged in the Event Viewer message data providing the exact failure error code.

For more information, see the topic “Install the Password Synchronization daemon on UNIX-based computers” in the Password Synchronization Help.

Verify

Retry Windows to UNIX password synchronization for any failed user password change attempts to verify that Password Synchronization is operating normally. Password Synchronization is operating normally when password synchronization succeeds and is operating under warning conditions if synchronization fails for some passwords but succeeds for others.

If password synchronization succeeds for some passwords but fails for others, Windows to UNIX Password Synchronization Configuration is likely fully operational, but there might be account- or computer-specific configuration problems preventing password changes from being synchronized on UNIX-based hosts.

Related Management Information

Windows to UNIX Password Synchronization — Configuration Issues

Identity Management for UNIX

Event ID 8197 — Remote Desktop License Server Database Availability

May 23, 2017May 23, 2017 PCIS Support Team Leave a comment

Event ID 8197 — Remote Desktop License Server Database Availability

Published: January 8, 2010

Applies To: Windows Server 2008 R2

When the Remote Desktop Licensing role service is installed, a database is created in which to hold information about the Remote Desktop Services client access licenses (RDS CALs) that are installed onto the license server.

The location of the RD Licensing database can be specified during the Remote Desktop Licensing role service installation. The database location must be a local folder on the computer on which the Remote Desktop Licensing role service is being installed. By default, the RD Licensing database is located in the %systemroot%\system32\lserver folder, where %systemroot% is the folder in which the operating system is installed, which is, by default, c:\windows. You can confirm the location of the RD Licensing database by using Review Configuration in the Remote Desktop Licensing Manager tool.

Event Details

Product:	Windows Operating System
ID:	8197
Source:	Microsoft-Windows-TerminalServices-Licensing
Version:	6.1
Symbolic Name:	TLS_W_TLSARW_DBPATH_FAIL
Message:	The RD Licensing database path could not be set to “%1!s!” during the installation of RD Licensing.Win32 error code: %2!s!

Resolve
No further action is required because the default database path will be used

During the installation of the Remote Desktop Licensing role service, the path that was specified for the RD Licensing database could not be used. Therefore, RD Licensing will use the default path instead. The default path is %systemroot%\system32\lserver (where %systemroot% is the folder in which the operating system is installed, which is, by default, c:\windows).

When specifying the location of the RD Licensing database during the installation of the Remote Desktop Licensing role service, ensure the following:

The path exists.
The path is local to the computer on which you are installing the Remote Desktop Licensing role service.
You have the required permissions to the path.

Important: The path to the RD Licensing database cannot be changed after the Remote Desktop Licensing role service has been installed.

Verify

To verify the location of the RD Licensing database, use Review Configuration in the Remote Desktop Licensing Manager tool. By default, the RD Licensing database is located in the %systemroot%\system32\lserver folder (where %systemroot% is the folder in which the operating system is installed, which is, by default, c:\windows).

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

To verify the location of the database folder:

On the license server, open Remote Desktop Licensing Manager. To open Remote Desktop Licensing Manager, click Start, point to Administrative Tools, point to Remote Desktop Services, and then click Remote Desktop Licensing Manager.
If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Yes.
In the left pane, click All Servers, click the name of the license server, and then on the Action menu, click Review Configuration.
The database location is listed at the top of the Configuration dialog box.

Use Windows Explorer to navigate to the folder containing the RD Licensing database to confirm its existence and that it contains the tslic.edb file.

Related Management Information

Remote Desktop License Server Database Availability

Remote Desktop Services

Event ID 8197 — FSRM Basic Functionality

April 21, 2017April 21, 2017 PCIS Support Team Leave a comment

Event ID 8197 — FSRM Basic Functionality

Updated: January 27, 2011

Applies To: Windows Server 2008

File Server Resource Manager (FSRM) uses minifilter drivers to intercept the I/O requests that are sent to the volumes it manages. These minifilter drivers require configuration information from metadata files that are stored in each of the volumes that the minifilter drivers are attached to.

Event Details

Product:	Windows Operating System
ID:	8197
Source:	srmsvc
Version:	6.0
Symbolic Name:	SRM_ERROR_UNEXPECTED_ERRORCODE
Message:	File Server Resource Manager Service error: Unexpected error. %1

Resolve
Monitor system resources

Determine if the computer is low on system resources like CPU resources, disk I/O performance, or memory. To identify what is causing the system to be low on resources, you can generate a System Diagnostics Report using Reliability and Performance Monitor, or you can use Resource Monitor to determine, in real-time, which applications or services are utilizing too many system resources.

To generate a System Diagnostics Report, which will present system information collected for 60 seconds, follow the steps in the “Generate a System Diagnostics Report” section. To use Resource Monitor to monitor system resources in real-time, follow the steps in the “Start Resource Monitor” section.

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

Generate a System Diagnostics Report

To collect system information for 60 seconds and generate a System Diagnostics Report:

Open an elevated command prompt. Click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
Type perfmon /report and press ENTER. Reliability and Performance Monitor will start collecting data to create the System Diagnostics Report.
When the report is ready for viewing, locate the Diagnostic Results section of the report and check for any Warnings. You can follow links to additional help on resolving warnings from this section. In addition, you can expand each category in the Basic System Checks section to see more details about why warnings appear. Also, the Performance section provides process-level detail about the top consumers of resources.

Start Resource Monitor

To start Resource Monitor:

Important: Resource Monitor stops collecting information while a System Diagnostics Report is being generated. To start collecting information after a System Diagnostics Report has completed, in Monitor, click Start.

Open an elevated command prompt. Click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
Type perfmon /res and press ENTER. Resource Monitor will start running.
Four scrolling graphs in the Resource Overview pane display the real-time usage of CPU, Disk, Network, and Memory. Four expandable sections below the graphs contain process-level detail about each resource. Click the resource labels to see more information, or click a graph to expand its corresponding details. You can use the real-time usage information to identify the top resource consumers. Click a column heading to sort the data in the table by that column; click the column heading again to reverse the sort order.

Verify

To verify that basic File Server Resource Manager (FSRM) functionality is available, you must verify that the quota and file screening minifilter drivers are attached to the volumes that are managed by File Server Resource Manager.

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

To verify that the quota and file screening minifilter drivers are attached to the volumes managed by File Server Resource Manager:

Open an elevated command prompt. Click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator.
Type fltmc instances, and press ENTER. A quota minifilter driver is attached to a volume if there is a Quota instance listed for that volume. A file screening minifilter driver is attached to a volume if there is a Datascrn instance listed for that volume. For example, on a computer where file screens are configured for drive C and D, and quotas are configured for drive C, the output of this command would look something like this:
Filter          Volume Name    Altitude    Instance Name

———    —————    ——–    —————

Datascrn    C:                       261000    Datascrn

Datascrn    D:                       261000    Datascrn

Quota        C:                       125000    quota

Related Management Information

FSRM Basic Functionality

File Services

Calendaring agent failed to initialize with error server name.

February 9, 2017February 9, 2017 PCIS Support Team Leave a comment

Details
Product:	Exchange
Event ID:	8197
Source:	EXCDO
Version:	6.5.0000.0
Message:	Calendaring agent failed to initialize with error server name.

Explanation
This failure can occur because of logon failures to mailbox and public folder stores.

User Action
Follow the instructions in the message.

The conference technology controller is now communicating with the T.120 MCU {name}.

February 8, 2017February 8, 2017 PCIS Support Team Leave a comment

Details
Product:	Exchange
Event ID:	8197
Source:	MSExchangeDCS
Version:	6.0
Component:	Conferencing Service
Symbolic Name:	MSG_MOVETOACTIVELIST
Message:	The conference technology controller is now communicating with the T.120 MCU {name}.

User Action
No user action is required.

Error initializing session for virtual machine %1. The error number is %2. Make sure Microsoft Exchange Store is running. Also, make sure that there is a valid public folder database on the Exchange server.

February 8, 2017February 8, 2017 PCIS Support Team Leave a comment

Details
Product:	Exchange
Event ID:	8197
Source:	MSExchangeFBPublish
Version:	8.0
Symbolic Name:	evtInitSessionError
Message:	Error initializing session for virtual machine %1. The error number is %2. Make sure Microsoft Exchange Store is running. Also, make sure that there is a valid public folder database on the Exchange server.

Explanation
This Error event indicates that the Microsoft® Exchange Server that logged this event could not initialize a MAPI session to a public folder store. A MAPI session to the public folder store must be initialized for Exchange Server Schedule+ Free Busy functionality to work correctly for Microsoft Office Outlook® 2003 or earlier clients.

User Action
To resolve this error, follow these steps: Make sure that at least one public folder store in your Exchange organization is in the Mounted state. Review other related Error and Warning events in the Application and System log. These related events may help you find the root cause of this event. 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.

There was a failure during startup of the Microsoft Exchange H.323 Conferencing Bridge. The registry was not configured properly. Error code: {error code}; Message: {message id}

January 11, 2017January 11, 2017 PCIS Support Team Leave a comment

Details
Product:	Exchange
Event ID:	8197
Source:	MSExchangeH323
Version:	6.0
Component:	Conferencing Service
Symbolic Name:	MSG_STARTUP_MISSING_REGENTRY
Message:	There was a failure during startup of the Microsoft Exchange H.323 Conferencing Bridge. The registry was not configured properly. Error code: {error code}; Message: {message id}

User Action
Reinstall Exchange Conferencing Server.

Error initializing session for virtual machine %1. The error number is %2. Make sure Microsoft Exchange Store is running.

January 10, 2017January 10, 2017 PCIS Support Team Leave a comment

Details
Product:	Exchange
Event ID:	8197
Source:	MSExchangeFBPublish
Version:	6.5.0000.0
Message:	Error initializing session for virtual machine %1. The error number is %2. Make sure Microsoft Exchange Store is running.

Explanation
Free/Busy Publishing has encountered errors attempting to log on to the Private or Public Information Stores. Transient occurrences of this event are not a problem, but if it is recurring every 25-30 minutes, then Free/Busy Publishing is down for all Outlook Web Access users. This event may also be generated if relevant services have recently been cycled or re-started.

User Action
This event can be caused by a wide variety of underlying problems, including problems with the associated MAPI profiles. Investigate further for other alerts and events which may be related. Often the most expedient solution is to cycle the System Attendant service.

Tag: Event 8197

Event ID 8197 — Windows to UNIX Password Synchronization — Configuration Issues

Related:

Event ID 8197 — Remote Desktop License Server Database Availability

Related:

Event ID 8197 — FSRM Basic Functionality

Related:

Calendaring agent failed to initialize with error server name.

Related:

Error initializing session for virtual machine %1. The error number is %2. Make sure Microsoft Exchange Store is running. Also, make sure that there is a valid public folder database on the Exchange server.

Related:

There was a failure during startup of the Microsoft Exchange H.323 Conferencing Bridge. The registry was not configured properly. Error code: {error code}; Message: {message id}

Related:

Error initializing session for virtual machine %1. The error number is %2. Make sure Microsoft Exchange Store is running.

Related:

Links