!)when using RPC/HTTPS connection in Outlook, you will need to follow the instructions below to store your password so Outlook will not prompt you for credentials. You must be running on Windows XP or Vista (any edition except Windows Home).

2) In Outlook 2003, go to: Tools > Email Accounts > Click Next to View or change existing email accounts > Highlight Microsoft Exchange Server and click Change.
In Outlook 2007, go to Tools > Account Settings > doubleclick Microsoft Exchange.
Click More Settings > Connections tab > Exchange Proxy Settings.
Select NLTM Authentication as the Proxy Authentication Setting

====================
In Windows, click the Start Menu > Run > Type in “control keymgr.dll’”
You’ll see Credential Manager window with an entry with the Exchange Server name.
Change Windows credentials:

If you are missing the Add button you may want to modify Windows Registry to save the password. Note, that for editing Windows Registry administrator rights are required, because it is not safe and you will perform it on your own risk.

In Windows, click the Start Menu > Run > Type in “regedit”
Navigate to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Lsa\
Find DisableDomainCreds entry. Value of 1 (enabled) will prevent you from saving new credentials.
Change the value to 0 and reboot. You should have the Add button. Note, that the value of 0 is the default value.
Also check LmCompatibilityLevel entry. It should be set to 3, which is a default value. If you have another value, change it to 3. If it does not work with 3 then also try it with 2.
Reboot the computer to apply changes.

Cause:

The error occurs because of a problem with BPACMD.EXE attempting to load BPAClient.dll. While upgrading the instance of SQL Server the setup looks for the BPAClient.dll and it fails as it is not able to find it at C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\BPA.

Solution :
Copy the BPAClient.dll file from the following location C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\BPA\bin to C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\BPA.

PHP uploaded files will generally get uploaded with the user nobody when using mod_php. This is the apache module for PHP which means the file will be uploaded with the apache user. In order to work around this you can modify your code to chown the file to the appropriate ftp user. The best option is to use PHP in FCGI mode or install SuPHP. This will ensure the files will always upload using the folder owner id.

Using cpanel this can be installed using the easyapache tool.

error:
Can’t locate loadable object for module Template::Stash::XS in @INC (@INC contains: /usr/local/cpanel /scripts /usr/lib/perl5/5.8.8/i686-linux /usr/lib/perl5/5.8.8 /usr/lib/perl5/site_perl/5.8.8/i686-linux /usr/lib/perl5/site_perl/5.8.8 /usr/lib/perl5/site_perl/5.8.7 /usr/lib/perl5/site_perl/5.8.6 /usr/lib/perl5/site_perl/5.8.5 /usr/lib/perl5/site_perl .) at /usr/lib/perl5/5.8.8/i686-linux/DynaLoader.pm l

===========solution =====

Delete source file of perl module “XS.pm”located at /usr/lib/perl5/site_perl/5.8.8/Template/Stash/
Absolute path should be /usr/lib/perl5/site_perl/5.8.8/Template/Stash/XS.pm
Then install perl module by cPanel script /scripts/perlinstaller
/scripts/perlinstaller Template::Stash:XS.pm. It can also install from the WHM
Once it install just update cPanel by using command /scripts/upcp –force

Microsoft reason for the error:
This problem typically occurs because drivers call either the IoQueueWorkItem function or the ExQueueWorkItem function two times on the same work item before the work item has been executed.

Device drivers that statically allocate either the IO_WORKITEM structure or the WORK_QUEUE_ITEM structure are particularly prone to this problem. Device drivers that perform such a static allocation must guarantee that they do not try to use the statically allocated item while it is already queued.

================================
WHAT.. that was very technical …

===============
The cause is due to a corrupt hardware driver. you will need to locate the hardware that is having the problem and disabled it. Then install the latest driver for the harddrive before enabling it.

We ran install this issue when playing with out wireless card.
=================

M$ Knowledgbase on it