Alexander’s Blog

Recently, I was installing Microsoft Office SharePoint Server 2007 Beta 2 on Windows Server 2003 running on my Virtual PC. I installed .NET Framework 2.0, Internet Information Services (IIS) 6.0, Windows Workflow Foundation Beta 2 and then added the ASP.NET 2.0 service extension in IIS 6.0. When I ran the setup.exe I received the following error “This product requires ASP.Net web service extensions to be enabled in Internet Information Services (IIS). Enable this setting and re-run setup.”

I verified that the ASP.NET 2.0 extension was enabled but still received the same error. The .NET Framework 2.0 didn’t give me the option to repair in Add or Remove Programs in Control Panel (similar to the one that’s available for Workflow Foundation shown below).

I knew that the ASP.NET was not properly registered because the General tab showed that the extension was not used by the ASP.NET v2.0.50727 as expected, instead it showed “unknown”, as shown in the following screen shot.

Rather than reinstalling the .NET Framework, I decided to register ASP.NET by using the following command at the command prompt. I made sure that I was in the folder where aspnet_regiis was located.

aspnet_regiis -i

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727>aspnet_regiis -i
Start installing ASP.NET (2.0.50727).
……………………………..
Finished installing ASP.NET (2.0.50727).

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727>

When I ran the SharePoint Server setup it failed again. I ran “aspnet_regiis -i” one more time, restarted the IIS Admin service and noticed that the ASP.NET was now being used by v2.0.50727. I ran the SharePoint Server setup again and it finally worked. If you’ve run into a similar situation, hopefully this will help solve your problem.

CodeWeavers’ latest Windows-compatibility product is on its way. Intended for Intel Mac OS X machines, CrossOver Mac will allow Mac users to run their favorite Windows applications seamlessly on their Mac, without the need for a Windows OS license of any kind.

The product is currently in its beta and is expected to be released in late July or early August. CrossOver Mac will be priced at $59.95 for a single copy. Volume and Educational discounts will apply. CrossOver Mac will come with 1 year of both Level 2 support and free product upgrades from CodeWeavers.

If you are hoping to get a beta copy, good luck. There is a huge backlog of testers and chancing of getting in at this time are rather slim. Keep in mind that CrossOver Mac will only run on Intel OS X Macs. Click here for more information.

I ran into this situation when I was installing Office 2003 on Windows computer. I was prompted for SKU017.CAB file. Here’s what the error message looked like.

If you do a search on your computer, you may not find the SKU017.CAB, especially if you have deleted the MSOCache folder to save disk space. You won’t find SKU017.CAB on the source CD for Office 2003 either. Notice that the error message is asking for Microsoft Office FrontPage 2003 CD and not for Microsoft Office 2003 CD. What’s not clear to a lot of people is that Microsoft Office 2003 Service Packs not only update the Office 2003 products but also Microsoft Publisher and Microsoft FrontPage 2003.

If you insert the source CD for Office FrontPage 2003, the Office 2003 setup will continue.

Microsoft has released a list of applications that are affected by Windows Server 2003 SP1. Microsoft also released a list of applications that passed the application compatibility test. The solutions or possible workaround are documented in KB article 896367. The Windows Application Experience test teams tested 127 server applications on Windows Server 2003 SP1 computers. The goal of the test teams was to verify that the server applications maintained the same level of functionality that was verified for Windows Server 2003. All tests were performed by using the default settings in the English version of Windows Server 2003 SP1. An application passed if no failing functionality regression was found when the functionality of the application in Windows Server 2003 with SP1 was compared to the functionality of the application in Windows Server 2003.

More info…

Last week I got an e-mail from a family member who wasn’t able to install a program she purchased a year ago. The software is called “Creating Keepsakes - Scrapbook Designer”. She was getting an error message “Error 1606. Could not access network location . All users\”. She went to the vendor’s Web site looking for solutions but didn’t find any, she also e-mailed them 3 times but never heard back from them. I told her of a solution that worked and I think it’s worth documenting because this error can occur under various circumstances. For example, you may encounter this error if you try to install or uninstall Norton AntiVirus 2003. Sometimes the path and location is given in the error message, which may point to several different paths, such as C:\Documents and Settings\All Users\Desktop, or C:\My Documents\My Pictures.

Microsoft’s KB article 315352 mentions that this error occurs if you upgrade from Windows 98 SE or Windows Me to Windows XP, or Windows XP SP1. However, variations of this error are also known to exist when you upgrade from Windows 98 to Windows 2000. Here’s a step-by-step solution that has worked for me.

1. Click on Start, Run and then type REGEDIT.EXE to start the Registry Editor.

2. Navigate to:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders.

3. Double-click the Common Administrative Tools Value Name and set the data value to %ALLUSERSPROFILE%\Start Menu\Programs\Administrative Tools.

4. Navigate to:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Explorer\Shell Folders.
Notice that this path is different than the path in step 2. This is “Shell Folders”, in step 2 you went to “User Shell Folders”.

5. Double-click the Common Administrative Tools Value name and verify that the Value data is set to the
%ALLUSERSPROFILE%\Start Menu\Programs\Administrative Tools.

6. Close the Registry Editor.

7. Restart your computer.