Posts Tagged ‘Office’

How do I – Activate my MSDN copy of Visio 2013 Professional?

Written by Cornelius J. van Dyk on . Posted in Blog, How Do I...

Situation:  You have a MSDN subscription and you have downloaded Office 2013 or one of the Office products, like Visio 2013 Professional, from Microsoft and have installed said product.  You have a license key provided by MSDN, but the installer never prompts you for the license key.  This is a departure from traditional installer behavior where you would enter the license key before the install can even be done.  Once you’ve completed the install, you open your product and are confronted by this little gem of a warning just below the Ribbon:

screenshot.492

Since you have a license key, you click the “Activate” button.  You are presented with this screen which is there for a while, so be patient:             

screenshot.493

Eventually, you’re presented with a Sign In screen like this:

screenshot.494

Having gotten your license key from MSDN, you promptly enter your MSDN UserID and password and click the “Sign in” button.  Unfortunately, you’re presented with an error thus:

screenshot.495

After trying the login a couple more times (just in case you fat fingered the password), you click the “Can’t access your account?” button.  Your browser opens and you’re taken to this page:

screenshot.496

Again, you enter your MSDN UserID as well as the CAPCHA code and click the “Next” button.  This time you’re presented with an error screen stating that your ID doesn’t exist thus:

screenshot.497

So now what?

This is the problem with the new installer.  In order to use our MSDN license key, we’re going to have to follow these steps:

  1. Click “Start”.
  2. On the popup menu, click “Control Panel”.
  3. In the Control Panel, double click the “Programs and Features” icon.
  4. Scroll down through the list of installed products and locate the product in question.  In this example it was “Microsoft Visio Professional 2013”.
  5. Select the target product.
  6. In the toolbar above the list, click the “Change” button.screenshot.498
  7. When the configuration window appears, select the “Enter a Product Key” radio button and click “Continue”.screenshot.499
  8. No enter your product key and click “Continue”.screenshot.500
  9. Unfortunately, you have to go through the configuration piece again.  For a simple license key addition, I don’t see the need in this, but that how it works for now.  You could just click “Continue” but in my case, I wanted to make sure nothing was getting reset so I clicked “Customize”.screenshot.501
  10. Ensure your configuration settings are as desired and click the “Continue” button.screenshot.502
  11. It sets in the Configuration Progress screen for quite a while.  Just be patient.screenshot.503
  12. Once the configuration completes, click the “Close” button.screenshot.504
  13. Finally re-launch the application and the red warning should now be gone.screenshot.505

 

This took me a while to figure out, so hopefully this saves someone some time.



Cheers
C




image

Latest Hyper-V VMs Available for Download

Written by Cornelius J. van Dyk on . Posted in Blog

Here’s a quick list of the lastest Hyper-V Virtual Machines available for download from Microsoft.  If you’re setting up a little private playground lab, this will save you tons of time and get you working out the latest and greatest software in a flash.

Start by grabbing the latest IW VM loaded with Office and SharePoint 2010 goodness: If you have Exchange cravings, satisfy them here: Want to throw OCS in the mix too?  Here you go: See how system health plays with all these: Of course, if you want to look at migration scenarios you could restore your restore you data to this VM and run an upgrade/migration: Lastly, if you want to just have the OS baseline and do all the other installs yourself, start here:  

Happy downloading!



Cheers
C




image

How do I – Fix the problem where IE crashes when opening Office documents on SharePoint?

Written by Cornelius J. van Dyk on . Posted in How Do I...

OK, this one has several pieces out there in the blogosphere and some more on the newsgroups, but I’ve not seen a comprehensive post that clearly stipulates why the problem occurs and how to fix it.

Why? OK, so first the why. Why does IE (both 6 and 7) crash when I try to open an Office document (Word, Excel, PowerPoint etc.) on SharePoint (WSS or MOSS)?



When you try to use the “Edit in Microsoft…” option for a document it always blows up. Sometimes this is also seen when you just simply click on the document which would then open in browse mode.

Either way, instead of seeing this:



Friendly little warning, you see this:



Ugly “The exception unknown software exception (0xc06d007f) occurred in the application at location 0x7c812a5b.” error message. When you click the “OK” button, you get another error message, the “The instruction at “0x30cb05e4” referenced memory at “0x00000000”. The memory could not be “written.” error.



Well the problem started when you installed a brand new shiny Office 2007 application. In my case, I was working on migrating us to MOSS 2007 from SPS 2003 and installed SharePoint Designer 2007… and that was enough to break my system. The underlying problem occurs in the OWSSUPP.DLL file located in the C:\Program Files\Microsoft Office\Office12 folder.

After much research and debug tracing with Joe on a Microsoft Premier Support ticket I had opened for this, we discovered that OWSSUPP.DLL actually calls, down the line, the NAME.DLL which, installed with Office 2007 apps, are incompatible. Anyway, to make a long story short, reverting back to the old version of OWSSUPP.DLL will solve the problem.

How?

OK, so here’s how you fix it. NOTE: This fix will only work until you install another Office 2007 component at which point you will need to redo these steps again.

  1. Open Windows Explorer and navigate to C:\Program Files\Microsoft Office\Office12.
  2. Locate the OWSSUPP.DLL file and rename it to OWSSUPP.DLL.OLD.


  3. Now navigate to the C:\Program Files\Microsoft Office\Office11 folder.
  4. Locate the OWSSUPP.DLL file and copy it.


  5. Now navigate back to the C:\Program Files\Microsoft Office\Office12 folder.
  6. Paste the OWSSUPP.DLL file from the Office11 folder to here, the Office12 folder.
  7. Open a command prompt window with Start/Run/cmd.
  8. Chance directory to the Office12 folder with CD “Program Files\Microsoft Office\Office12”.
  9. Now using REGSVR32 OWSSUPP.DLL re-register the DLL file.


  10. Now here’s where the trick come in. You will receive an error message like this:


  11. Pay the error no heed. The registration worked. Go back and attempt to edit your Office document on SharePoint. It should work without any problems.


Cheers
C




image

Office Ultimate 2007 Installation Fails – How to fix it!

Written by Cornelius J. van Dyk on . Posted in Blog

If you, like myself and millions out there, couldn’t wait for Office 2007 and installed the beta bits as soon as they became available, then you too will be facing an “upgrade” shortly as the beta bits expire early next year.

I discussed my erroneous assumption that I’ll be able to upgrade my Office 2007 Professional Plus 2007 Beta 2 TR to the RTM bits for Office Ultimate 2007. The issue was that the RTM bits would not “upgrade” any of the beta versions. So in order to get to the new version, I had to uninstall all my beta versions. I had the Office suite as well as SharePoint Designer 2007 Beta 2 TR and Visio 2007 Beta 2 TR installed.

I began by just removing the Office suite… same error message.
Then I removed the Visio beta… same error message.
“OK fine” I thought as I uninstalled the SharePoint Designer beta as well.
Restart setup and… same error message! Say WHAT?!?!

I checked the Windows Add/Remove Programs to see if there was any beta bits left.

010207_0102_OfficeUltim1

As you can see, Visio for Enterprise Architects is listed as well as Live Meeting 2005, but NO 2007 products.
“OK” I thought. “A reboot will fix it.” 
So I rebooted… restart Setup… SAME ERROR MESSAGE!!!

By this point I’m starting to run out of ideas.
After scratching around for a couple of minutes, I conclude that the Office beta products must have left registry entries behind and I’m going to have to user a registry cleaning utility to fix it.
Though I’m not afraid to make registry changes, I’ve always avoided tools that make mass registry changes… quite frankly, that scares me a bit.
Anyway, so I conduct a search for the term “registry cleanup tools” and find:

010207_0102_OfficeUltim2

You’ll notice that the first item listed, after the sponsored links of course, is from the Microsoft Support site and not only does it appear to be a registry cleanup tool, but it appears to be a tool that fixes previous Windows Installer problems… EXACTLY WHAT I NEED! 

I proceed to download the Windows Installer Cleanup Utility from the Microsoft Support site.
[TIP: Add this tool to your toolbox. It’ll save you some day!]

Once downloaded, I installed it and fired it up and what do I see?

010207_0102_OfficeUltim3

I took the liberty of pointing out the Live Meeting 2005 entry and the Visio for Enterprise Architects entry, the two entries that are side by side in the Add/Remove Programs screen.
As you can see, there are 4 beta tools listed.
I selected them an clicked Remove.
Then I quit the Windows Installer Cleanup Utility and restarted Office Ultimate 2007 Setup and… TADA!!! 

010207_0102_OfficeUltim4

Finally, I was able to complete my installation.
So if you run into the same issue, get the Windows Installer Cleanup Utility!



Cheers
C




image