Microsoft Graph Problems in Office XP Pro

[pshankland]

Hi,

Running Windows 2000 SP2 (server & pro.). Active Directory installing Office XP using group policy on a computer basis.

We are having a problem with Microsoft Office XP and inserting graphs into Word and Powerpoint.

When you press the Chart icon you get the following error message:

'Unable to run Microsoft Graph Developer Edition. You must have Microsoft Graph to create or edit charts.'

After pressing the OK button the next error appears:

'Microsoft PowerPoint can't start the application required to open this object. An error occured and this feature is no longer funtioning properly. Would you like to repair this feature now?'

After pressing Yes Office tried to installed 'Application server' but then comes back with the same original error.

I have checked and Chart is installed on every machine as default and Excel even allows you to insert a chart correctly.

Does anyone have any ideas??

Cheers.

 

[onedtent]

if u r using Norton antivirus, unregister Officeav.dll


also, re-register your msgraph

Go to Start, Run and type
"C:\Program Files\Microsoft Office\Office\graph9.exe" /regserver

that could be graph10.exe for xp

 

[pshankland]

Have tried what you suggested but still no luck. One of the errors that I am getting which looks a bit strange is when Office tries to install 'Application Server'??

 

[onedtent]

check this link:

http://support.microsoft.com/default.aspx?scid=KB;EN-US;q134863&

other than this, i have no clue

 

[pshankland]

I know it has been a long time since I replied in this thread, but I have found the answer to my problem(s). It seems as though when a new machine has been built with the image of W2K and then the apps get installed through Active Directory and Group Policy, if a certain app / msi is run before an OfficeXP app is run, then this problem occurs. I don't know what the offending app / msi is, but as long as all of OfficeXP is installed before anything else, then this problem dosn't happen. This does mean that we will have to visit every machine with this problem (40+), and re-build every single one, hehe.

Thanks for help.