It all started with this error when I tried to log into VCenter Server:

“vSphere Client could not connect to ‘{machine name}’ A connection failure occurred (Unable to connect to the remote server)”

After investigating this, I determined the VMware VirtualCenter Server Service was not running. However, trying to start it produced an Event 7000, Service Control Manager “The VMware VirtualCenter Server service failed to start due to the following error: The service did not respond to the start or control request in a timely fashion.”

After contacting VMware support, their suggestion was to uninstall and reinstall. Which frankly, is their answer to 90% of any issues – very frustrating for what has to be one of the most expensive OS support contracts out there. While this didn’t directly fix the problem, uninstalling and reinstalling produced this error:

The following port numbers are either invalid or already in use.
VMware VirtualCenter HTTPS Port: 443

As it turned out, Routing and Remote Services now employs SSTP protocol. That feature produces a listener on 80 and/or 443. I’m not sure if this was introduced when we did the Service Pack or when. But nevertheless, selecting RRAS>PORTS>WAN Miniport (SSTP) Configure, and disabling “Remote access connections (inbound only)”

For reference, here is the knowledge bulletin I eventually used to troubleshoot:
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1003926

There were a number of posts including David Klein’s and Waxtadpoles regarding SQL 2005 and the “TypeGuessRows” setting in the registry.  Their suggestion was to set the value to 0 (zero), in order to force SQL to parse all rows in the excel sheet, not the first 8 (http://support.microsoft.com/kb/189897)

This was ultimately the solution, but not as stated. For us, possibly because we were running 64bit or differences in SQL 2008/Server 2008, the registry entry was not where either the Microsoft Bulletin or the two posts above stated. By searching the registry for this Dword Value we found several other instances of it at:

• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Jet\4.0\Engines\Excel
• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\Jet\4.0\Engines\Lotus

 

After making the change to “0″, our error was resolved. Thanks to both the posters above, and Philip Michael’s persistence.

UPDATED

It turns out this is indeed related to the 64bit OS. Apparently the Jet Engine runs in “Windows On Windows 64″ 32 bit run-time. Here is a little information on WoW64. And David Jennaway has some more information on SQL 64bit, Excel providers and DLLs in this article: The Registry settings for the 32 bit OLEDB provider for Excel have moved.

I have been using my Sony HDR-SR12 camcorder for several years now (here is a link to that post). As much as I love this camcorder and storing straight to a hard drive, AVCHD footage presented some workflow challenges with my editing system – Final Cut Pro.  And since Sony’s archiving software is Windows only and I work on a MAC, archiving was no picnic either. But the solution I’m currently using is achieving good results for both, so I thought I would share my process for anyone else facing these issues.

In general encoding algorithmns are design to balance the need for real-time dataflow against file compression.  In AVCHD, the files are encoded to maximize files size and processing of a very narrow processing set.  Transcoding the footage for non-linear editing (i.e. Apple ProRes, etc.) offloads the need for processing by decompressing the files for fast retrieveal.  While this retains the quality, it significantly increases the file size (4-10 times).  So, my main objective was to develop a workflow that would offload footage from the cameras internal drive for permanent storage without quality loss or increasing the file size, while still allowing for easy loading of any footage into Final Cut projects for editing.

For workflow, I use Final Cut Pro’s “Log and Transfer” function (not “Log and Capture”) to transcode the files to my desired editing format.  The trick was to copy the data off the camera to a structure that Final Cut Pro would still read within the Log and Transfer function.  To do this, I used Retrospect to clone/copy the internal drive of the Sony Camera.  Using Restrospect I was also able to syncronize the the cameras drive with a folder stored on an external firewire drive.  This feature allowed me to just copy over files that had been added since the last compare.  It should be noted, I’m not making a backup of the drive…but a copy.  The AVCHD file structure must remain intact for this to work.

So, here is my workflow was my solution:

1. After a shoot, I mount the camera to the MAC via the built in USB connect function.
2. Run a Retrospect script that syncs the cameras drive to a matching folder/
3. Mount the matching folder in Final Cut’s LOG & TRANSFER
4. Transcode to ProRes422 and edit.

Once I’ve completed offloading the storage of the camera, I can reformat the Camera’s drive for the next shoot.  Archiving the camera’s footage can be done simply by any Data Backup routine.

Enter the HDR-SR series.  I won’t cover the specs – cause it’s been done…but this verson is a 120 Gig internal hard drive.  This new camera had everything I was intrested in except, a 20x optical zoom and HDV versus AVCHD.  The 20x just isn’t happening.  I believe due to the sensor size and format, it’s just too expensive to produce this – for now.   Nevertheless, the 12x smaller Carl Zeiss lense is very good.

Waiting for HDV was ignorance on my part.  I’m stunned how good AVCHD format looks.  My first playback straight out of the camera (not compressed to DVD), left me speechless.  And AVCHD’s storage capabaility is remarkable.  I’ve been using the camcorder for personal footage for nearly six months.  While I’ve downloaded everything, I’ve not erased anything from the camera’s internal hard drive.  And it still has nearly 10 hours of recording capacity left.  Seriously, this camera will pay for itself inside of two years through saved tape cost.  Given this, I think the AVCHD format is more than capable for consumer and semi-pro use.  It seems as though more and more apps are becoming compatible with it as well.  There is something about the concept of compression (and throwing away data) that offends the pro in me.   But AVCHD does a nice job.  Afterall MP3 sounds good at 190kbps and above.

If you have an Intel Mac, Final Cut Pro 6 can read the files straight off the camera.  It must convert to ProRes to edit.   You CAN use the motion picture browser that comes with it for maintaining the oringal files.  This is windows only – I run mine through a virtural Vista instance (Parallels Windows for the MAC).  This software allows for quick burn to DVD and the facial recognition feature. 

ONE-BUTTON DVD BURN
This is cool concept, but the conversion from AVCHD to DVD (which requires MPG2 format) is less than speedy.  Easy, yes!  Quick, no!  A typical DVD might take 1 to 2 hours to convert and burn.

FACIAL RECOGITION INDEXING
This feature was an unexpected suprise.  When this is turned on, the camera idenifies faces while shooting.  It then provides a list of faces as indexes for each clip.  While you are viewing it in browser mode, you can browse through faces, not just locations or dates.  At first glance, this seemed to be somewhat silly.  But it works well and is actually quite useful.

10 MEGA-PIXEL STILLS
Keep in mind, I love my Canon 40D.  Seriously, I love SLRs, high dollar lenses, and controlling depth of field.  I’m very excited about Canon’s new 5DmarkII - which shoots video in HD format.  With that said, having a quality camera built into a camcorder, is extremly convient and sound idea as well.  I would suspect for the non-discriminating photographer, this camera is more than enough. And even for the more discriminating, the ability to grab a still while shooting (even if the quality isn’t pro) is very cool…and inviting.

LOW LIGHT
Two steps forward, one step backward!  This might be Sony’s worst low-light performer in years.  It doesn’t get a failing grade here, just a low one.  Don’t expect to shoot stunning footage in a dimily lit room or outdoors at night.  It does have the “night vision” mode – but I’m referring to color shooting.

CONCLUSION
I would highly recommend this camcorder for personal use to anyone, even pros.  And given the smaller hard drive versions are farily cheap…the savings realized from not having to purchase blank tapes allows anyone to shoot in High Def for little expense.  Do it.  Seriously, explain to your wife how much savings you’ll realize, and do it!

After performing a clean install of Microsoft Office 2008, Entourage began to give me the following error:

“Unable to establish a secure connection to servername because the correct root certificate is not installed.”

I followed various post regarding installing our Exchange Server’s certificate.   After installing this, I began to receive this error:

“Unable to establish a secure connection to servername because the server name or IP address does not match the name or IP address on the server’s certificate. If you continue, the information you view and send will be encrypted, but will not be secure.”

Clicking okay, will allow Entourage to connect – but the error will return and is annoying.

However, the error continued.  After much experimenting, I was able to resolve the issue, but the error is so ambigous, that it can be caused from several different misconfigurations.  

If you desire to use SSL, your server must have a valid certificate.  If the certificate is through a public provider, I don’t believe you will not need to install any certificates at all.  If your system admin has provided you a private certificate you will need to install it into Keychain Access.  Install it to system chain if all users on the computer will need it, or to login chain if only you need it.  There are several documents on the web for doing this.  However, if you have installed the certificate, and you still recieve this error, read on.

RESOLUTION
Several blogs have discussed the new AutoDiscovery Service issue within Exchange 2007, however we use Exchange 2003.  

The problem with my Entourage was being caused by our domain structure.  The hardware firewall passes mail ports to the Exchange server.  The Exchange server has a public accessible Security Certificate through GO DADDY.  

However, the LDAP port is forwarded to the domain controller running the Active Directory.  Because in our setup, we don’t publish a separate internet host record the LDAP (for example ldap.mydomain.com), there is no way for the machine name listed in the certificate for mail.mydomain.com to match 2 different machines (the Exchange server and LDAP server).  Therefore the error is valid, and not a Microsoft bug in Office/Entourage.

Since the LDAP lookup is what was causing the error, the error would not popup until a lookup function was needed.  Because of this, it was possible to have Entourage sessions without getting this dialog.  In order to prevent this error, do not require LDAP functions to connect sercurely.  

1. Under the ENTOURAGE menu select ACCOUNT SETTINGS
2. Double click your Exchange Account.
3. Select the Advanced Tab under the EDIT ACCOUNT dialog.
4. Ensure “This LDAP server requires a secure connection (SSL)” is NOT selected.

All mail activity is still handled through an SSL secure connection to the Exchange server.  Only directory lookup function is changed.  Some organizations allow non-secure LDAP access, if yours does not and you are using a separate server for LDAP functions.  Then it will be necessary to obtain a certificate that has a matching internet host record to machine name.   You can also ignore the dialog box safely – though it is very inconvenient.

You can also use this procedure to ensure the error is being caused by LDAP functions.

CONCLUSION
At the very least, I can reassure you that OSX 10.5.6 and Microsoft Office for the Mac (Entourage) 12.1.5 do work together without error.  Microsoft has fixed whatever error/bug was involved, so don’t give up trying to resolve it.  And definitely don’t wait in vain for Microsoft’s next update to do so.

Then…BAM!

It comes and goes like a lit rocket…and we’re Wile E. Coyote standing in the exhaust wondering what happened.  And just like Wile E., the smoke clears revealing the ACME truck that is about to hit us smack in the face.  Only in this case, it is the 5-0 Tennessee Titans.  Remember the Titans?

They have the best record in the NFL right now.  They’re on an eight game winning streak (regular season).  And they’re just coming off a week of rest too!

I can’t watch!