Hello Everyone,
Can anyone please help me finding a solution installing publisher 2010 on the machine with office 2010.(It occurs only on our company's image)

When i install publisher2010.msp file on a machine with office 2010 and launch the application it errors out
"Publisher cannot load the required file (PTXT9.DLL). You may be out of out of memory, or the file may be corrupt".It happens only on Celanese Image machines.

I tried deleting the file and running a repair and it didnot help me out. So,I then created a new publisher.msp with customization not to remove any office components during installation but then the office 2010 was uninstalled from the system and publisher was installed with out showing any errors.(It wasn't helpful!!)

I figured out that when i reinstall office 2010 with publisher , it works absolutely fine.

Regards,
VK
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
Hello All,

i have installed office publisher 2010, on my customized build which is having all the latest softwares installed.after launching the shortcut office publisher 2010, Go to File->New, recent, options, what ever clicked on i am getting the error "Publisher cannot load the required file (PTXT9.DLL). You may be out of out of memory, or the file may be corrupt". it is high priority for me.

Please let me know any one has faced the same issue and they have the solution.

I have tried deleting the file PTXT9.DLL and replaced from the source, no luck. even i tried repairing after that still it is not working.

If you have any other suggestions please post me.


Thanks,
Sreenivasulu,
System Administrator,
Application Packager.
Answered 08/30/2011 by: sp47328
Yellow Belt

Please log in to comment
0
Are there any clues in the event log? Have you tried using ProcMon when Publisher starts up, to see if perhaps there are other things going on which the error message isn't telling you?
Answered 08/31/2011 by: VBScab
Red Belt

Please log in to comment
0
I have experienced the same issue with an Office 2010 build with Publisher "not installed". The problem occurs with a standalone installation of Publisher 2010.

I found a workaround is to create a new *.msp for the Office 2010 build with Publisher *enabled". Then apply the patch directly, i.e. msiexec.exe /p new.msp

Give this a try.
Answered 09/03/2011 by: qz7cbz
Yellow Belt

Please log in to comment
Answer this question or Comment on this question for clarity