Quantcast
Channel: Primavera Online Interaction » WARNING
Viewing all articles
Browse latest Browse all 61

prim25041:Unable to Print to a non-default network printer from Windows 2000

$
0
0
Solution ID: prim25041
Unable to Print to a non-default network printer from Windows 2000
Status: Reviewed
Version(s): 4.0, 4.1



Fact: Windows 2000
Problem: Unable to print to a non-default network printer from Windows 2000.
Problem: Windows closes Project Management when trying to print to a non-default network printer from Windows 2000.
Problem: The Event Viewer produces an Error or Warning in the Application log containing one of the following messages, after failing to print:

“Security policies are propagated with warning. 0x4b8: An extended error has occurred. …….. Event ID: 1202″.


- “Windows cannot load your profile file. …….. Contact your administrator …….. DETAILS – Access refused”.


To examine the Error / Warning file in the Event Viewer:


1) Generate the error by trying to print from Project Management to the non-default network printer.


2) Go to ‘Start’ then ‘Run’ and enter  %SystemRoot%\system32\eventvwr.msc /s  and click on ‘OK’.


3) This will open the ‘Event Viewer’. Double-click on ‘Application’ on the left-hand side, and view the entries listed on the right-hand side.


4) Look for most recent entry(ies), verifying date & time. Locate Error message entry (with red symbol) or Warning message (yellow symbol).


5) Double-click the entry, and view the Event information and Description field. 

Cause: The PC’s local group policy has become corrupt.
Fix: The Microsoft knowledgebase contains an article at  http://support.microsoft.com/kb/278316 which addresses this issue and provides the solution below:

“RESOLUTION
To resolve this issue, use the procedure described in this section to re-create the local Group Policy file.

Note When you use the following procedure, your computer is returned to the original installation state where the Local Security Policy is not defined.
(You may have to start your computer in Safe mode to rename or move files. For additional information about how to dothis, see Windows 2000 Help.)

1. Open the C:\%SystemRoot%\Security folder, create a new folder, and then name it “OldSecurity”.
2. Move all of the files ending in .log from the C:\%SystemRoot%\Security folder to the OldSecurity folder.
3. Find the Secedit.sdb file in the C:\%SystemRoot%\Security\Database folder, and then rename this file to “Secedit.old”.
4. Click Start, click Run, type mmc, and then click OK.
5. Click Console, click Add/Remove Snap-in, and then add the Security and Configuration snap-in.
6. Right-click Security and Configuration and Analysis, and then click Open Database.
7. Browse to the C:\%SystemRoot%\Security\Database folder, type Secedit.sdb in the File name box, and then click Open.
8. When you are prompted to import a template, click Setup Security.inf, and then click Open.

Note:  If you receive an “Access denied” message, you can safely ignore it.



In a corporate environment the IT department should be consulted.  


DISCLAIMER: The solutions provided are for the convenience of the User and are not provided under warranty or supported as part of Primavera System Inc.’s Maintenance and Support Program. Users who implement these solutions do so at their own risk. Primavera Systems Inc. will not be responsible for any problems or data loss resulting from the following of such instructions.  

Fix: An alternative Solution is as follows:

1) Save all work and close all open programs.
2) Go to  C:\%SystemRoot%\System  on the client PC.
3) Create a new folder called ‘Old Security’ and move all ‘Edb*.*’ and ‘Res*.*’ files into it.
4) Reboot the PC and log back into Windows. Behind the scenes the policy files will be recreated with new up-to-date versions.
5) Launch Project Management and try printing to the printer.

DISCLAIMER: The solutions provided are for the convenience of the User and are not provided under warranty or supported as part of Primavera System Inc.’s Maintenance and Support Program. Users who implement these solutions do so at their own risk. Primavera Systems Inc. will not be responsible for any problems or data loss resulting from the following of such instructions.


Viewing all articles
Browse latest Browse all 61

Trending Articles