Windows XP Pro Permissions

[scott]

****o,

First I jusy want to say that this is a great product.

I have installed Adobe acrobat reader 6.01 and primo pdf on a windows xp pro machine. When logged in as a user without admin privaledges and I create a primo pdf doc, adobe will not launch to view the document at the end of the process and gives a generic error. It still creates the pdf document ok and I can open the document after the fact but it will not allow primo pdf to launch adobe.

If I log in with admin rights, it allows primo pdf to launch adobe. I have tried giving the users group modify permissions to the ActivePDF directory but the problem still happens.

Any ideas would be appreciated.

Thanks

[Douglas Saltsman]

The problem is the user context (that primo is running under) does not have access to execute reader. Try giving full access to the directory containing reader.

[drstone]

Hi,
Thank you for supporting this great an easy to use product.
I have the same problem, and I already gave full control to Acrobat Reader directory, as well as C:\Windows\Temp.
When the user try to open the newly created pdf with Acrobat Reader, no problem. The problem only occurs when Primo tries to display the file with Reader.
Any suggestion? It must be a rights problem, as with an administrative account, everything runs well.
Thank you for your support.

[hiandras]

Does your PDF actually gets created?
You mention, that Acrobat Reader is not started, but do you get the PDF file?

regards,
hiandras

[rapacity]

We're having the same problem. It all works fine for administrators, but for normal users we've had a few problems.

First, we needed to grant write access to the main PrimoPDF folder so it could create Temp.ps - I think this is a problem with Ghostscript and not PrimoPDF itself, but it's still a bit of a nuisance.

Now users can create PDF's fine, but we have the problem the O.P. mentioned - Acrobat Reader crashes when it's started to open the file. This doesn't happen to admin users. Even more bizarrely, if you double-click the newly created file in Explorer, then Acrobat Reader can open it just fine.

The generic error message is:

Titlebar: Font Capture: AcroRd32.exe - Application Error

The instruction at "0xff1475ff" referenced memory at "0xff1475ff". The memory could not be "read".

[rapacity]

Anyone else run into this problem or have any suggestions?

[Douglas Saltsman]

****o,

First I jusy want to say that this is a great product.

I have installed Adobe acrobat reader 6.01 and primo pdf on a windows xp pro machine. When logged in as a user without admin privaledges and I create a primo pdf doc, adobe will not launch to view the document at the end of the process and gives a generic error. It still creates the pdf document ok and I can open the document after the fact but it will not allow primo pdf to launch adobe.

If I log in with admin rights, it allows primo pdf to launch adobe. I have tried giving the users group modify permissions to the ActivePDF directory but the problem still happens.

Any ideas would be appreciated.

Thanks


Primo should have the same permissions as the logged in user. If it's not working then that would lead me to believe that the logged in user doesn't have permission to Launch reader. Can you verify this?

[Douglas Saltsman]

Primo should have the same permissions as the logged in user. If it's not working then that would lead me to believe that the logged in user doesn't have permission to Launch reader. Can you verify this?


Seems I posted that last one a little hastily. Primo Simply does a s**** execute of the defualt pdf application on the system. I haven't run into any cases where this hasn't worked before as the permissions should be those mentioned in my last post. I will look into this when we test the beta next.

[harrow]

****o,

First I jusy want to say that this is a great product.

I have installed Adobe acrobat reader 6.01 and primo pdf on a windows xp pro machine. When logged in as a user without admin privaledges and I create a primo pdf doc, adobe will not launch to view the document at the end of the process and gives a generic error. It still creates the pdf document ok and I can open the document after the fact but it will not allow primo pdf to launch adobe.

If I log in with admin rights, it allows primo pdf to launch adobe. I have tried giving the users group modify permissions to the ActivePDF directory but the problem still happens.

Any ideas would be appreciated.

Thanks

My current environment:
Windows XP Pro with Service Pack 2 + Office 2003 Service Pack 2

This is what worked for me:-

Everyone Modify on the following...

-Allows the PrimoPDF window to appear
C:\Windows\Temp (or wherever the system temp directory has been set to.)

-Allows the Adobe Reader 7.0 preview to appear with out any errors
C:\Documents and Settings\LocalService\Application Data

C:\Program Files\activePDF\PrimoPDF

Default Read Permissions on the registry for the local Users group.

Hope That helps.

[thedoge]

My current environment:
Windows XP Pro with Service Pack 2 + Office 2003 Service Pack 2

This is what worked for me:-

Everyone Modify on the following...

-Allows the PrimoPDF window to appear
C:\Windows\Temp (or wherever the system temp directory has been set to.)

-Allows the Adobe Reader 7.0 preview to appear with out any errors
C:\Documents and Settings\LocalService\Application Data

C:\Program Files\activePDF\PrimoPDF

Default Read Permissions on the registry for the local Users group.

Hope That helps.
This may be a reasonable work-around for the SOHO environment, but for a corporation that is trying to implement "locked down" desktops and insists that XP applications meet Microsoft's Windows XP Logo Certification Requirements (http://www.microsoft.com/winlogo/default.mspx), this ain't gonna make it. Well-behaved XP applications shouldn't require local admin rights to run and shouldn't require you to give Everyone modify permissions to the \Windows\Temp directory.

I thought it was odd that PrimoPDF would have made such an obvious error, but now that I've gotten a quote for what it would cost to create a customized version that doesn't fail XP Logo Certification, I'm beginning to understand the strategy here: offer a broken product for free and then charge major $$ to fix it.

Hey, it works for Microsoft... :rolleyes: