Friday, October 15, 2010

Windows 7 clients may not be able to print to Windows Server 2003 print server

Microsoft has announced a compatibility problem between Window 7 PC and Windows Server 2003. As per KBA2269469, print job fails when print is fired from a Window 7 PC to a network printer connected to Windows Server 2003.

The print job fails with the following error message:

Event ID: 372
Level: Error
Description:
The document , owned by , failed to print on printer . Try to print the
document again, or restart the print spooler.
Data type: . Size of the spool file in bytes: . Number of bytes
printed: 0. Total number of pages in the document: 1. Number of pages printed: 0.
Client computer: . Win32 error code returned by the print processor: 1722.
The RPC server is unavailable.

The file needed to be included in the windows 7 client's registry.

Windows Registry Editor Version 5.00

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows NT\Printers]
"EnabledProtocols"=dword:00000006

Monday, June 29, 2009

Troubleshooting Exchange database

Running eseutil /mh "pathname\database.edb"

With this command, it is used to check the status of the database. When performing the command the database must be dismounted.
This will check the status of the database and the last committed log file.
Take note of the state:
State: Clean Shutdown' (or Dirty Shutdown)

If clean up status is clean shutdown, then we are able to delete the log files in in the log folder. But leave the last log file ard, then just start to mount the database again.

If inconsistent , then run
isinteg -pri -fix -test alltests

_______________________________________________

Running Eseutil /d "pathname\database.edb"

Eseutil / d is probably the commonest and the safest of eseutil's switches. This switch is to defrag the database.

To prepare for eseutil /d, first dismount the store.There is no need to stop the Information Store service, just dismount the individual stores in the Exchange System Manager.

Next, make sure that you have plenty of free disk space, at least as much as the priv.edb or store.edb that you wish to defrag.

Navigate in the cmd window to the \exchsrver\bin folder and issue a command such as this:

Example: eseutil /d "e:\exchsrvr\mdbdata\priv1.edb" (Or other path to your store)

If you really do not have enough free space try the Eseutil /d /t "f:\temp.edb". Where the f drive has enough free space. Always remember to remount the store once the defrag has finished.

** Never run repair switch /p unless last resort as it can destroy the storage database and you might have to get back from backup tape.


_________________________________

Some sites to assist in using the command :

http://www.computerperformance.co.uk/exchange2003/exchange2003_eseutil.htm

http://support.microsoft.com/kb/219419

http://support.microsoft.com/kb/192185


Friday, June 5, 2009

Solving Microsoft Exchange offline address book 0X8004010F

Working with the offline address book is a challenge.

After much struggle , I have some encounter of this error.

Above is how to solve it.
______________
1.Troubleshooting by:

- Download the above file OABInteg.exe @ http://code.msdn.microsoft.com/oabinteg/Release/ProjectReleases.aspx?ReleaseId=726

- Then unzip in your PC c: drive. Then go to command prompt by going to Start>run>cmd

- Then You should go to c:\ by typing cd:\

- Uncheck the cache mode in the outlook

- Then copy the above command line : OABInteg /s:exchsrvname /t:oabfldcheck /v:2 /l

- Then you should be able to see a series of code.

- It will also create a file c:\OABInteg.txt

- Open the out look again and see if it replicate the oab file to your computer when click on download address book .

- Try for both cache mode and online mode.

- Read the log if possible for possible errors

- Look out for the biggest file size as appliance might block the transfering, antivirus might be another culprit.



Try to recreate another offline address book if possible , link to the first storage group, and enable the offline addressbook at the offlineaddressbook tab in exchange 2007.

Then try replication again.
This should solve our problem.

Tuesday, May 26, 2009

To force update offlineaddressbook (OAB) in exchange 2007

Using power shell:

get-offlineaddressbook update-offlineaddressbook

update-filedistributionservice %CAS server name%

From client side : you could download addressbook once again bt going to tool>download addressbook.

If not possible:
Close the outlook.
Try rename the *.oab file away in %userprofile%\Local settings\Application Data\Microsoft\outlook folder. Then open the outlook again.
Try redownload the addressbook again.

Sunday, January 4, 2009

USB cannot left double-clicked.

Lately, my USB thumbdrive was infected with a trojan virus. Most probably, the virus was written onto my thumbdrive from one public computers that I usually frequent.

As the Anti-virus software did a viral quarantine and deletion.

After deletion, the USB thumbdrive is unable to be “left-double-clicked”. When double-clicked, Windows will launch a windows saying some files cannot be found. It was that my Autorun.inf file (the file that is used to Autorun specified programs) has commands to launch certain programs on the thumbdrive. Apparently, the virus overwrites the old Autorun.inf to an infected one which launches the virus everytime the thumbdrive is placed into a PC. Thus, this is the solution that you should do if you are facing the same problem.


Do a virus scan on your thumbdrive. Next, backup your data (just to be safe) to a hard disk.

Later change your Autorun.inf by the following steps:

1. Go to tools -> folder options -> view tab: check show hidden files and folders and click OK.

2. Go to My Computer -> Right-click your thumbdrive -> explore.

3. In your Windows explorer, right click on the file on your thumbdrive with name "Autorun.inf" -> Choose "open with" -> select "notepad.exe "

4. Delete all the contents inside the file, and replace the contents with:



+++++++++++++++++++++++++++++++++++++++++++++

[autorun]
shell=Open

+++++++++++++++++++++++++++++++++++++++++++++