I get the following when trying to install on Windows XP Pro
Windows 2000/XP Install
------------------------------------------------------------------------------------
Installing PDF printer driver
Error Code: 5
Access is denied.
------------------------------------------------------------------------------------
Installing PDF printer
Error Code: 1797
The printer driver is unknown.
------------------------------------------------------------------------------------
Printer setup failed
Error Code: 1797
The printer driver is unknown.
------------------------------------------------------------------------------------
Installation error code 5
Hello,
Please check the following:
1 - That you are logging to the system as Administrator.
2 - That you are installing a license for Windows NT / 2000 / XP
3 - That you are running Install.exe from a folder containing all the files and dlls you received with the driver.
4 - That none of these files and dlls is marked as read-only.
5 - Delete any existing file related to the PDF Converter from the system directory and then install the printer.
(You can search for CDIntf*.* and acfpdf*.* in the system directory).
Hope this helps.
Please check the following:
1 - That you are logging to the system as Administrator.
2 - That you are installing a license for Windows NT / 2000 / XP
3 - That you are running Install.exe from a folder containing all the files and dlls you received with the driver.
4 - That none of these files and dlls is marked as read-only.
5 - Delete any existing file related to the PDF Converter from the system directory and then install the printer.
(You can search for CDIntf*.* and acfpdf*.* in the system directory).
Hope this helps.
I had a similar problem on an XP machine a while back. I do not remember if it is the exact same error you are describing or not because I got past it. Here's what I did, and I still don't understand why it didn't work initially.
I attempted to install PDF Converter using the local Admin account on an XP laptop and received a series of error messages that may have been like the one's you list. After a bunch of playing, I tried running the install using a Domain Admin account and it worked. I absolutely do not understand what rights a domain admin would have on an individual machine that a local admin would not have, but it worked.
I attempted to install PDF Converter using the local Admin account on an XP laptop and received a series of error messages that may have been like the one's you list. After a bunch of playing, I tried running the install using a Domain Admin account and it worked. I absolutely do not understand what rights a domain admin would have on an individual machine that a local admin would not have, but it worked.
I can't. I am not a Windows Server admin. I can tell you what it is. I'm willing to bet that if you already have domain logins, there is a domain admin set up somewhere.
You know when you log in to an XP machine, the login screen has (or can have) 3 areas to fill in information: userid, password, and domain. In the last box, you can choose the local computer name. If you log in with an admin account to the local computer, you are using a local admin account. This is admin on that machine only and likely has no rights (or very limited rights) on the wider network.
However, you can also log in as administrator for the entire network. That is a domain admin account. My understanding is that as far as the local machine is concerned, it should have the same rights as a local admin, but it also has much broader rights within the overall network. So, based on this developer's limited understanding of Windows networking and logon accounts, it should make no difference when installing a PDF Converter printer on an individual machine. However, the one time I did it on an XP machine, it did make a difference. (Everyone else is 2000 and I've had no problems with them.)
You know when you log in to an XP machine, the login screen has (or can have) 3 areas to fill in information: userid, password, and domain. In the last box, you can choose the local computer name. If you log in with an admin account to the local computer, you are using a local admin account. This is admin on that machine only and likely has no rights (or very limited rights) on the wider network.
However, you can also log in as administrator for the entire network. That is a domain admin account. My understanding is that as far as the local machine is concerned, it should have the same rights as a local admin, but it also has much broader rights within the overall network. So, based on this developer's limited understanding of Windows networking and logon accounts, it should make no difference when installing a PDF Converter printer on an individual machine. However, the one time I did it on an XP machine, it did make a difference. (Everyone else is 2000 and I've had no problems with them.)
-
fmcsupport
- Posts: 1
- Joined: Mon Jan 26 2004
- Location: Omaha,NE USA
- Contact:
Install error #5 Problems
I am having the same problem and have not been able to successfully resolve the problem.
The problem began only when we got new machines with preinstalled OEM Windows 2000 SP4. I n machines with pre SP 4 w2k this did not happen and does not happen with machines which were upgraded over time from SP 2 W2k to SP4. On those machines the installation proceeds as expected since amyuni was intitially installed on the SP 2 w2k.
We have observed this in the 2.06 version and the 2.07b version that is shipped with the Calyx Sofware application known as Point version 4.3 and V 4.2.
In each case the installation is done with Administrative rights to the machine. Each machine is in a work group so there are no domain controllers or rights issue.
The cdintf.dll file in w2ksp 4 cannot be deleted unless you boot the machine into safe mode since the OS indicates that it is in use at the time.
The cdintf.dll file is not registered in in the registry.
a regsvr32 on the cdintf.dll file will seem to get it to register but the encrypting features that Calyx has incorporated produces error messages.
The version 2.06 that we purchased also produces the same errors as the customize version used by Calyx when installing that. The error is consistent between what we have and Calyx.
Any assistance in this matter is appreciated.
The problem began only when we got new machines with preinstalled OEM Windows 2000 SP4. I n machines with pre SP 4 w2k this did not happen and does not happen with machines which were upgraded over time from SP 2 W2k to SP4. On those machines the installation proceeds as expected since amyuni was intitially installed on the SP 2 w2k.
We have observed this in the 2.06 version and the 2.07b version that is shipped with the Calyx Sofware application known as Point version 4.3 and V 4.2.
In each case the installation is done with Administrative rights to the machine. Each machine is in a work group so there are no domain controllers or rights issue.
The cdintf.dll file in w2ksp 4 cannot be deleted unless you boot the machine into safe mode since the OS indicates that it is in use at the time.
The cdintf.dll file is not registered in in the registry.
a regsvr32 on the cdintf.dll file will seem to get it to register but the encrypting features that Calyx has incorporated produces error messages.
The version 2.06 that we purchased also produces the same errors as the customize version used by Calyx when installing that. The error is consistent between what we have and Calyx.
Any assistance in this matter is appreciated.
Hello,
Please send an e-mail about installation problems you are facing under Windows 2004 with detail information to support@amyuni.com we will check this issue and will get back to you.
Thanks.
Please send an e-mail about installation problems you are facing under Windows 2004 with detail information to support@amyuni.com we will check this issue and will get back to you.
Thanks.