office 2000 - feature you are trying to use is on a network resource that is unavailable

J

John

I have a mix of Windows 2000 and Windows XP clients that have Office 2000
Professional installed from an administrative installation point on my
Windows 2000 Server network. I have just upgrade my network to Windows
20003. Since the domain name changed every workstation had to have a new
user profile created. Now every single computer on my network is running
Office setup when the user logs in to the network.

It starts with a message box that says "Please wait while Windows configures
Microsoft Office 2000 SR-1 Professional".

Then I get a dialog box that says "The feature you are trying to use is on a
network resource that is unavailable. Click OK to try again, or enter an
alternate path to a folder containing the installation package 'data1.msi'
in the box below. The box below says Use source: and is a drop down that
points to my administrative installation point. The server that contains
the administrative installation point still exists in my domain and all
users have read/write access to the folder.

If I click OK it tells me it can't find data1.msi. If I click cancel I get
an error message "Error 1706. No valid source could be found for the
product Microsoft Office 2000 SR-1 Professional. The Windows installer
cannot continue." Then the installer trys to run again and I have to click
cancel.

Tried an Office Repair and it has no affect. There is nothing in the
startup folder or registry startup keys that have anything to do with
Office. You can cancel the installation and Office functions properly on
all the workstations.

So why is this dialog box coming up and how can I get rid of it?

Please do not tell me to re-install Office since I have over 100
workstations and it is not an option. There has to be a registry key or a
file I can modify to eliminate this annoying dialog box coming up.
 
J

Jason Lu [MSFT]

Hi John,

Regarding this issue, I am suspecting the cause is related to the local cache of Office 2000 setup data. I suggest you try the following
steps on one workstation experiencing this issue to check the results.

1. Close all running applications.
2. Click Start->Run.
3. Type the following command in the Open box.

msiexec /fvm <path to the data1.msi on your network>\data1.msi

4. Start Office 2000 to check the result.

If this method helps, you can apply this command to all workstations experiencing this issue.

I hope the information helps.

Regards,
Jason Lu
Microsoft Online Partner Support

When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from your issue.
This posting is provided "AS IS" with no warranties, and confers no rights.
 
J

Jason Lu [MSFT]

Hi John,

Regarding this issue, I am suspecting the cause is related to the local cache of Office 2000 setup data. I suggest you try the following
steps on one workstation experiencing this issue to check the results.

1. Close all running applications.
2. Click Start->Run.
3. Type the following command in the Open box.

msiexec /fvm <path to the data1.msi on your network>\data1.msi

4. Start Office 2000 to check the result.

If this method helps, you can apply this command to all workstations experiencing this issue.

I hope the information helps.

Regards,
Jason Lu
Microsoft Online Partner Support

When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from your issue.
This posting is provided "AS IS" with no warranties, and confers no rights.
 
J

Jason Lu [MSFT]

Hi John,

Regarding this issue, I am suspecting the cause is related to the local cache of Office 2000 setup data. I suggest you try the following
steps on one workstation experiencing this issue to check the results.

1. Close all running applications.
2. Click Start->Run.
3. Type the following command in the Open box.

msiexec /fvm <path to the data1.msi on your network>\data1.msi

4. Start Office 2000 to check the result.

If this method helps, you can apply this command to all workstations experiencing this issue.

I hope the information helps.

Regards,
Jason Lu
Microsoft Online Partner Support

When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from your issue.
This posting is provided "AS IS" with no warranties, and confers no rights.
 
J

Jason Lu [MSFT]

Hi John,

Regarding this issue, I am suspecting the cause is related to the local cache of Office 2000 setup data. I suggest you try the following
steps on one workstation experiencing this issue to check the results.

1. Close all running applications.
2. Click Start->Run.
3. Type the following command in the Open box.

msiexec /fvm <path to the data1.msi on your network>\data1.msi

4. Start Office 2000 to check the result.

If this method helps, you can apply this command to all workstations experiencing this issue.

I hope the information helps.

Regards,
Jason Lu
Microsoft Online Partner Support

When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from your issue.
This posting is provided "AS IS" with no warranties, and confers no rights.
 
J

Jason Lu [MSFT]

Hi John,

Regarding this issue, I am suspecting the cause is related to the local cache of Office 2000 setup data. I suggest you try the following
steps on one workstation experiencing this issue to check the results.

1. Close all running applications.
2. Click Start->Run.
3. Type the following command in the Open box.

msiexec /fvm <path to the data1.msi on your network>\data1.msi

4. Start Office 2000 to check the result.

If this method helps, you can apply this command to all workstations experiencing this issue.

I hope the information helps.

Regards,
Jason Lu
Microsoft Online Partner Support

When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from your issue.
This posting is provided "AS IS" with no warranties, and confers no rights.
 
J

Jason Lu [MSFT]

Hi John,

Regarding this issue, I am suspecting the cause is related to the local cache of Office 2000 setup data. I suggest you try the following
steps on one workstation experiencing this issue to check the results.

1. Close all running applications.
2. Click Start->Run.
3. Type the following command in the Open box.

msiexec /fvm <path to the data1.msi on your network>\data1.msi

4. Start Office 2000 to check the result.

If this method helps, you can apply this command to all workstations experiencing this issue.

I hope the information helps.

Regards,
Jason Lu
Microsoft Online Partner Support

When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from your issue.
This posting is provided "AS IS" with no warranties, and confers no rights.
 
J

Jason Lu [MSFT]

Hi John,

Regarding this issue, I am suspecting the cause is related to the local cache of Office 2000 setup data. I suggest you try the following
steps on one workstation experiencing this issue to check the results.

1. Close all running applications.
2. Click Start->Run.
3. Type the following command in the Open box.

msiexec /fvm <path to the data1.msi on your network>\data1.msi

4. Start Office 2000 to check the result.

If this method helps, you can apply this command to all workstations experiencing this issue.

I hope the information helps.

Regards,
Jason Lu
Microsoft Online Partner Support

When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from your issue.
This posting is provided "AS IS" with no warranties, and confers no rights.
 
J

Jason Lu [MSFT]

Hi John,

Regarding this issue, I am suspecting the cause is related to the local cache of Office 2000 setup data. I suggest you try the following
steps on one workstation experiencing this issue to check the results.

1. Close all running applications.
2. Click Start->Run.
3. Type the following command in the Open box.

msiexec /fvm <path to the data1.msi on your network>\data1.msi

4. Start Office 2000 to check the result.

If this method helps, you can apply this command to all workstations experiencing this issue.

I hope the information helps.

Regards,
Jason Lu
Microsoft Online Partner Support

When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from your issue.
This posting is provided "AS IS" with no warranties, and confers no rights.
 
J

Jason Lu [MSFT]

Hi John,

Regarding this issue, I am suspecting the cause is related to the local cache of Office 2000 setup data. I suggest you try the following
steps on one workstation experiencing this issue to check the results.

1. Close all running applications.
2. Click Start->Run.
3. Type the following command in the Open box.

msiexec /fvm <path to the data1.msi on your network>\data1.msi

4. Start Office 2000 to check the result.

If this method helps, you can apply this command to all workstations experiencing this issue.

I hope the information helps.

Regards,
Jason Lu
Microsoft Online Partner Support

When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from your issue.
This posting is provided "AS IS" with no warranties, and confers no rights.
 
J

John

Jason,

Running the command

msiexec /fvm <path to the data1.msi on your network>\data1.msi

did not work.

John
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top