Adobe PDF error "The Adobe Acrobat/Reader that is running can not be used to view PDF files in a Web Browser"

When using Adobe PDF to view PDF file in browser, you may encounter the following error:

"The Adobe Acrobat/Reader that is running can not be used to view PDF files in a Web Browser.
Please exit Adobe Acrobat/Reader and exit your Web Browser and try again."

I have visited tons of forums but am yet to find a concrete solution. However the below solution can also help.

Solution 1:

1. Click Start->Run->regedit
2. Browse to HKEY_CLASSES_ROOT\Software
3. Right click on Software, Select New->Key
4. Enter Adobe and press enter
5. Right click on Adobe->New->Key
6. Type Acrobat and press enter
7. Right click on Acrobat->New->Key
8. Type Exe and press enter
9. Click on Exe and double click on (Default) & enter the following key (include the quotations):
"C:\Program Files\Adobe\Reader 9.0\Reader\AcroRd32.exe"
10. Click OK

This solution helped the first time I encountered the problem. However when I repaired Adobe to resolve another problem with printing, this issue resurfaced & the solution given above has not helped.

Couldn't access Yahoo! Zimbra Desktop serve

If you have used Yahoo Zimbra desktop & have received the following error, then read on to get the solution:

"Couldn't access Yahoo! Zimbra Desktop server. If issue persists after reinstall, please check logs for errors and report to http://www.zimbra.com/forums/zimbra-desktop."

If you not know Yahoo zimbra yet, you should download this fantastic equivalent to Outlook. It configures with all your email servers including Gmail, hotmail & yahoo & Its fast.

The error occurs due to two reasons:

1. Space in directory name: It's a Windows registry issue where the path name of the service needs quotations. (The Yahoo zimbra service)

&

2. The Yahoo desktop service is disabled.

Solution:

1. Registry path correction:

1. Click Start, and then click Run.
2. In the Open box, type regedit, and then click OK.
3. Locate, HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Yahoo! Zimbra Desktop Service.
4. In the right pane, double-click ImagePath.
5. In the Value data box, add quotation marks around the complete path of the executable file for the service.
6. For example, if the path of the MyService service is C:\Program Files\MyProgram\MyService.exe, change the entry in the Value data box for the MyService service to the following "C:\Programs Files\Zimbra\zdesktop\zdesktop.exe""Click OK, and then quit Registry Editor. (This is based on asuumption that Yahoo zimbra has been installed in default location. If you have changed the install directory, change the path accordingly.

2. Second thing to check for is whether the yahoo zimbra service is enabled.

1. Click Start, and then click Run.
2. In the Open box, type services.msc, and then click OK.
3. In the services box, locate Yahoo! Zimbra Desktop Service
4. Right click on the service & click properties
5. In startup type box, select manual if you prefer to use the service only when required or automatic if you are going to be allowing the desktop client to run in the background (Just like outlook)

That should take care of the error.

How to Enable Remote errors on SQL reporting services.

If you have been using SQL reporting services, you may have encountered few errors which just become difficult to resolve. In such cases, its advisable to enable the remote errors on your reporing services which helps you to understand the inner exceptions.

The remote errors can be enabled on the reporting services in two ways:

1. Using the SQL Server Management Studio

Start Management Studio and connect to a report server instance.
Right-click the report server node, and select Properties.
Click Advanced to open the properties page.
In EnableRemoteErrors, select True.
Click OK.

2. Using a script to enable remote errors:

a. Create a text file and copy the following script into the file.

Public Sub Main()
Dim P As New [Property]()
P.Name = "EnableRemoteErrors"
P.Value = True
Dim Properties(0) As [Property]
Properties(0) = P
Try
rs.SetSystemProperties(Properties)
Console.WriteLine("Remote errors enabled.")
Catch SE As SoapException
Console.WriteLine(SE.Detail.OuterXml)
End Try
End Sub

b. Save the file as .rss in your local folder.
c. Open a command prompt window
d. Either Navigate to the directory that contains the .rss file you just created or use the absolute file location on the command prompt. Type the following command line, replacing servername with the actual name of your server:

rs -i EnableRemoteErrors.rss -s http://servername/ReportServer

3. Enabling the remote errors by updating the database.

a. Update ReportServer database Configuration table for EnableRemoteErrors

Update the ConfigurationInfo table in the ReportServer database for configuration record named "EnableRemoteErrors". The default value for EnableRemoteErrors property in the ConfigurationInfo database table is "False". Update the value to true by running a simple update statement.

You may not be successful to see the changes made on the ConfigurationInfo table on the Reporting Services application, if the application is being used intensely.

If everything goes fine, you should see a message "remote error enabled."

Note: Do ensure that your server is accessible from the location / machine you run the script from. If you have direct access to the server, run the script on the server.

Enabling the remote errors should give you detailed information on all the issues you encounter on your reporting services.

Unable to start debugging on the web server. Debugging failed because integrated Windows authentication is not enabled

"Unable to start debugging on the web server. Debugging failed because integrated Windows authentication is not enabled" error occurs when you try try to debug the application in Microsoft Visual Studio 2005 in Windows Vista Home Basic or in Windows Vista Home Premium using Internet Information Services (IIS) 7.0.

This problem occurs because Windows Vista Home Basic and Windows Vista Home Premium do not contain the Windows Authentication module for IIS. When the client tries to automatically attach the debugger in an ASP.NET 2.0 application, the client sends a HTTP request that contains the DEBUG verb. This HTTP request is used to verify that the process of the application is running and to select the correct process to attach. This HTTP request must be authenticated by using Windows Authentication. However, Windows Vista Home Basic and Windows Vista Home Premium do not contain the Windows Authentication module for IIS. Therefore, the problem occurs.

A supported hotfix is available from Microsoft. Apply this hotfix only to systems that are experiencing this specific problem.

To download this hotfix from the MSDN Code Gallery, visit the following Microsoft Web site:

http://code.msdn.microsoft.com/KB937523

You must have Visual Studio 2005 Service Pack 1 (SP1) installed to apply this hotfix.

Filezilla ECONNREFUSED Connection refused by server

If you are a Filezilla user for all your FTP needs then you may have faced this error. When you try to connect to your web host using Filezilla, you get this error "ECONNREFUSED - Connection refused by server". When I first got this error, I ran around from my ISP to my web host to get a solution. All the suggestions from my ISP, my web host and filezilla failed.

I just decided to take a step back to figure out when & how this problem had started. I had recently updated my filezilla and thought probably this was a bug with the new version. I tried installing the previous version but ended up with the same error. The only other thing I had done was to upgrade my zonealarm. Then it stuck me, that when my zone alarm was being upgraded, the firewall was shut down for some time. Thats when the windows firewall has automatically started without my knowledge.

Even after zone alarm had been upgraded, the windows firewall was still on. Effectively I had two firewalls running on my machine. Even with the Filezilla executable listed in the exceptions list for windows firewall, it was still being blocked.

I turned off my windows firewall and voila, filezilla was immediately able to connect. So the real culprit behind my entire ordeal was windows firewall.

I was also surprised to see incorrect error by Filezilla. If Filezilla had reported that it was being blocked by a firewall, it would have saved me a lot time. Instead the error was "Connection refused by server".

Hope this helps you to resolve your problem as well.

When you install WinMySQLAdmin with MySQL and start WinMySQLAdmin you end with this error. Every time you start the control application you get a warning which is repeated until WinMySQLAdmin is shut down.

Access violation at address 10002593 in Module 'LIBMYSQL.dll'

Repeating the Error

Start WinMySQLAdmin with the xampp and you should get the error again.

Solution

1. Open WinMySQlAdmin
2. Click on the my.ini Setup tab
3. Change the following entries

user=root
password=password

to

user=
password=

Another simple solution is to locate my.ini in your windows directory and make the below changes:

user=root
password=password

to

user=root
password=


This should resolve the error. If not, let me know and I will try my best to get you another solution. :)

Illegal Interview questions

Here's a list of Illegal interview questions I read about on TechRepublic.
#1: Where were you born?
#2: What is your native language?
#3: Are you married?
#4: Do you have children?
#5: Do you plan to get pregnant?
#6: How old are you?
#7: Do you observe Yom Kippur?
#8: Do you have a disability or chronic illness?
#9: Are you in the National Guard?
#10: Do you smoke or use alcohol?
Read full details on TechRepublic

Could not create Windows user token from the credentials specified in the config file

Error: "Could not create Windows user token from the credentials specified in the config file. Error from the operating system 'Logon failure: unknown user... "

This error usually is encountered when either the username / password is not valid for the selected user OR the selected user does not have necessary privilege.

You can add the privileges by following the below steps:

Run - Control Panel, Administrative Tools, Local Security Policy

Choose - Local Policies, User Rights Assignment from the tree

"Act as part of OS" should be the second entry on the right hand pane

How to use the ASP.NET utility to encrypt credentials and session state connection strings

In your Asp.net applications, you might want to encrypt the impersonation userid & password. You can do this by using the tool provided by Microsoft and encrypt the userName and password attributes to be used with the section.

1. Download aspnet_setreg.exe from this location:
http://download.microsoft.com/download/2/9/8/29829651-e0f0-412e-92d0-e79da46fd7a5/aspnet_setreg.exe

2. ideally you can create a .bet file with the following command:
aspnet_setreg.exe -k:SOFTWARE\SECURE_APP\identity -u:"yourdomainname\username" -p:"password"

3. Then add an entry in your web.config to use this username & password for impersonation.



4. You need to also add necessary permissions so that the process can read this registry settings. else you will end up with the following error"

"Error reading configuration information from the registry"

You can read more on adding permission on the post "Error reading configuration information from the registry"

5. Restart IIS using iisreset on the command prompt.

Error reading configuration information from the registry

You will encounter this error if you are trying to read from the registry. This error specifies that some thing is wrong with the process account when reading the identity information from the registry.

Try the below steps to resolve the issue:

1. Open Regedt32.exe
2. Navigate to HKLM\SOFTWARE\SECURE_APP\identity (Replace SECURE_APP with the app name that you have entered from the aspnet_setreg.exe
3. Right click on key identity and select permissions



4. On the add permissions, click ADD and enter "NETWORK SERVICE"






5. Select Read Permission
6. If you are using Windows 2000 / IIS 5, you will need to add permission to MACHINE\ASPNET
7. This should resolve the access error.