Problems encountered by installing Autodest PrintManager / Installing SQL Server
In order to refer to the workflow of the print server, I will find an Autodest PrintManager to see. Autodest PrintManager installation steps: Step 1.PrintManager database installation Step. Procedure Step 3. PRINTManager Web Site Installation Step. PrintManager Print Service Installation Step 4. Registration is mainly in "Step I.PrintManager Database Installation". Question 1: The PrintManager database is required to be installed on a machine with SQL Server, so you have to install SQL Server first. When installing SQL Server2000, the system pops up a warning message box and displays "The previous program installation has been created on the installation computer. The computer must be restarted before running the installer!". The problem remains after reboot. So on Google Search: The most article is "a SQL Server 2000 installation adventure", but it does not know the cloud, the article does not find the problem; continue to search, finally find the answer, delete hkey_local_machine / system / currentControlSet / Control / Session Manager / PendingFileerenameOperations.
Direct causes of problems involve an old problem --- psdriver, see Appendix.
Question 2: After installing SQL Server 2000, continue to install the PrintManager database, prompt error "[DBNETLIB] [Connection ()).】 SQL Server Does NOT EXISTS OR Access Denied." Check the PrintManagerDe document, originally PrintManager's SASS The user must set the password, so they have to reload SQL Server. Because I just want to see how the PrintManager works, it is not important to register or not. However, with Softice, the registration protection of PrintManager does not seem to be very complicated, and you can try it when you have time. Appendix: Psdriver's old problem
PSDriver is a long time. Simply put, PSDriver is under Window2000, create a virtual printer, other Application can easily generate a PS file via this printer, plus the Acrobat DistillR, can generate PDF. Now because the Print Manager is dragged again, although it is only a small problem involved. PSDriver is to call AddprinterDriver to install the printer.
AddprinterDriver caller only needs to copy the relevant driver to the directory:% system% / spool / drivers / w32x86
When you call AddPrinterDriver, you will copy these files to your directory:% system% / spool / drivers / w32x86 / 3
Specific to PPD: When installing, the system copies the PPD file to "% system% / system32 / spool / drivers / w32x86 / 3" and generates a BPD file. When the installation is repeated, the system decides whether to update the PPD according to the modification date of the PPD file. If the PPD is new, replace the old PPD, that is, copy it again; otherwise, do nothing!
The problem now is that if the PPD file that is starting to start is read-only, the system is just a copy file, and the file attribute will not change. When updating the PPD, because the PPD under "% system% / system32 / spool / drivers / w32x86 / 3" is read-only, the system copy will fail! ! ! Thus, the system will modify the registry, and write a key value in: hkey_local_machine / system / currentcontrolset / control / session manager / down: PendingFileerenameOperations = "/ ?? / c: / Winnt / System32 / Spool / Drivers / W32x86 / 3 / New / test.ppd / ?? / c: /winnt/system32/spool/drivers/w32x86/3/test.ppd / ?? / c: / Winnt / System32 / Spool / Drivers / W32x86 / 3 / OLD / TEST. PPD / ?? / c: / winnt / system32 / spool / drivers / w32x86 / 3 / OLD "The last tail is gone, it can be seen that the previous section indicates when the system is restarted, use C: / Winnt / System32 / Spool /Drivers/w32x86/3/new/test.ppd overrides C: /Winnt/System32/spool/Drivers/w32x86/3/test.ppd to achieve the purpose of updating the PPD. Note: This is a typical installation-driven processing strategy. Details can refer to the API: Bool MovefileEx (LPCTSTSTR LPEXILELENAME, LPCTSTSTR LPNEWFILENAME, DWORD DWFLAGS); where parameter dwflags can be: movefile_delay_until_reboot but in the target file is readable, this is not true. The end of the code is gone, unclear. After restarting the machine, the actual situation is: pendingfilerenameOperations = "/?/c:/winnt/system32/spool/drivers/w32x86/3/old/test.ppd"
Obviously this is not a grammar, and can only be handled by hand, it is existence, resulting in the above-mentioned SQL Server installation error! ! ! In addition, this problem has already been processed, that is, when installation, remove the read-only attribute of the PPD. The reason why it is now just because the garbage in the registration is not clean.
