Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

"The system cannot find the file specified" error message on a Windows Server 2008 R2-based file server if the remote index server has a catalog that has a credential-enabled UNC path


View products that this article applies to.

Symptoms

Consider the following scenario:
  • You enable the Indexing Service role service on two file servers (Server A and Server B) that are running Windows Server 2008 R2.
  • You create an index catalog on Server A, and then add a UNC path into the index catalog.
  • You configure the credential that is needed to access the UNC path.
  • On Server B, you create an IAdminIndexServer object to access Server A. For example, you run the following Microsoft Visual Basic script:
    set objAdminIS = CreateObject("Microsoft.ISAdm") objAdminIS.MachineName = "[Server A]" msgbox objAdminIS.MachineName 
In this scenario, you receive the following error message:
The system cannot find the file specified
Note This error message indicates that the IAdminIndexServer object cannot access the indexing services on Server A correctly.

↑ Back to the top


Resolution

Hotfix information

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft website: Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

To apply this hotfix, you must be running Windows Server 2008 R2 Service Pack 1 (SP1). Additionally, you must install the File Services server role and enable the Indexing Service role service.

For more information about how to obtain a Windows 7 or Windows Server 2008 R2 service pack, click the following article number to view the article in the Microsoft Knowledge Base:

976932 Information about Service Pack 1 for Windows 7 and for Windows Server 2008 R2

Registry information

To apply the hotfix in this package, you do not have to make any changes to the registry.

Restart requirement

You do not have to restart the computer after you apply this hotfix. To avoid restarting, stop the Indexing Service role service.

Hotfix replacement information

This hotfix does not replace a previously released hotfix.

File information

The global version of this hotfix installs files that have the attributes that are listed in the following tables. The dates and the times for these files are listed in Coordinated Universal Time (UTC). The dates and the times for these files on your local computer are displayed in your local time together with your current daylight saving time (DST) bias. Additionally, the dates and the times may change when you perform certain operations on the files.
Windows Server 2008 R2 file information notes
  • The files that apply to a specific product, milestone (RTM, SPn), and service branch (LDR, GDR) can be identified by examining the file version numbers as shown in the following table:
    VersionProductMilestoneService branch
    6.1.760
    1.17xxx
    Windows Server 2008 R2SP1GDR
    6.1.760
    1.21xxx
    Windows Server 2008 R2SP1LDR
  • GDR service branches contain only those fixes that are widely released to address widespread, extremely important issues. LDR service branches contain hotfixes in addition to widely released fixes.
  • The MANIFEST files (.manifest) and the MUM files (.mum) that are installed for each environment are listed separately in the "Additional file information for Windows Server 2008 R2" section. MUM and MANIFEST files, and the associated security catalog (.cat) files, are extremely important to maintain the state of the updated components. The security catalog files, for which the attributes are not listed, are signed with a Microsoft digital signature.
For all supported x64-based versions of Windows Server 2008 R2
File nameFile versionFile sizeDateTimePlatform
Query.dll6.1.7601.177302,056,19224-Nov-201107:18x64
Query.dll6.1.7601.218672,056,19228-Nov-201106:19x64
Query.dll6.1.7601.177301,363,45624-Nov-201106:22x86
Query.dll6.1.7601.218671,363,45628-Nov-201105:18x86

↑ Back to the top


Status

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.

↑ Back to the top


More Information

For more information about the Indexing Service role service, visit the following Microsoft website:For more information about the IAdminIndexServer interface, visit the following Microsoft website:For more information about software update terminology, click the following article number to view the article in the Microsoft Knowledge Base:

824684 Description of the standard terminology that is used to describe Microsoft software updates

Additional file information

Additional file information for Windows Server 2008 R2

Additional files for all supported x64-based versions of Windows Server 2008 R2
File nameAmd64_2661ac0e6e92534a05690d1cd1e2c740_31bf3856ad364e35_6.1.7601.21867_none_4b043b12a59d16cd.manifest
File versionNot Applicable
File size1,070
Date (UTC)29-Nov-2011
Time (UTC)10:29
File nameAmd64_ac26cece4c2cc99e71184d7387283a76_31bf3856ad364e35_6.1.7601.17730_none_50c3fd1dc4644283.manifest
File versionNot Applicable
File size1,070
Date (UTC)29-Nov-2011
Time (UTC)10:29
File nameAmd64_microsoft-windows-c..ent-indexing-common_31bf3856ad364e35_6.1.7601.17730_none_64c07605edc3a90b.manifest
File versionNot Applicable
File size68,691
Date (UTC)24-Nov-2011
Time (UTC)08:19
File nameAmd64_microsoft-windows-c..ent-indexing-common_31bf3856ad364e35_6.1.7601.21867_none_6530a51306f34e09.manifest
File versionNot Applicable
File size68,691
Date (UTC)28-Nov-2011
Time (UTC)06:53
File nameX86_microsoft-windows-c..ent-indexing-common_31bf3856ad364e35_6.1.7601.17730_none_08a1da82356637d5.manifest
File versionNot Applicable
File size68,687
Date (UTC)24-Nov-2011
Time (UTC)07:23
File nameX86_microsoft-windows-c..ent-indexing-common_31bf3856ad364e35_6.1.7601.21867_none_0912098f4e95dcd3.manifest
File versionNot Applicable
File size68,687
Date (UTC)28-Nov-2011
Time (UTC)05:50

↑ Back to the top


Keywords: kbautohotfix, kbqfe, kbhotfixserver, kbfix, kbsurveynew, kbexpertiseinter, kb

↑ Back to the top

Article Info
Article ID : 2645610
Revision : 1
Created on : 3/21/2017
Published on : 1/11/2012
Exists online : False
Views : 227