An error occurred while creating the IIS virtual directory during Exchange 2007 setup
Trying to setup Exchange 2007, you get an error that basically states:
An error occurred while creating the IIS virtual directory 'IIS://mailserver.yourserver.com/W3SVC/
1/ROOT/owa' on 'mailserver'.
You try to uninstall the Client Access Role (CAS) but alas! you can only do maintenance once you install Exchange 2007...and you get the same error (over and over and over...)
I suspect that the base problem is that IIS is running in 32-bit compatibility mode; Exchange 2007 only runs on 64-bit processors; but you can't fix it and you can't find it.
Is there help!
Yes!
However, once you start the install, how do you wipe out the CAS and start over?
That old fallback - command line tools!
Check out this link:
http://technet.microsoft.com/en-us/library/bb124273.aspx
It tells you how to do cool stuff!
For example, to remove the Client Access server role from an existing server, type the following:
%LocalExchangeInstallationDir%\bin\Setup.com /role:ClientAccess /Mode:Uninstall
(My %blahblahblah% didn't work, so I did a CD to the Exchange program directory and type it in manually)
It killed the role! I could reinstall! So, I ran setup again (note, this process will wipe out the setup files cached on your drive, and you will need the installation media *or* the downloaded programs to continue).
After wiping out CAS, during the reinstall the IIS error popped up, and I had to follow the recommended action, which was:
***--***
Microsoft® Exchange Server 2007 setup cannot continue because the Microsoft Internet Information Service (IIS) is running in 32-bit mode on this 64-bit computer.
Exchange 2007 requires that IIS be in full 64-bit mode when it runs on a 64-bit computer.
To resolve this issue, switch IIS to 64-bit mode, and then rerun Microsoft Exchange setup.
To switch IIS to 64-bit mode
Open a command prompt.
Type the following:
cscript c:\inetpub\adminscripts\adsutil.vbs SET /w3svc/AppPools/Enable32BitAppOnWin64 False
Press enter
*** Then it worked!!!!! ***
Hope that helps.
-Brian
Activesync fails with error 0x8004010F on Pocket PC
Activesync fails with error 0x8004010F on Pocket PC, when synchronizing the Exchange/Outlook.
Nothing changed on my Pocket PC *or* my server! Rebooting the server didn't work.
This began happening yesterday. There are a few suggestions, but the one that worked for me was to remove the email synchronization from the Pocket PC, sync (which removes all the email from the device), add it back and sync again. Presto!
So..start activesync on the Pocket PC.
Go to Menu -> Options and uncheck E-mail
Sync
Go to Menu -> Options and re-check E-mail
Sync
If that doesn't work...Doug suggested:
I had the same problem and none of the above worked! However this did: On the pockect PC open the my device\windows\activesync folder delete the synckey and srvrSync files re sync[Note: I haven't tested this solution!]
Labels: activesync, email, failure, Pocket PC
How to use msiexec.exe and the globally unique identifier (GUID) of the product to remove suite or stand-alone Office 2000 programs
This article was previously published under Q296067
SUMMARY
You can remove Microsoft Office 2000 Suite editions and stand-alone Office programs remotely with Microsoft Systems Management Server or by other means. To remove a program or suite remotely, you need the product's globally unique identifier (GUID). This article lists the GUIDs for all Office 2000 suite editions and stand-alone Office programs.
MORE INFORMATION
Each Office Suite and stand-alone program has a globally unique identifier (GUID). There are two forms of GUIDs: uncompressed (or standard) and compressed. Compressed GUIDs are stored in the registry. You can use the uncompressed GUID to identify the suite or program to be removed when you are running the Windows Installer program.
Removing Programs or SuitesTo remove a program or suite, run the following command with the appropriate product GUID:
msiexec.exe /x {guid} where GUID is the uncompressed GUID number inside braces.
For example, the following command removes Microsoft Office 2000 Premium Edition without any further user interaction:
msiexec.exe /x {00000409-78E1-11D2-B60F-006097C998E7} /qn
If necessary, you can also create a log file during the removal. To do this, append the following to the end of the command line:
/l*v C:\uninstall.log
Compressed and Uncompressed GUIDsThe following are the GUIDs for all the Microsoft Office product suites and stand-alone programs. The first GUID for each product in the following list is the uncompressed or standard GUID.
Office 2000 Premium CD1 GUID: {00000409-78E1-11D2-B60F-006097C998E7}
Compressed GUID: 904000001E872D116BF00006799C897E
Office 2000 Premium CD2 GUID: {00040409-78E1-11D2-B60F-006097C998E7}
Compressed GUID: 904040001E872D116BF00006799C897E
Office 2000 Professional CD1 GUID: {00010409-78E1-11D2-B60F-006097C998E7}
Compressed GUID: 904010001E872D116BF00006799C897E
Office 2000 Professional CD2: (same as Office 2000 Premium CD2)
Office 2000 Standard CD1 GUID: {00020409-78E1-11D2-B60F-006097C998E7}
Compressed GUID: 904020001E872D116BF00006799C897E
Office 2000 SBE CD1 GUID: {00030409-78E1-11D2-B60F-006097C998E7}
Compressed GUID: 904030001E872D116BF00006799C897E
Office 2000 SBE CD2: (same as Office 2000 Premium CD2)
Office 2000 SBE CD2: (same as Office 2000 Premium CD2)
Word 2000 GUID: {00170409-78E1-11D2-B60F-006097C998E7}
Compressed GUID: 904071001E872D116BF00006799C897E
Excel 2000 GUID: {00110409-78E1-11D2-B60F-006097C998E7}
Compressed GUID: 904011001E872D116BF00006799C897E
PowerPoint 2000 GUID: {00130409-78E1-11D2-B60F-006097C998E7}
Compressed GUID: 904031001E872D116BF00006799C897E
Access 2000 GUID: {00100409-78E1-11D2-B60F-006097C998E7}
Compressed GUID: 904001001E872D116BF00006799C897E
Outlook 2000 GUID: {00160409-78E1-11D2-B60F-006097C998E7}
Compressed GUID: 904061001E872D116BF00006799C897E
XP Blue Screen of Death, Inaccessable Boot Volume or other nonsense
First, try to boot in Safe Mode by pressing F8.
Then, try booting from your XP CD and either Re-install or try the follwing.
Go to Recovery mode
Type the following commands
CHKDSK C: /r
CHKDSK C: /p
fixboot
If you STILL have problems you can try this last ditch fix:
Boot off the XP CD into recovery mode
COPY K:\i386\ntldr
C: COPY K:\i386\ntdetect.com C:
ATTRIB -H -R -S C:\boot.ini
DEL C:\boot.ini
BootCfg /Rebuild
Good luck!
Got this from one of the Lockergnome forums....seems to be a problem with XP and Windows Server 2003, especially in the networking componets area.
Problem: You have deleted a netword adapter/upgraded motherboards, and now you get IP Address conflicts with the "phantom" adapter -- and you can't find it in Device Manager to delete it!
---------------------
Solution: Either open a command prompt (Start -> Run -> CMD
) and type in the following, or copy and paste it to a new .BAT file. You will have to save the Notepad file as "all files" or it will put ".txt" on the end of the name.
set DEVMGR_SHOW_NONPRESENT_DEVICES=1
devmgmt.msc
exit
If you saved the file run it, or, if you typed the commands, the Device Manager should appear. Click on View -> Show Hidden Devices.You should now have a device manager which shows all of the hardware ever detected on your system.
-----------------------
Delete the offending devices, reboot, and you should be ready to go!
Here are two MSKB articles on missing network components:
http://support.microsoft.com/kb/269019
http://support.microsoft.com/?id=825826
IF, after trying everything in the known world, including updated the MDAC, try reading this knowledgebase article.
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q328306
What part of that that worked for me was deleting the key for the SQLSERVER instance under the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\Client\ConnectTo\DSQUERY
Cheers.
This is the latest bestest fix for the Entry Point Not Found (incomplete SP2 install!)
You receive an "Explorer.EXE - Entry Point Not Found - The procedure entry point SHCreateThreadRef could not be located in the dynamic link library Shlwapi.dll" error message after you install the MS04-038 security update
This article discusses how to recover a computer that reports an error after you apply the security update
MS04-038.
SYMPTOMS
When you install security update
MS04-038 on Microsoft Windows XP, you receive the following error message after your computer starts:
Explorer.EXE - Entry Point Not Found - The procedure entry point SHCreateThreadRef could not be located in the dynamic link library SHLWAPI.dll
CAUSE
This error occurs when MS04-038 is installed on a computer with a failed Windows XP Service Pack 2 (SP2) installation. Typically, if Windows XP SP2 installation fails, an automatic rollback occurs that returns the computer to the pre-Windows XP SP2 installation state. If automatic rollback does not occur, the service pack recovery process will partially uninstall Windows XP SP2 after you restart your computer. (For example, automatic rollback may not occur if a power failure occurs during Windows XP SP2 installation.) After you restart the computer again, you receive a message that prompts you to use Add or Remove Programs in Control Panel to manually remove the remnants of the failed installation. If you do not follow this recommendation, and you do not use Add or Remove Programs to remove the remnants of the failed installation, your computer will have pre-Windows XP SP2 files, and your registry will contain Windows XP SP2 information. If your computer has pre-Windows XP SP2 files and your registry contains Windows XP SP2 information,
Windows Update or Automatic Updates offers the Windows XP SP2 version of the
MS04-038 security update.
RESOLUTION
To recover your computer, follow these steps:
1.
Start your computer and log on as you typically do. Note If your computer will not start correctly, start the computer in Safe mode. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
315222 A description of the Safe Mode Boot options in Windows XP
2.
When you receive the error message, press CTRL+SHIFT+ESC to open Task Manager. You can safely ignore any additional error messages that may appear.
3.
On the File menu, click New Task (Run...).
4.
In the Open box, type control appwiz.cpl, and then click OK. You can safely ignore any additional error messages that may appear.Note If the Add or Remove Programs tool (Appwiz.cpl) does not open, type the following line in the New Task (Run...) box to remove the Internet Explorer fix, and then go to step 5:
%windir%\$NtUninstallKB834707$\spuninst\spuninst.exe
5.
In the Add or Remove Programs window, click Windows XP Hotfix – KB834707, click Remove, and then follow the instructions.
6.
When the Finish button becomes available, click Finish, and then let your computer to restart, even if it seems that the removal process is not complete. You can safely ignore any messages about additional software or hotfixes that are installed during this process.Warning Although your computer may successfully start without error messages, your computer is still in an incomplete Windows XP SP2 state. You must complete the remaining steps and reinstall Windows XP SP2.
7.
After your computer restarts, click Start, and then click Control Panel.
8.
Click Add or Remove Programs, click Windows XP Service Pack 2, click Remove, and then follow the instructions. If you receive a message about software that you may have installed after you installed Windows XP SP2, make a note of the titles. You may have to reinstall these products after you reinstall Windows XP SP2.Note If you cannot access Add or Remove Programs, use Task Manager as described in steps 1, 2, and 3. Remove Windows XP Service Pack 2 by typing the following in the New Task (Run...) box:
%windir%\$NtServicePackUninstall$\spuninst\spuninst.exe
9.
After your computer restarts, visit the
Windows Update Web site. Reinstall Windows XP SP2. For information about how to install Windows XP SP2, and for steps that you can take to help make sure that Windows XP installs successfully, visit the following Microsoft Web site:
http://www.microsoft.com/sp2install/
10.
After Windows XP SP2 has successfully installed, visit the
Windows Update Web site and install any critical updates.If this procedure does not work, you can perform an in-place reinstallation. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:
315341 How to perform an in-place upgrade (reinstallation) of Windows XP
STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
MORE INFORMATION
Q1: I do not think my computer is in an "incomplete Windows XP SP2 state." How can I know for sure?A1:. After you successfully remove Windows XP Hotfix – KB834707, use one of the following methods to determine whether your computer is in an incomplete Windows XP SP2 state.
Method 1
1.
Check Add or Remove Programs for the presence of Windows XP SP2. If Windows XP SP2 is listed, go to step 2. If Windows XP Service Pack 2 is not listed, Windows XP Service Pack 2 is not installed.
2.
Determine the version of the Lsass.exe file that is in the %Windir%\System32 folder. To do this:
1.
Click Start, click Search, and then click All Files and Folders.
2.
In the All or part of the file name box, type %windir%\system32\lsass.exe, and then click Search.
3.
Right-click the Lsass.exe file, click Properties, and then click the Version tab. Note The Lsass.exe file may appear as "Lsass" without an extension.If the version number of the Lsass.exe file is earlier than 5.1.2600.2096, and Windows Service Pack 2 appears in the Add or Remove Programs tool, your computer is in an incomplete Windows XP SP2 state.
Method 2
Click Start, and then click Run, type winver, and then click OK.If the version is listed as "Version 5.1 (Build 2600.xpsp_sp2_rtm.040803-2158: Service Pack 2" or a later version, you have the correct installation of Windows XP SP2. However, if the version has a number that begins with a 01, a 02, or a 03, your computer is in an incomplete Windows XP SP2 state. Additionally, if any number that is less than 040803 appears after "xpsp2", such as "Build 2600.xpsp2.030422-1633: Service Pack 2," your computer is in an incomplete Windows XP SP2 state.
REFERENCES
For additional information about Windows XP SP2, click the following article number to view the article in the Microsoft Knowledge Base:
322389 How to obtain the latest Windows XP service pack
Found this at doxdesk.com, and wanted to store it for posterity...
Xupiter consists of an Internet Explorer toolbar containing link buttons to one of Xupiter's search engines and a task run at Windows startup which downloads updates to the software and may launch pop-ups. It also contains functionality to hijack your home page and address bar searches, and add Xupiter links to your bookmarks.
Variants
Xupiter/Xupiter uses the site xupiter.com for all functions; Xupiter/Xjupiter is the same but uses xjupiter.com instead. Xupiter/2003 is the same as the Xupiter variant, but puts its DLL directly in its Program Files folder instead of in an 'Updates' folder.
Xupiter/BrowserWise points to browserwise.com but is still otherwise identical to Xupiter. Xupiter/Browser is a newer variant which still points to browserwise.com, but stores its program files in a folder called 'Browser' instead of 'Xupiter'.
Xupiter/Sqwire is a newer variant pointing at sqwire.com. Its program files are stored in a 'Sqwire' folder, in a different layout to previous versions, and an installer DLL is left in Downloaded Program Files.
Xupiter/OrbitExplorer is the latest variant, pointing at orbitexplorer.com. Some of its program files are stored in an 'Orbit' folder in Program Files, the rest in an 'OE' folder in Common Files. It also has the installer DLL.
Also known as
XupiterToolbar (program name).
Distribution
Installed by ActiveX drive-by-download in affiliate pages. Known sources include the site www.freewebupgrades.com (which is advertised by junk e-mail) and pop-up adverts on sites such as FortuneCity and cjb.net subdomains.
More recently also bundled with Grokster.
One of Xupiter/Sqwire's ActiveX drive-by-download pages has been advertised by junk e-mail (spam) offering a 'Free Christian Toolbar'. Another pretends to be a program to disable Windows Messenger service pop-ups.
What it does
Advertising
Yes. Apart from the hijacking and added links, the software periodically opens pop-under advertisements as directed by its controlling servers. (These may appear in windows with only an 'exit' menu.)
Privacy violation
The privacy policy states that the software may track all web usage. However this behaviour has not been observed.
Security issues
Yes. The software contacts its servers to ask for update code, which is executed without checks. It has also been known to download third-party software (for instance a casino loader app).
Stability problems
In the initial variants, the update-checking task tries to connect to xupiter.com to download updates whether or not you are connected. If it fails it may cause a crash in 'RunDownload.exe'. Some versions of Xupiter can cause the Windows Explorer to crash when opened under Windows XP.
Removal
The OrbitExplorer variant may have an uninstall available. Go to Add/Remove Programs in the Control Panel, choose 'Orbit' and click 'Remove'.
Other variants have no built-in uninstall. An uninstaller is available through ActiveX drive-by-download from Xupiter sites; reports suggest this works for some but not all variants, and may leave a message on bootup that Xupiter must be reinstalled.
The latest updates of Spybot S&D and Ad-Aware can remove all Xupiter variants.
Manual removal
Open the registry (from the Start menu, click Run and enter regedit) and find the key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run.
Delete the entries 'XupiterStartup' and 'XupiterCfgLoader' (earlier variants), 'SQUpdatesChecker' and 'SQConfigChecker' (Sqwire variant) or 'OrbitUpdate' and 'OrbitView' (OrbitExplorer variant).
Open a DOS command prompt window (Start->Programs->Accessories) and enter the following commands to deregister the toolbar (Xupiter and BrowserWise variants):
cd "%WinDir%\System" regsvr32 /u "\Program Files\Xupiter\Updates\XupiterToolbar.dll" regsvr32 /u "\Program Files\Xupiter\Updates\XTUpdate.dll" regsvr32 /u "\Program Files\Xupiter\Updates\XTSearch.dll"
(The earliest variants of Xupiter didn't have the XTSearch.dll file, so don't worry if this last command gives an error.)
For the 2003 variant, use:
cd "%WinDir%\System" regsvr32 /u "\Program Files\Xupiter\XupiterToolbar.dll" regsvr32 /u "\Program Files\Xupiter\XTUpdate.dll" regsvr32 /u "\Program Files\Xupiter\XTSearch.dll"
For the Browser variant, use:
cd "%WinDir%\System" regsvr32 /u "\Program Files\Browser\Updates\BrowserToolbar.dll" regsvr32 /u "\Program Files\Browser\Updates\BWUpdate.dll" regsvr32 /u "\Program Files\Browser\Updates\BWSearch.dll"
For the Sqwire variant, use:
cd "%WinDir%\System" regsvr32 /u "\Program Files\Sqwire\t.dll" regsvr32 /u "\Program Files\Sqwire\u.dll" regsvr32 /u "\Program Files\Sqwire\s.dll"
For the OrbitExplorer variant, use:
cd "%WinDir%\System" regsvr32 /u "\Program Files\Common Files\OE\toolbar.dll" regsvr32 /u "\Program Files\Common Files\OE\redirector.dll" regsvr32 /u "\Program Files\Common Files\OE\search.dll"
(On non-English versions of Windows, 'Program Files' and 'Common Files' may be called something different. In that case you will have to change these commands to match the name of these folders.)
Restart the computer and open the Program Files folder. Delete the 'Xupiter', 'Browser', 'Sqwire' or 'Orbit' folders, and in the OrbitExplorer variant also the 'OE' folder inside Common Files. For the Sqwire and OrbitExplorer variants, you should also open 'Downloaded Program Files' in the Windows folder and remove the 'Loader class' entry if it is there.
You can now restore your home page (Internet Options->General->Home page) and your search settings (Internet Options->Programs->Reset web settings). You can also delete the settings to clean up if you like: open the registry and delete the key HKEY_CURRENT_USER\Software\Xupiter, HKEY_CURRENT_USER\Software\SQ (Sqwire variant) or HKEY_CURRENT_USER\CLSID\{0FDA4D2B-7975-405d-8D7C-F5E2247EAE80} (OrbitExplorer variant).
