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

[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.

 

[Ada Pan [MSFT]]

Hi John,

According to your description, I know that after you upgrade the server
Office setup will run when the users log onto the network. If I am off
base, please feel free to let me know.

Based on my experience and research, this problem occurs if the following
conditions are true:

- You installed Office from an administrative installation.
- The administrative installation was updated with a Windows Installer
update. For example, the Office 2000 SR-1a administrative update or the
Outlook E-mail Security Update.
- Your network client was not updated from the administrative installation
after the Windows Installer update was applied to the administrative
installation.
- On the network client, you clicked Repair Office in the Microsoft Office
2000 Maintenance Mode dialog box.
- You clicked either Reinstall Office or Repair errors in my Office
installation in the Reinstall/Repair Microsoft Office 2000 dialog box.

When you perform a repair or reinstall that is initiated from the
Add/Remove Programs Control Panel, the Windows Installer does not recache
the .msi file (Data1.msi) from the updated administrative installation onto
the network client.

To resolve this problem, use one of the following methods.

Method 1: Run Setup.exe from the Administrative Installation
----------------------------------------------------------------------------
--------------
1. Click Start, and then click Run. Type a command line similar to the
following in the Open box:
Admin Path\Setup.exe /qb
where Admin Path is the path to your administrative installation point.

2. Click Yes if prompted to restart your computer.

Method 2: Use a Command Line
----------------------------------------------
1. Click Start, and then click Run. Type a command line similar to the
following in the Open box:
msiexec /i Admin Path\Data1.msi Reinstall=All ReinstallMode=vomus
where Admin Path is the path to your administrative installation point.

2. Click OK when the update is finished.

3. Click Yes if you are prompted to restart your computer.

If there is anything unclear or you need further assistance, please feel
free to let me know.

Regards,

Ada Pan

Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
=====================================================
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.

 

[John]

Ada,

I tried both methods and niether worked.

John

 

[Ada Pan [MSFT]]

Hi John,

Here is the sample VB script which will change the source list. However,
you need to modify to fit on your environment for ProductCode and
sNewSource in the sample.

You can use the below script to modify the SourceList for the Windows
Installer to your local servers. This script looks for the SourceList to
clear and rebuild by checking the ProductCode provided by our developer,
Office 2000 in the example below. Then it clears the SourceList and adds
the sources back that are specified in sNewSource1, sNewSource2, etc...

========================================
Dim installer
Const sProductCode = "{00000409-78E1-11D2-B60F-006097C998E7}" 'Office 2000
Premium
Const msiInstallStateUnknown = -1
Const msiInstallStateAdvertised = 1
Const msiInstallStateAbsent = 2
Const msiInstallStateDefault = 5
Const sUserName = ""

Const sNewSource1 = "\\off2kservername1\share"
' Const sNewSource2 = "\\off2kservername2\share"
' Const sNewSource3 = "\\off2kservername3\share"
' Const sNewSource4 = "\\off2kservername4\share"
' Const sNewSource5 = "\\off2kservername5\share"

' On Error Resume Next
Set installer = CreateObject("WindowsInstaller.Installer")
Select Case installer.ProductState(sProductCode)
Case msiInstallStateDefault, msiInstallStateAdvertised
' if advertised or installed for this user then continue

' empty the current list
installer.ClearSourceList sProductCode, sUserName

' add the new the source
' all new sources get added to the Net sources
installer.AddSource sProductCode, sUserName, sNewSource1

' repeat above for all new sources
installer.AddSource sProductCode, sUserName, sNewSource2
' installer.AddSource sProductCode, sUserName, sNewSource3
' installer.AddSource sProductCode, sUserName, sNewSource4
' installer.AddSource sProductCode, sUserName, sNewSource5

' next time the app needs a path, force it to get a new one
installer.ForceSourceListResolution sProductCode, sUserName

Case msiInstallStateAbsent
MsgBox "This product is installed but not for this user"
Case msiInstallStateUnknown
MsgBox "This product is not installed. Are you sure you used the correct
Product code?"
Case Else
MsgBox "Cannot tell if this product is installed. " & _
"Either the parameters are incorrect or the " & _
"product configuration is corrupt"
End Select
========================================


For your reference:
------------------------------
ProductCode = "{00000409-78E1-11D2-B60F-006097C998E7}" 'Office 2000 Premium
ProductCode = "{00210409-78E1-11D2-B60F-006097C998E7}" 'MultiLanguage Pack
Disc2 (Japan and Korean) ProduceCode=
"{00230409-78E1-11D2-B60F-006097C998E7}" 'MultiLanguage Pack Disk4
(Simplified Chinese and Traditional Chinese).

Hope this help! Please let me know if you need any assistance from me.

Regards,

Ada Pan

Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
=====================================================
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.

 

[bgracy]

I am having this exact same issue. We recently rebuilt our domain
controller from scratch. After we did this our office installs are
having the exact same problem. We did not change anything on the
Administrative installation point besides reassigning permissions.

Here is what I have tried to do so far:
*Remove and reinstall office from the administrative install point
*Run the msiexec command to reinstall and recache this installation
*Redid the administrative installation point from scratch and
reinstalled all office updates on the administrative install point
*Installed a fresh copy of windows and office on the computer

All of these steps have resulted in the same issue. Our Office XP and
2003 installations do not have these same problems. I did not try the
vbscript yet to try to remedy the situation because I don't think it
will do anything. I will try it next however.

 

[Ada Pan [MSFT]]

Hello Bgracy,

Based on your information, I know that you encounter a similar issue. You
can try the suggestion to check if it helps.

In the meantime, I would like to tell you we answer one question per post
in the newsgroups. In order to concentrate fully on the new issue we ask
that you post it as a separate thread. That way each issue can receive full
attention and will also make the thread more clear and consistent for
others reference. Please feel free to open a new post for your issue.

Thank you,

Ada Pan

Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
=====================================================
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.

 

[John]

At least your post confirms to me this is a problem and not some kind of
wierd configuration thing that is only affecting my network.

None of the suggested fixes have worked for me and I've done quite a bit of
research on this. So at this point I've given up and bit the bullet to do
things the hard way.

The only way I could fix the problem is:

1. Uninstall Office 2000 Premium.

2. Run the Offfice Removal Wizard from the Office 2003 Resource kit and let
it delete everything it finds.

3. Copy the Office 2000 cabs to each workstation from the cd.

4. Run the Office 2000 setup from the cabs I copied to each workstation.

A totally crappy solution if you ask me but it's all I can get working. It
will have to do until the next version of Office (2006?) comes out since I
skipped XP and it's too soon to the next version to invest money in Office
2003.

John

 

[Ada Pan [MSFT]]

Hi John,

I am glad to know you have resolved the problem. I am sorry to say we
didn't find the root cause of this issue and you spent so much time to
resolve this issue by reinstallations on each workstation. I can
understand your concerns on this issue. I suggest that you submit a
Microsoft Wish to our development team directly. We strive to capture any
and all product issues and feedback so as to ensure that we are
continuously developing Microsoft products to meet customer needs. This is
exactly why feedback such as yours is always taken very seriously. For your
convenience, you can send your comments or suggestions via e-mail, use the
following Microsoft Wish Program e-mail address: (e-mail address removed) .

Thank you for your understanding and efforts.

Regards,

Ada Pan

Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
=====================================================
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.