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

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

Post by John » Fri, 17 Jun 2005 22:20:39


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.
 
 
 

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

Post by MS Exper » Sat, 18 Jun 2005 04:47:45


Check this article for more details on a fix
http://www.yqcomputer.com/


--
MS Expert
------------------------------------------------------------------------
MS Expert's Profile: http://www.yqcomputer.com/
View this thread: http://www.yqcomputer.com/
Visit - http://www.yqcomputer.com/ | http://www.yqcomputer.com/

 
 
 

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

Post by jasl » Sat, 18 Jun 2005 12:26:22

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.
 
 
 

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

Post by John » Tue, 21 Jun 2005 23:33:31

Jason,

Running the command

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

did not work.

John
 
 
 

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

Post by John » Tue, 21 Jun 2005 23:35:34

I did not upgrade any workstations so I'm not sure this KB article applies
to my situation.

Also, the registry key
HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer does not
exist on any of my workstations.

John
 
 
 

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

Post by jasl » Wed, 22 Jun 2005 17:25:13

Hi John,

In this case, you may need to perform some troubleshooting steps to locate the real cause and a solution. At this time, I suggest you try the
following steps to see if they help on one workstation.

1. Temporarily give the user Administrator permission on that workstation and check if the Office 2000 setup completes well.

2. If 1 does not help, use the same user to logon and go to Add/Remove Programs. Try uninstalling Office 2000 to see if it is successful.

3. If Office 2000 can be uninstalled well, try installing it again from the network source. Then check if the error disappears.

If you need further assistance, feel free to post it here.

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.
 
 
 

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

Post by John » Wed, 22 Jun 2005 21:18:28

Jason,

1. It makes no differenece if the user has Admin permissions on the
workstation.

2. I can uninstall Office 2000 sucessuflly.

3. I can re-install Office 2000 and the error goes away.

However, as I said in my orginial post, I'm not looking for a solution that
involves re-installing Office. I know that will work but I have over 100
workstations and I don't want to have to go to each one and re-install
Office.

Here's what I know:

1. The only change to the workstations was removing the computers from the
old domain (Windows 2000) and adding them to the the new domain (Windows
2003).

2. The users have admin rights to their workstation.

3. The location of the admin installation point has not changed during the
network upgrade. It is the same server, share name, and mapped drive and
the server was not upgraded. It is still a Windows 2000 Server.

4. The user has full read/write access to the admin installation point.

5. Resynchronizing the workstation with the installation point using the
msiexec command or by running setup from the installation point does not
work.

Any ideas?

John
 
 
 

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

Post by jasl » Thu, 23 Jun 2005 20:03:32

Hi John,

I understand your concerns. From the previous test, I am suspecting some domain related IDs registered in the Registry do not match the
new network. Normally, it is hard to locate the exact keys for repairing. I suggest you use Windows Installer command line to reinstall
Office 2000. In this way, you do not need to reinstall Office on each client. Instead, you can simply push a script out to all the clients.

According to my research, the following command may fix this issue. You can first test it on one client experiencing this issue.

msiexec /i <Admin Path>\Data1.msi Reinstall=All ReinstallMode=vomus

where <Admin Path> is the path to your administrative installation point.

In case it does not help, we can use two Windows Installer commands to first uninstall Office and then reinstall it.

msiexec /x {Product Code of the Office SKU}

You can find the Product Code in Office registry keys and it is the same for all Office installations with the same Office suite.

<Admin Path>\setup /i data1.msi /qb+

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.
 
 
 

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

Post by ibeet » Thu, 04 Aug 2005 11:39:37

It definitely has to do w/your application data folder under your uswername
under Documnets and Settings
 
 
 

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

Post by Gerry Hick » Fri, 05 Aug 2005 08:04:02


I'd say this is unlikely, it's usually when an Administrative
Installation Point has not been looked after properly. Jason Lu gives a
good tip below to deal with these kinds of problems.





--
Gerry Hickman (London UK)