Event ID - 355

Event Id355
SourceWMServer
DescriptionThe WMS Cache Proxy plug-in could not open the cache database index %1. %2
Event InformationAccording to Microsoft :
Cause :
The Network Service account does not have appropriate permissions for the cache directory on the cache/proxy server
To determine the Network Service account permissions for the cache directory:
  1. On the Windows Media cache/proxy server, open Windows Media Services. To open Windows Media Services, click Start, point to Administrative Tools, and then click Windows Media Services.
  2. In the console tree, click the Windows Media server for which you want to cache content.
  3. In the details pane, click the Properties tab.
  4. In Category, click Cache/Proxy Management.
  5. In Plug-in, right-click WMS Cache Proxy, and then click Properties.
  6. In the WMS Cache Proxy Properties dialog box, on the Cache tab, note the cache directory path value in Cache Directory Path. The default value is %systemdrive%\WMSCache.
  7. In Windows Explorer, right-click the cache folder, and then click Properties.
  8. On the Security tab, in the Group or user names area, click NETWORK SERVICE.
  9. In the Permissions for NETWORK SERVICE area, view the permissions allowed for the Network Service account.
  10. If the Network Service account does not have Read, Write, and Modify permissions to the cache directory, see the section titled "Specify Network Service account permissions for caching."
Resolution :
Specify Network Service account permissions for caching
Windows Media Services uses the Network Service account to manage the content files that are cached in %systemdrive%\WMSCache and its subdirectories on the cache/proxy server. By default, the Network Service account has Read, Write, and Modify permissions to the WMSCache directory and its subdirectories.
If the specified cache folder does not reside in %systemdrive%\WMSCache, you must specify permissions on the alternate cache folder for the Network Service account on the cache/proxy 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 Network Service account permissions for caching:
  1. On the Windows Media cache/proxy server, open Windows Media Services. To open Windows Media Services, click Start, point to Administrative Tools, and then click Windows Media Services.
  2. In the console tree, click the Windows Media server for which you want to cache content.
  3. In the details pane, click the Properties tab.
  4. In Category, click Cache/Proxy Management.
  5. In Plug-in, right-click WMS Cache Proxy, and then click Properties.
  6. In the WMS Cache Proxy Properties dialog box, on the Cache tab, note the cache directory path value in Cache Directory Path. The default value is %systemdrive%\WMSCache.
  7. In Windows Explorer, right-click the cache folder, and then click Properties.
  8. On the Security tab, click Edit.
  9. In the Permissions for <Object name> dialog box, click Add.
  10. In the Select Users, Computers, or Groups dialog box, in Enter the object names to select, type Network Service, and then click OK.
  11. In the Permissions for <Object name> dialog box, in the Group or user names area, click NETWORK SERVICE.
  12. In the Permissions for NETWORK SERVICE area, click the Allow check box for the following permissions: Read, Write, Modify.
  13. Click OK to save the changes.
Cause :
The cache index file on the cache/proxy server is missing
To determine whether the cache index file is missing:
  1. On the Windows Media cache/proxy server, open Windows Media Services. To open Windows Media Services, click Start, point to Administrative Tools, and then click Windows Media Services.
  2. In the console tree, click the Windows Media server for which you want to cache content.
  3. In the details pane, click the Properties tab.
  4. In Category, click Cache/Proxy Management.
  5. In Plug-in, right-click WMS Cache Proxy, and then click Properties.
  6. In the WMS Cache Proxy Properties dialog box, on the Cache tab, note the cache directory path value in Cache Directory Path. The default value is %systemdrive%\WMSCache.
  7. In Windows Explorer, open the cache folder.
  8. If the cache index file named CacheIndex.txt is not present in the cache folder, see the section titled "Create a new cache index file."
Resolution :
Create a new cache index file
To create a new cache index file, you must empty the cache directory on the cache/proxy server. The next time a client requests content, the cache/proxy server will download the requested content from the origin server and create a new cache index file that includes an entry for the content.
To perform this procedure, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.
To empty the cache directory:
  1. On the Windows Media cache/proxy server, open Windows Media Services. To open Windows Media Services, click Start, point to Administrative Tools, and then click Windows Media Services.
  2. In the console tree, click the Windows Media server for which you want to cache content.
  3. In the details pane, click the Properties tab.
  4. In Category, click Cache/Proxy Management.
  5. In Plug-in, right-click WMS Cache Proxy, and then click Properties.
  6. In the WMS Cache Proxy Properties dialog box, on the Cache tab, note the cache directory path value in Cache Directory Path. The default value is %systemdrive%\WMSCache.
  7. In Windows Explorer, open the cache folder.
  8. Select all files and folders in the cache folder, and then delete them.
Verify :
To verify that cache/proxy servers on your network can cache content files from the origin server, prestuff the cache directory on the cache/proxy servers with one or more content files from the origin server. Prestuffing content means that you are caching the content on the cache/proxy servers before it is requested by clients. It is a good way to confirm that cache/proxy servers on your network can communicate with the origin server.
Reference LinksEvent ID 355 from Source WMServer

Catch threats immediately

We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.

See what we caught

Did this information help you to resolve the problem?

Yes: My problem was resolved.
No: The information was not helpful / Partially helpful.