MikeH – Another Geek in Need…

Windows Live Messenger 2011 Continues to fail to login–Why? Error 8e5e0226

I have Messenger setup on my notebook – which is basically a Windows Server 2008 R2 Server.

So – I’m in the middle o doing any number of reconfigurations – and voila – I notice I cannot log into Messenger.

It’s a quick failure – with the above hex code.

I found the following link – THANK YOU – http://windowslivehelp.com/solution.aspx?solutionid=3494c948-55e4-448d-84bd-1e734e34a658

Here – you ensure that you can view hidden/system folders.

Navigate to your /Users/AppData/Local/Microsoft/Windows Live/contacts – and delete your email address folder name. No reason to reboot or anything – just do that – and all was great.

EventID 2803 from source MSSQL$MICROSOFT##SSEE cannot be found. Either the component that raises the even is not installed on your local computer or the installation is corrupt.

In this case, we had a CRM/ADFS installation that we backed out – and in doing so – the ADFS internal SQL Server instance (MSSQL$MICROSOFT##SSEE) was not removed.

This also happens with Windows SharePoint Service v3 or any Stand-Alone deployment of SharePoint. When you do a stand-alone deployment – you get this local, embedded edition of SQL Server.

Well, when you remove SharePoint, or in our case, we removed ADFS – it doesn’t remove this embedded edition database. Further, if you try to re-install – you’ll hit issues because this takes the installation down the default/stand-alone install – even if you elect a different deployment. So – we must manually remove this database.

Alternatively – you may be getting this error and attempting to resolve it – well, I hope this tidbit has helped you – the best thing to do is remove this instance – and re-install your initial stand-alone server component – in our case ADFS, in others WSS v3 or SharePoint Foundation / Stand-alone Deployment.

Here is the error we see:

Research shows this results from WSUS, ADFS, and WSSv3 (Windows SharePoint Services v3) being installed, or specifically installed as a stand-alone deployment – and once removed – the database is out there orphaned. Running the following command – 32bit or 64bit – run which ever is applicable (reference: http://technet.microsoft.com/en-us/library/cc708610(WS.10).aspx) will remove the database just fine:

1. Open a command shell (as Administrator)

2. Call msiexec with the correct key for the operating system platform.

   • On 32-bit platforms: msiexec /x {CEB5780F-1A70-44A9-850F-DE6C4F6AA8FB} callerid=ocsetup.exe
   • On 64-bit platforms: msiexec /x {BDD79957-5801-4A2D-B09E-852E7FA64D01} callerid=ocsetup.exe

Now you should be able to re-install, or install non-stand-alone – and all should be fine. HTH’s…

Office Professional Plus Setup 2010–Error–\ProPlusr.WW\OSETUP.DLL\ digital signature does not validate or is not present

Notice this error?

Check references like this one – http://social.technet.microsoft.com/Forums/en-CA/officesetupdeploy/thread/0fa444dd-8b5c-4a0c-8b89-617bbd0b8e53

As you already know – this seems endless – well, it’s not.

Are you installing on an older 32 bit notebook/desktop? As I am, perhaps?

Are you installing on a older 64 bit notebook / desktop? Perhaps?

As you may remember, earlier – there were downloads for the 32bit and the 64bit Professional Plus bits – each with a unique ID number

* en_office_professional_plus_2010_x86_51486.exe

* en_office_professional_plus_2010_x64_515489.exe

These were self-extracting ISO’s basically.

Once I loaded the specific ones I needed – it’s an older Dell D810 32 bit notebook – and ran As Administrator – voila!

I entered my key – 10 minutes later – the completion screen. Trust me – you’ll spend days sometimes, running this down – I truly hope this helps.

You need to isolate your installation form the dual x86_x64 combo ISO’s / extractions – you need just the ISO / bits you are installing – otherwise – no matter what you try – it’ll drive you nuts. NOTE: This is particular to the older notebook/desktop architectures and where you do have Windows Vista/7 installed and working – but as you already know – you had issues with various drivers perhaps, etc.

NOTE: I did see this behavior not only in Office but many bits from MSFT. Typically it happens when you extract an ISO and copy it from one system to another – especially a pain when copying to a VM in VMware Workstation or Hyper-V, for example. Invariably, we’d pull the ISO down on the host we need to install on – and all is well – on a VM – but not so on these older infrastructures.

Try the above – using very specific bits – not mixed x86/x64.

HTH’s….

How to Find a Microsoft Partner – Microsoft Partner Network

I’ve worked for Microsoft Partners – anything from a Registered Partner – to the only Platinum Partner in history – that I’m aware of – HP – and in working for all of them – I’ve always wondered – how do day-to-day people find a Microsoft Partner?

Fortunately, over the years, they’ve gotten better at helping you do this.

Microsoft PinPoint is many things – but the key thing you’ll like – is you can pull it up and in a few keystrokes/clicks – find out 1) is this a real Microsoft Partner? 2) What are their real competencies (which is new in 2010/2011 and forward), 3) what is their reputation as a Partner?

Fortunately – you can find out a great deal – click – http://pinpoint.microsoft.com/en-US/companies - enter a search context – and have at it.

More to come… Champing at the bit to blog more on SharePoint 2010 – SPS solutions, but our real focus? Our book due Jan 2012 (tentatively – we may be able to publish it sooner) Multi-Tenancy Hosting with SharePoint Foundation, Server 2010, and On-Premise Hosting Farms.