"Document cannot be printed" is fixed by installing Adobe Reader 9

Today I tried to print my PDF document in the office, it didn’t work and it showed “Document cannot be printed”. I even tried print as images and it still didn’t work.

I found it should be an issue of Adobe Reader 8. Therefore, I installed Adobe Reader 9 directly. After installing Adobe Reader 9 and restarting my laptop, I printed my PDF document successfully.

Next time if you see the error message -Document cannot be printed, just install Adobe Reader 9. It should work.

IE 8: Can’t copy words from MS Word to Blogger

Today I downloaded IE 8 in my PC with Windows XP SP3 to surf some websites. One interesting fact I found today was that if I wrote some keywords in .docx or .txt and wanted to copy them to my blog, I couldn't paste them to blogspot on IE 8 because "paste" is disabled when I right clicked the mouse. Crtl+ v is not working , either.

If I went to Tools, Compatibility View Settings, and checked Display all websites in compatibility view, I could paste the words from .txt or .docx to BlogSpot on IE 8.

Uploading the images using IE 8 makes UI look so ugly in blogger.

Do you think it is an interesting issue?

Windows Update failed (0x80072733): Got the virus

Today when I did the windows update, it didn’t work. It also showed the following message and the error code -0x80072733

Windows Update has encountered an error and cannot display the requested page.

When I tried to google some information, the link redirected to windowsclick.com. At that time I knew I got the virus. Therefore, I downloaded Trojan Remover trial version online to give it a try to see if I could kill the virus.

The tool scanned my laptop immediately and found out the virus. I needed to restart my laptop. During the reboot, the blue screen showed up and it checked the file consistency. After 2 minutes, I could login to my laptop.

When I viewed my log file, I found 6 files were deleted as follows

C:\WINDOWS\system32\UACsehbippe.dll - deleted
C:\WINDOWS\system32\UACntpvauln.dat - deleted
C:\WINDOWS\system32\UACsrsudnth.dll - deleted
C:\WINDOWS\system32\UACklyfvkbm.dll - deleted
C:\WINDOWS\system32\UAClwxvmtal.dll - deleted
C:\WINDOWS\system32\UACnmevpjie.log - deleted

After that, I could do the windows update again and everything seems normal as usual.

Next time if you can’t do the windows update and get the error code, just try this Trojan Remover free software. Hope your issue will be disappeared.

To upload the file fails in VSTS 2008 web test ?

If you use VSTS 2008 web test to upload the file, after you record and run the test, your web test fails. That's because when you upload the file , VSTS web test doesn't know where your file is. After you record the test, you need to manually modify your web Request.

If your file path is c:\test.txt, VSTS only knows the file name, test.txt, not the file path: c:\test.txt.

You just change the file path and run the test again. Your test will pass.

VSTS 2008 Web Test and Windows Authentication Login Popup

You are a user (Domain A\Ray) in domain A. If you use VSTS 2008 web test to test the URL in domain B, IE 7 will have the Windows Authentication login popup to remind you of entering the username (Domain B\Ray) and password in domain B. You will see the login popup as follows:

The server XXX.XXX.com at XXX.XXX.com requires a username and password.

After you enter your username and password, the web test moves on and finally makes your test fail. When you see the test result, you find one of the requests is: You are not authorized to view this page.

After you generate the codes and find that VSTS 2008 doesn’t record the username and password you just entered. How can you handle this situation?

You need to add the following source codes.

this.UserName = "abc\raylin";
this.Password = “12345”;

After you add them and if the test case still fails, please check if you install VSTS 2008 SP1. You might also need to add the proxy in your source codes too. You will make your test case pass.

VSTS 2008 Web test-The remote name could not be resolved

If you use VSTS 2008 to do the web test, you might have one issue- the remote name could not be resolved. It is hard to say what makes your web test case failed.

When I have this issue, I always think it is the proxy issue. When I add the following source code, it works all the time.

this.Proxy = “XXX.XXX.com";

VSTS 2008 web test recorder bar does not show up

During this month, I have used VSTS 2008 web test to create more than 200 automated tests in my current Microsoft Project without any problem. The test automation runs very smoothly every day.

Today I used my personal PC in my house to create one simple automated test. Unluckily, the recorder bar didn’t show up. My PC environment is as follows:

Windows XP SP3, IE 7, VSTS 2008 SP1.

I finally found that my Microsoft Web Test Recorder was disabled. Only what I needed to do was launch IE 7, go to Internet Options/Programs/Manage Add-ons and enable Microsoft Web Test Recorder.

After that, the issue was fixed. I could create the simple web test successfully.

VSTS 2008 could not load file or assembly Interop.SHDocVw

Today I downloaded WatiN (Web application test in .Net) tools and wanted to run the web test using Visual Studio .Net 2008. I got the following error:

Could not load file or assembly 'Interop.SHDocVw, Version=1.1.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

If you see this in the future, it is easy to fix it. You can just go to C:\Windows\System32 and copy shdocvw.dll to the bin directory of your current project.

Open your Visual Studio project, add shdocvw.dll in your references and run the test again. The problem will be disappeared.

Always install SQL Server 2008 RTM first before you install Visual Studio 2008

If you have Visual Studio 2008 and Visual Studio 2008 SP1 Beta on your PC, and then you want to install SQL Server 2008 RTM, you might have the following error.

A previous release of Microsoft Visual Studio 2008 is installed on this computer. Upgrade Microsoft Visual Studio 2008 to the SP1 before installing SQL Server 2008.
(see : http://support.microsoft.com/kb/956139)

That’s because you have Visual Studio 2008 SP1 Beta on your PC, not Visual Studio 2008 SP1. If you don’t have SP1, you can’t install it successfully. Today is August 9, and we need to wait until Microsoft releases Visual Studio 2008 SP1.

If you really want to install SQL Server 2008 RTM now, you need to uninstall Visual Studio 2008 and SP1 , install SQL Server 2008 RTM and then reinstall Visual Studio 2008. When Visual Studio 2008 SP1 is released, you can install it later.

The lesson I learn :
Always install SQL Server 2008 RTM first before you install Visual Studio 2008 +SP1

Microsoft doesn’t support upgrading from SQL Server 2008 RC0 to SQL Server 2008 RTM

If you have SQL Server 2008 RC0 and Visual Studio 2008 SP1 Beta on your PC and then you want to upgrade to SQL Server 2008 RTM, You may feel disappointed.

At this moment, Microsoft doesn’t support upgrading from SQL Server 2008 RC0 to SQL Server 2008 RTM.

You need to uninstall SQL Server 2008 Beta and Visual Studio 2008 SP1 Beta first and then install SQL Server 2008 RTM.

Will it change in the future??