Problems with installing PrintManager and SQL Server

server| problem
Problems encountered with installing Autodest PrintManager/Installing SQL Server

In order to refer to the workflow of the print server, specially found a autodest printmanager to see.

Installation steps for Autodest PrintManager:

Step one. PrintManager Database Installation
Step two. PrintManager Web site Installation
Step three. PrintManager Print Service Installation
Step four. Registration

Mainly in "Step one." PrintManager Database Installation "encountered a problem.
Question 1:
The PrintManager database needs to be installed on a machine with SQL Server, so you must install SQL Server first.
When you install SQL Server2000, the system pops up a warning message box that says "A previous program installation has created a pending file operation on the installation computer." You must restart your computer before running Setup! "。
The problem remains after the reboot.
So on Google search:
The most common article is "a SQL Server 2000 installation Adventure", but it is unintelligible, the article did not find the essence of the problem;
Continue to search, finally found the answer, delete HKEY_LOCAL_MACHINE Ystem\currentcontrolset\control Ession manager\pendingfilerenameoperations can.

The immediate cause of the problem involves an old problem ———— Psdriver, see appendix.

Question 2:
After installing SQL Server2000, continue to install the PrintManager database, prompting for errors "[Dbnetlib][connection Connect ()].] SQL Server does not exists or access denied.
Consult the Printmanagerde document, which is the PrintManager requires that the SA user of SQL Server must set a password and then have to reload SQL Server.


Because just want to see how printmanager work, so registration is not important. But with SoftICE simple follow, PrintManager registration protection does not seem to be very complicated, you can try when free.

Appendix: The old Problem of Psdriver

Psdriver was something that was long ago.

Simply put, Psdriver is under Window2000, create a virtual printer, other application can easily generate PS files through this printer, plus the collaboration of Acrobat Distillr, you can generate a PDF.

Now, because of print Manager, it's involved, even though it's just a little problem right now.

Psdriver is called AddPrinterDriver to install the printer.

The AddPrinterDriver caller only needs to copy the driver to the directory:%system% pool\drivers\w32x86

When AddPrinterDriver is invoked, the system copies the files to the directory:%system% pool\drivers\w32x86\3

Specific to PPD:
At the first installation, the system copies the PPD file to the "%system% ystem32 pool\drivers\w32x86\3" and generates a bpd file. When the installation is repeated, the system determines whether to update the PPD based on the modified date of the PPD file. If the PPD is new, replace the old PPD, that is, copy it once; otherwise, do nothing!

The problem now is that if the PPD file that was first provided is read-only, the system simply copies the files and the file properties do not change. When you need to update the PPD, because the PPD under "%system% ystem32 pool\drivers\w32x86\3" is also read-only, the system copy will fail!!!
The system then modifies the registry by:
HKEY_LOCAL_MACHINE Ystem\currentcontrolset\control Ession Manager\
Write a key value below:
PendingFileRenameOperations = "\?? \c:\winnt ystem32 pool\drivers\w32x86\3\new\test.ppd\?? \c:\winnt ystem32 pool\drivers\w32x86\3\test.ppd\?? \c:\winnt ystem32 pool\drivers\w32x86\3\old\test.ppd\?? \c:\winnt ystem32 Pool\drivers\w32x86\3\old "
The end of the tail is not, you can see, the previous paragraph is pointed out in the system restart, with C:\WINNT ystem32 POOL\DRIVERS\W32X86\3\NEW\TEST.PPD cover C:\WINNT ystem32 pool\drivers\ W32X86\3\TEST.PPD, so that the purpose of the update PPD is achieved.
Note: This is a typical installation-driven processing strategy, but it won't work if the destination file is readable.

The back of the code tail is gone, unknown, so.

After restarting the machine, the actual situation is:
PendingFileRenameOperations = "\?? \c:\winnt ystem32 POOL\DRIVERS\W32X86\3\OLD\TEST.PPD "

Obviously this is not syntactically, and can only be deleted manually, it is the existence of the above SQL Server installation error!!!

To add, this problem has already been dealt with, that is, when installing, remove the PPD read-only attribute. The only problem is that the garbage in the registration list is not clean.

After a few days to tidy up the psdriver, to get a relatively friendly gadget out.