If you have installed Windows 8 by doing an upgrade from Windows 7, you may have experienced this error. SQLJoe wrote an article that includes the solution. Please go through it.
Tag Archives: error
In a scenario where your ISA SQL database is hosted on a different server than the ISA application itself, you may have noticed that your ISA server Firewall Service has been stopping repeatedly with the following error logged:
Event Type: Error
Event Source: Microsoft ISA Server Web Proxy
Event Category: Log
Event ID: 21204
Time: 8:16:12 AM
The ISA Server Web filter failed to log information to SQL Database ISA_Server_Database. The SQL Error description is: Timeout expired.
You also find this error in the Alerts tab, in ISA console monitoring information.
This error is due to the Log Failure alert rule that is configured to stop some services, if the Firewall Service is not able to log an error.
So, to fix this, you need to modify the alert Actions tab, as follows.
1. Connect to ISA console, and go to Monitoring under Arrays -> Monitoring and locate Log Failure. Select the alert, and in the right pane, click on “Configure Alert Definitions”.
2. In the window that opens, make sure the category is “Firewall Service” and go to Actions tab. Deselect the “Stop Selected Services” option.
The result of doing will be that your Firewall Service will not stop, even if it is unable to log some errors in the SQL database. This guarantees a good service uptime, but will not help in case of troubleshooting as some important data might miss.
To find all error codes explanations for your System Center Configuration Manager usage, please go to : http://technet.microsoft.com/en-us/library/bb632794.aspx
UEFI IBM x3650 M2 installed with Windows Server 2008 x64: IRQL_NOT_LESS_OR_EQUAL, Stop Error 0x0000000A
This IBM x3650 M2 installed with Windows Server 2008 x64 R2 is running Hyper-V and multiple virtual machines on it. It is also connected to a EMC NS-960 FC SAN, from which it mounts volumes where the virtual hard disks are located.
1- We noticed that when one of the virtual machine is having a certain load, the complete IBM server has a blue screen showing “IRQL_NOT_LESS_OR_EQUAL” with STOP ERROR “0x0000000A”.
Figure 1: Stop Error
2- It is not the only strange behavior. When the dump consecutive to the error finishes and the server restarts, it stays a long time trying to load Windows in vain. We have to physically go to the datacenter, stop the server, remove the FC cables, and start it up, for the OS to load correctly. We then plug back the FC cables once the OS is completely loaded.
You can imagine the inconvenience, especially when important services are running on the virtual machines!
1- Having a look to different knowledge bases, I found that Microsoft discusses the issue of Windows Server 2008 R2 experiencing stop error 0x0000000A and has published a hotfix.
The following article may be interesting for you to read:
Article ID: 979903 – "STOP 0x000000A" Stop error when there is a request to allocate a large amount of contiguous physical memory in Windows Server 2008 R2 or Windows 7.
It is explained in the article that the issue is due to Memory Manager struggling with database scans.
2- I also found another article on the second behavior and for that one too, Microsoft had a hotfix published.
Article ID: 979374 – The system becomes unbootable after you add raw disks to a Windows Server 2008 R2-based computer that has EFI enabled
Due to the fact that our server runs UEFI and is mounting external storage volumes from the SAN, the system is unbootable, they explain. I just wonder why this issue did not appear before, as we have been running with that server almost for a year without experiencing this.
I would also recommend you follow this link which discusses the same behavior of IBM servers with external storage: http://sites.google.com/site/virtualkb/accueil/hardware/localoperatingsystembootfailswhenexternalstorageisattached-ibmsystemx3550m2x3650m2andbladecenterhs22
The issue might occur on series:
BladeCenter HS22, Type 1936, any model
BladeCenter HS22, Type 7870, any model
System x3550 M2, Type 4198, any model
System x3550 M2, Type 7946, any model
System x3650 M2, Type 4199, any model
System x3650 M2, Type 7947, any model
So I understood that we were merely leaving two different issues at a time.
Did the hotfixes…fix the issues?
We successfully downloaded and applied the two hotfixes one month ago. Since then, we haven’t experienced any of the previous behaviors!!!
Note that in the KB 979374, there are two methods proposed: one method if you are already running your server with the OS installation, another method to be followed at the installation of the server (it is about including the hotfixes into your install media, and you would have to add one other hotfix 975535).
The lesson: So if you have a server built on EFI and may have to add external storage volumes, I would recommend you go to the second method before you install your OS!
I was recurrently getting the following error when installing Office 2007 or 2010 on Windows 7:
Error 2203. An Internal Error has occurred. (C:WindowsInstaller******.ipi – 2147287035 ) Contact Microsoft Product Support Services (PSS) for assistance. For information about how to contact PSS, see C:usersmy_userAppDataLocalTempSetup00000420PSS10R.CHM
(The .ipi file being everytime different)
Looking for a solution, I first found this link which suggested to restart Windows Installer service, and give Full Control permission to “Everyone” on %TEMP% folder.
Unfortunately for me, this never happen to solve my issue.
I finally thought about Windows Clean Boot: http://support.microsoft.com/kb/929135 .
Here follow the steps I used to install correctly Office:
1. Click Start and type "msconfig.exe" in the Start Search box. Press Enter.
2. On the General tab, choose Selective Startup and clear the "Load Startup Items" check box.
3. In the "Services" tab, check "Hide all Microsoft Services" and click disable all.
4. In the "Startup" tab, click "Disable all".
5. Click OK.
6. Restart the computer and try to install Office again. The installation should execute perfectly.
7. After the installation, go back to msconfig.exe and select “Normal startup”. This should also bring back all previous configurations in “Services” and “Startup” tabs.
You are on a 32-bit Windows installation, running Outlook 2003.
You are using locally Microsoft Exchange Management Shell to export a mailbox to a PST file.
But your export generates an error:
[PS] C:\Documents and Settings\sadissa>Export-Mailbox -Identity ZedErasm -PSTFolderPath C:\Temp
Are you sure you want to perform this action?
Exporting mailbox content from the mailbox ‘Erasmus Zed’ into .pst file ‘C:\Temp\ZedErasm.pst’. This operation may take a long
time to complete.
[Y] Yes [A] Yes to All [N] No [L] No to All [S] Suspend [?] Help
(default is "Y"):y
Export-Mailbox : Error was found for Erasmus Zed because: Error occurred in the step: Moving message
s. Failed to copy messages to the destination mailbox store with error:
MAPI or an unspecified service provider.
ID no: 00000000-0000-00000000, error code: -1056749164
At line:1 char:15
+ Export-Mailbox <<<< -Identity ZedErasm -PSTFolderPath C:\Temp
This probably occurs because you don’t have enough rights to perform the export.
You should make sure you give the account used for exporting GenericAll rights on the Exchange database(s) you need to work on.
To do this, you need to have the right database name.
In my case, my databases and storage groups are named the same, so I had this error:
[PS] C:\Documents and Settings\sadissa>Add-ADPermission -Identity Boxes3\DB3 –User Sadissa –AccessRights GenericAll
Add-ADPermission : Boxes3\Boxes3 was not found. Please make sure you have typed it correctly.
After many attempts to write the name in the right format, I found an article on mailbox databases name for the command and decided to configure all databases at the same time:
[PS] C:\Documents and Settings\sadissa>Get-MailboxDatabase –Server Boxes3 | Add-ADPermission –User Sadissa –AccessRights GenericAll
The command executed successfully so I was able to then export the mailboxes I needed.
You might find interesting information at these links: http://www.itexperience.net/export-mailboxes-from-exchange-2007-with-export-mailbox/
In Hyper-V, in the Virtual Network Manager, you are adding a new EXTERNAL virtual Network.
After selecting the physical network card to bind it to your virtual network, you click “Apply” or “OK”.
You receive the following error message:
“Error Applying New Virtual Network Changes
Binding to External Ethernet failed
Cannot bind to my_nic because it is already bound to another virtual network”
To fix this issue, close your Virtual Network Manager and run the command line with administrative privilege. Type:
netcfg -u vms_pp
netcfg -l c:\windows\winsxs\amd64_wvms_pp.inf_31bf3856ad364e35_6.1.7600.16385_none_beda85050b13680c\wvms_pp.inf -c p -i vms_pp
Open the Virtual Network Manager again, and add your external virtual network.
The operation shall be successful now.
In my case, the issue happened after a physical failure of the server: I had to disable two faulty NICs in the BIOS and when restarting the server, Hyper-V got lost in the mapping of the virtual networks and the remaining NICs. So I removed all external virtual networks and tried to recreate each. And I had the error at the recreation.