Archive

Archive for September, 2014

Installation hangs on “Windows Installer Coordinator”

September 25, 2014 16 comments

When installing IBM i Access for Windows on a Windows Server 2008 R2 Remote Desktop Services host it may hang on a dialog box that says, “Windows Installer Coordinator. Please wait while the application is preparing for the first use”.

windows_installer_coordinator

It’s weird that I’ve been using Windows Server 2008 R2 for so long & never ran into this issue.

Anyway, to resolve the issue open gpedit.msc (or create a GPO, whatever you prefer) . Browse to Computer Configuration\Administrative Templates\Windows Components\Remote Desktop Services\Remote Desktop Session Host\Application Compatibility. Set Turn off Windows Installer RDS Compatibility to Enabled. Now run the installer again.

Ref – http://support.microsoft.com/kb/2655192

Advertisements

Printer Keeps Going Offline

September 19, 2014 1 comment

A user reported that they had printed some documents but that they were not printing. Looking at the print server I saw that the printer was showing as Offline.

1 Offline

I was able to ping it as well as bring up the web interface. As a test I disabled SNMP checking for the printer’s port by doing the following:

  • Right click the printer & select Properties.
  • Select the Ports tab.
  • Select the printer’s port & click Configure Port.
  • Uncheck SNMP Status Enabled.
  • Click OK.

The moment I did that the printer went to a Ready status & the documents printed. I have two printer server that both have this printer configured. They were both experiencing the issue so I believe the issue to be with the print servers.

OK, perhaps the SNMP string got changed on the device. I ran an SNMP test (Paessler has a good free one http://www.paessler.com/tools/snmptester) but it check out good using the SNMP string configured on the printer’s port.

So when in doubt use ProcMon. First, I set the printer’s port back to using SNMP checking then fired off ProcMon on the printer server. Within a minute the printer switched from Ready to Offline. I stopped ProcMon & begun the artful task of sifting through the capture. I noticed a section where the print server starting sending SNMP requests to all the printers. I saw a response for all the other printers but none for the one in question. Note below all I saw were UDP Send.

2 no snmp response

So for some reason the printer is not responding (or not responding timely. I didn’t feel like doing a full on packet capture). So like everything else if it’s not working, reboot. Once the printer came back up it I started another ProcMon capture. This time I saw the SNMP requests & responses (UDP Send & UDP Receive).

3 with snmp responses

Sure I could have just left SNMP unchecked on the printer port but that wouldn’t have really resolved the issue; just masked it. Now if it continues to happen I may have to see if there is a newer firmware for the printer that resolves SNMP issues (or contact HP, ugh), but for now a printer reboot will do the trick. I also got to see a little more under-the-hood thanks to ProcMon.

Categories: Computers Tags: , ,

Quick Post: Screenshot Shortcuts for Surface Pro 3

September 16, 2014 Leave a comment
  1. Press & hold the Windows button until it vibrates. Then press & release the volume down button. The screen will dim for a moment. (You can also press them both at the same time if you time it right.)
  2. On the Type Cover press Fn+Windows+Space.

All screenshots are saved in Pictures>Screenshots.

Error Logging Into AutoLab vCenter Server

September 14, 2014 Leave a comment

When trying to log into the AutoLab vCenter server with the vi-admin account you get an error that says, “The vSphere Client could not connect to vc.lab.local. You do not have permission to login to the server: vc.lab.local”.

autolab_vcenter_error

Cause – The vi-admin account does not have Administrator permissions in vCenter.

Solution – Log in using the administrator@vsphere.local account with a password of VMware1.lab. That account info is missing from the AutoLab documentation. Once logged in you can assign the vi-admin account Administrator permissions to vCenter.

Categories: Computers Tags: , , ,

Errors Installing Windows Server 2012 R2 in a Virtual Machine

September 8, 2014 4 comments

Error #1

When installing Windows Server 2012 R2 on a VM (vSphere or Hyper-V) configured for EFI you may receive the following error when booting to the ISO. “Windows failed to start. A recent hardware or software change might be the cause. To fix the problem… File: \EFI\Microsoft\Boot\BCD. Status: 0xc000014c. Info: The boot Configuration Data for your PC is missing or contains errors.”

boot error with efi

 

Error #2

When loading the VMware Paravirtual SCSI driver you receive an error that says, “No new devices drivers were found. Make sure the installation media contains the correct drivers, and then click OK.”

error on clean install won't load driver

 

Error #3

The installation cannot load any SCSI driver & says, “A media driver your computer needs is missing.”

install error after changing from efi to bios

 

Error #4

“No device drivers were found. Make sure that the installation media contains the correct drivers, and then click OK.”

Capture

 

Cause – Corrupted ISO

Solution – Re-download the ISO & try again. In my experience ISOs can become corrupt if you pause them when downloading.

%d bloggers like this: