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

[Jason Lu [MSFT]]

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.

 

[Jason Lu [MSFT]]

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.

 

[Jason Lu [MSFT]]

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.

 

[Jason Lu [MSFT]]

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.

 

[Jason Lu [MSFT]]

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.

 

[Jason Lu [MSFT]]

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.

 

[John]

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

 

[John]

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

 

[John]

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

 

[John]

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

 

[John]

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

 

[John]

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

 

[John]

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

 

[John]

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

 

[John]

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

 

[Jason Lu [MSFT]]

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.

 

[Jason Lu [MSFT]]

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.

 

[Jason Lu [MSFT]]

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.

 

[Jason Lu [MSFT]]

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.

 

[Jason Lu [MSFT]]

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.