Windows 7 taskbar covers all windows
I recently noticed that the taskbar was blocking the bottom of all windows (IE, Outlook, etc) - making it difficult or impossible to access scroll bars, status(es) etc.
I looked around the web, and someone advised clearing the profile (losing all my stuff!) but someone else had a simple fix that worked:
Right click on taskbar, choose 'Properties'
Check "auto hide"
Uncheck "auto hide".
I also had to reboot to make this work...but work it did!
Labels: taskbar, win7, windows
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.
