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

J

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

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

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

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

ibeetb

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

ibeetb

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

ibeetb

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

ibeetb

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

ibeetb

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

ibeetb

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

ibeetb

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

ibeetb

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

ibeetb

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

Gerry Hickman

ibeetb said:
It definitely has to do w/your application data folder under your uswername
under Documnets and Settings
Click to expand...

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

Gerry Hickman

ibeetb said:
It definitely has to do w/your application data folder under your uswername
under Documnets and Settings
Click to expand...

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

Gerry Hickman

ibeetb said:
It definitely has to do w/your application data folder under your uswername
under Documnets and Settings
Click to expand...

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

Gerry Hickman

ibeetb said:
It definitely has to do w/your application data folder under your uswername
under Documnets and Settings
Click to expand...

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

Gerry Hickman

ibeetb said:
It definitely has to do w/your application data folder under your uswername
under Documnets and Settings
Click to expand...

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

Gerry Hickman

ibeetb said:
It definitely has to do w/your application data folder under your uswername
under Documnets and Settings
Click to expand...

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

Gerry Hickman

ibeetb said:
It definitely has to do w/your application data folder under your uswername
under Documnets and Settings
Click to expand...

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.
 

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

Similar Threads

REINSTALLING MS OFFICE PRO PLUS 2019 0
Adding Network Trusted Location on MS O365 Word per Computer Registry Setting 1
Active Content in this file is blocked issue 1
"MSysCompactError", "System resource exceeded" & "You do not have the necessary permissions to use the...." 0
office 2000 - feature you are trying to use is on a network resource that is unavailable 7
Error 1719 when trying to add Office Pro 2003 components.(bit long) 0
"The feature you are trying to use is on a network resource that i 0
Which Microsoft Office branch allows you to manually pick components to install? 0

Top