The last couple of days an application which connects to a certain SSRS server on port 80 results in a lot of error messages.
Source system is W2K8 R2 with 16 Gb RAM.
MaxUserPort setting is 2024
In the application log it shows several connection problems:
An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full x.x.x.x:80
All refering to the SSRS server.
How to solve this problem, simple reboot?
Randomly we have issues on all kinds of servers that Windows Update is completely unresponsive and errors out. I have to believe it has to be something in combination with environment and OS, maybe GPO, I am not sure. Essentially Windows Update does not work, or is completely unresponsive until a reboot. Once a reboot occurs the system seems to come back to life with no issues. It seems to happen after each patch cycle though, but not directly after or any set time after, and not after every patch cycle. We run Symantec Endpoint Protection and I am also checking to see if that specific folder referenced in the error is being scanned and if so, can it be excluded.
Log Name: Application
Source: ESENT
Date: 11/7/2016 7:55:00 AM
Event ID: 488
Task Category: General
Level: Error
Keywords: Classic
User: N/A
Computer: COMPUTER NAME
Description:
wuaueng.dll (352) SUS20ClientDataStore: An attempt to create the file "C:\Windows\SoftwareDistribution\DataStore\Logs\tmp.edb" failed with system error 5 (0x00000005): "Access is denied. ". The create file operation will fail with
error -1032 (0xfffffbf8).
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="ESENT" />
<EventID Qualifiers="0">488</EventID>
<Level>2</Level>
<Task>1</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2016-11-07T14:55:00.000000000Z" />
<EventRecordID>294102</EventRecordID>
<Channel>Application</Channel>
<Computer>ComputerName.Domain.local</Computer>
<Security />
</System>
<EventData>
<Data>wuaueng.dll</Data>
<Data>352</Data>
<Data>SUS20ClientDataStore: </Data>
<Data>C:\Windows\SoftwareDistribution\DataStore\Logs\tmp.edb</Data>
<Data>-1032 (0xfffffbf8)</Data>
<Data>5 (0x00000005)</Data>
<Data>Access is denied. </Data>
</EventData>
</Event>
Log Name: Application
Source: ESENT
Date: 11/7/2016 7:55:10 AM
Event ID: 485
Task Category: General
Level: Error
Keywords: Classic
User: N/A
Computer: ComputerName.domain.local
Description:
wuaueng.dll (352) SUS20ClientDataStore: An attempt to delete the file "C:\Windows\SoftwareDistribution\DataStore\Logs\tmp.edb" failed with system error 5 (0x00000005): "Access is denied. ". The delete file operation will fail with
error -1032 (0xfffffbf8).
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="ESENT" />
<EventID Qualifiers="0">485</EventID>
<Level>2</Level>
<Task>1</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2016-11-07T14:55:10.000000000Z" />
<EventRecordID>294103</EventRecordID>
<Channel>Application</Channel>
<Computer>ComputerName.domain.local</Computer>
<Security />
</System>
<EventData>
<Data>wuaueng.dll</Data>
<Data>352</Data>
<Data>SUS20ClientDataStore: </Data>
<Data>C:\Windows\SoftwareDistribution\DataStore\Logs\tmp.edb</Data>
<Data>-1032 (0xfffffbf8)</Data>
<Data>5 (0x00000005)</Data>
<Data>Access is denied. </Data>
</EventData>
</Event>
Fault bucket , type 0
Event Name: WindowsUpdateFailure3
Response: Not available
Cab Id: 0
Problem signature:
P1: 7.6.7601.23453
P2: c8000408
P3: 00000000-0000-0000-0000-000000000000
P4: Scan
P5: 0
P6: 1
P7: 0
P8: AutomaticUpdates
P9: {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}
P10: 0
Attached files:
These files may be available here:
Analysis symbol:
Rechecking for solution: 0
Report Id: 3058b20c-a4fa-11e6-89e4-005056b54973
Report Status: 0
My laptop can no longer find it's built in web camera, any ideas?
Thanks!
Hello!
I need to use this command-line program to get the MD5 hash over a given file in a Microsoft Windows Server 2003 R2, but when I try it this command:
certutil -hashfile file.txt md5
I get this error:
Expected no more than 1 args, received 2
CertUtil: Too many arguments
If I repeat the command but take away the 'MD5' part, it works fine (looks the default is SHA-1). I've tried to search online to learn what is the earlier version of the Windows Server it works with the 'MD5' part, but I can't find any information about this.
Does anyone here know?
Thanks!
HI
In 2008r2 while we give the dcpromo command there is some error the operation failed because a admin controller could not be contacted for the domain mobhgroup.ae theat contained an account for this computer.
kindly help me out in this regards
Hi,
Please clarify my doubts
1) 32bit MS Access ODBC driver is installed as part of the Windows OS 2008(r2) and Windows OS 2012(R2) ?
2) Will 64 bit MS Access ODBC driver installed as part of Windows2016 or do i need to install explictly?
3) Can 64 Bit MS Access driver and 32 bit MS Access driver co-exist side by side ? or do i need to unistall the 32 bit first
regards
Somaraj
Hello
I need to have one user move files under a share "test" to subfolders.
the share permiisioin assigned to the share "test" with groupA has Read and modify
the NTFS permission assigned to the folder is a group groupB has modify/read&exec, list,read, write.
effective access does NOT have full control, delete subfolder and files, change permission and take ownership.
the subfolder called under "test" is "Testone" has inheritance disabled, with a group called GroupC does not have the modify permission.
So I need to remove that one user from GroupC and add her directly with modify rights?
thanks
Hi All,
Faced with issue that resolution which available in session 0 for services is 1024*768 in my case. Directly it can't be changed, of course, but as per this document - http://download.microsoft.com/download/7/E/7/7E7662CF-CBEA-470B-A97E-CE7CE0D98DC2/Session0Changes.docx - higher limit is 1920*1200.
Is it real to set up 1920*1200 resolution in session 0 or mentioned document has typo and 1024*768 is real limit?
I have a network share with an executable file located in it. If I browse to the share by UNC path from a Windows 7 pro workstation and go to the compatibility tab of the .exe, the options are grayed out.
I have another network share with an executable file located on it. This share and workstation are at a different location, unrelated to the first example. If I browse to the share by UNC path from a Windows 7 pro Workstation and go to the compatibility tab of the .exe file, the options are not grayed out, and I can check or uncheck what ever I need to.
Both shares are located on a Server 2008 R2 system w/sp1. Both workstations are joined to the same domain as the server they are connecting to the UNC path on. Both shares have given the user connecting full access on the smb sharing and ntfs sharing.
Someone please tell me how to make the compatibility tab not grayed out. Here is a screen shot of the comapatibility tab of the .exe file from both shares:
Hello
Thank you for reading my post.
I have successfully installed WDS server role WDS now starts after pressing F12 - no longer asks me to select an Image or enter a password
issue I now have is with the disks.
After I get the error "Windows could not apply the unattend answer file's <DiskConfiguration>"
When I read the logs on the test VM I notice that C:\ drive is the 350mb partition and no other partition
has been made.
I have noticed something strange in my unattended file - Not sure why this line is last in the disk configuration part - I thought since I am wiping the disk and selecting disk 0 this would be at the start of the process. .
<DiskID>0</DiskID>
<WillWipeDisk>true</WillWipeDisk>
</Disk>
<WillShowUI>Never</WillShowUI>
</DiskConfiguration>
My full unattended file is below
<?xml version="1.0" encoding="utf-8"?>
< unattend xmlns="urn:schemas-microsoft-com:unattend">
<settings pass="windowsPE">
<component name="Microsoft-Windows-International-Core-WinPE" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS"
xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<SetupUILanguage>
<UILanguage>en-GB</UILanguage>
</SetupUILanguage>
<InputLocale>en-GB</InputLocale>
<SystemLocale>en-GB</SystemLocale>
<UILanguage>en-US</UILanguage>
<UILanguageFallback>en-GB</UILanguageFallback>
<UserLocale>en-GB</UserLocale>
</component>
<component name="Microsoft-Windows-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<DiskConfiguration>
<Disk wcm:action="add">
<CreatePartitions>
<CreatePartition wcm:action="add">
<Order>1</Order>
<Size>350</Size>
<Type>Primary</Type>
</CreatePartition>
<CreatePartition wcm:action="add">
<Order>2</Order>
<Type>Extended</Type>
<Extend>true</Extend>
</CreatePartition>
</CreatePartitions>
<ModifyPartitions>
<ModifyPartition wcm:action="add">
<Active>true</Active>
<Extend>false</Extend>
<Format>NTFS</Format>
<Label>Boot</Label>
<PartitionID>1</PartitionID>
<Order>1</Order>
</ModifyPartition>
<ModifyPartition wcm:action="add">
<Active>false</Active>
<Format>NTFS</Format>
<Label>System drive</Label>
<Order>2</Order>
<PartitionID>2</PartitionID>
<Extend>false</Extend>
<Letter>C</Letter>
</ModifyPartition>
</ModifyPartitions>
<DiskID>0</DiskID>
<WillWipeDisk>true</WillWipeDisk>
</Disk>
<WillShowUI>Never</WillShowUI>
</DiskConfiguration>
<ImageInstall>
<DataImage wcm:action="add">
<InstallTo>
<DiskID>0</DiskID>
<PartitionID>2</PartitionID>
</InstallTo>
<InstallFrom>
<Credentials>
<Domain>LABTEST</Domain>
<Password>Password01</Password>
<Username>Administrator</Username>
</Credentials>
<MetaData wcm:action="add">
<Key>/IMAGE/NAME</Key>
<Value>Windows Server 2012 R2 SERVERSTANDARD</Value>
</MetaData>
</InstallFrom>
<Order>1</Order>
</DataImage>
</ImageInstall>
<UserData>
<ProductKey>
<Key>CCCCCCCCCCC</Key>
<WillShowUI>OnError</WillShowUI>
</ProductKey>
<AcceptEula>true</AcceptEula>
</UserData>
<WindowsDeploymentServices>
<Login>
<Credentials>
<Domain>labtest</Domain>
<Password>Password01</Password>
<Username>Administrator</Username>
</Credentials>
</Login>
<ImageSelection>
<InstallImage>
<Filename>install-(2).wim</Filename>
<ImageGroup>Windows 2012 R2</ImageGroup>
<ImageName>Windows Server 2012 R2 SERVERSTANDARD</ImageName>
</InstallImage>
<InstallTo>
<DiskID>0</DiskID>
<PartitionID>1</PartitionID>
</InstallTo>
</ImageSelection>
</WindowsDeploymentServices>
</component>
</settings>
<settings pass="specialize">
<component name="Microsoft-Windows-Shell-Setup" processorArchitecture="amd64" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<ComputerName>Windows2012</ComputerName>
<ProductKey>CCCCCCCCCCCCCCCCCCCCCCCCCCC</ProductKey>
<TimeZone>GMT</TimeZone>
<ShowWindowsLive>false</ShowWindowsLive>
<RegisteredOrganization>labtest</RegisteredOrganization>
</component>
</settings>
<cpi:offlineImage cpi:source="wim://labtest-wds01/ewindows%20isos/windows%202012%20r2/install.wim#Windows Server 2012 R2 SERVERSTANDARD" xmlns:cpi="urn:schemas-microsoft-com:cpi" />
< /unattend>
My error logs
2016-11-02 23:33:32, Error [0x0b003a] WDS <GetNameInfo failed; status 0x8007276d>[gle=0x0000276d]
2016-11-02 23:33:32, Error [0x0b003a] WDS <GetNameInfo failed; status 0x8007276d>[gle=0x0000276d]
2016-11-02 23:33:32, Error [0x0b003a] WDS <GetNameInfo failed; status 0x8007276d>[gle=0x0000276d]
2016-11-02 23:33:32, Error [0x0b003a] WDS <GetNameInfo failed; status 0x8007276d>[gle=0x0000276d]
2016-11-02 23:33:32, Error [0x0b003a] WDS <GetNameInfo failed; status 0x8007276d>[gle=0x0000276d]
2016-11-02 23:33:32, Error [0x0b003a] WDS <GetNameInfo failed; status 0x8007276d>[gle=0x0000276d]
2016-11-02 23:33:32, Error [0x0b003a] WDS <GetNameInfo failed; status 0x8007276d>[gle=0x0000276d]
2016-11-02 23:33:32, Error [0x0b003a] WDS <GetNameInfo failed; status 0x8007276d>[gle=0x0000276d]
2016-11-02 23:33:32, Error [0x0b003a] WDS <GetNameInfo failed; status 0x8007276d>[gle=0x0000276d]
2016-11-02 23:33:48, Error [0x060495] IBS ValidateOperation:Couldn't find specified disk region on disk [0]
2016-11-02 23:33:54, Error [0x06048f] IBS CallBack_DiskConfiguration_ApplyUnattend:An error occurred while applying unattend disk configuration; hr = 0x80300002
AND MY OTHER LOG FILE (EDIT TO FIT) information.information.
2016-11-02 23:33:54, Info [0x0606cc] IBS DiskInfo:===== Disk number [0] =====
2016-11-02 23:33:54, Info [0x0606cc] IBS DiskInfo: Friendly name: [VMware Virtual disk SCSI Disk Device]
2016-11-02 23:33:54, Info [0x0606cc] IBS DiskInfo: Arc path: [multi(0)disk(0)rdisk(0)]
2016-11-02 23:33:54, Info [0x0606cc] IBS DiskInfo: Disk signature [0x5C750F0C]
2016-11-02 23:33:54, Info [0x0606cc] IBS DiskInfo: Size (bytes) [42949672960 / 0xa00000000]
2016-11-02 23:33:54, Info [0x0606cc] IBS DiskInfo: Sector size (bytes) [512]
2016-11-02 23:33:54, Info [0x0606cc] IBS DiskInfo: Disk bus type: [Serial Attached SCSI]
2016-11-02 23:33:54, Info [0x0606cc] IBS DiskInfo: SMART health status = UNKNOWN
2016-11-02 23:33:54, Info [0x0606cc] IBS DiskInfo: Container (extended) partition at {offset = [368050176], size = [42580574208]}
2016-11-02 23:33:54, Info [0x0606cc] IBS DiskInfo: Partition style: MBR
2016-11-02 23:33:54, Info [0x0606cc] IBS DiskInfo: 4 region(s), 2 partition(s), 2 toplevel partition(s)
2016-11-02 23:33:54, Info [0x0606cc] IBS DiskInfo: ------- Unallocated disk region --------
2016-11-02 23:33:54, Info [0x0606cc] IBS DiskInfo: Offset (bytes) [0 / 0x0]
2016-11-02 23:33:54, Info [0x0606cc] IBS DiskInfo: Size (bytes) [32256 / 0x7e00]
2016-11-02 23:33:54, Info [0x0606cc] IBS DiskInfo: ------- Unallocated disk region --------
2016-11-02 23:33:54, Info [0x0606cc] IBS DiskInfo: Offset (bytes) [32256 / 0x7e00]
2016-11-02 23:33:54, Info [0x0606cc] IBS DiskInfo: Size (bytes) [1016320 / 0xf8200]
2016-11-02 23:33:54, Info [0x0606cc] IBS DiskInfo: ------ NT partition number [1] -------
2016-11-02 23:33:54, Info [0x0606cc] IBS DiskInfo: Offset (bytes) [1048576 / 0x100000]
2016-11-02 23:33:54, Info [0x0606cc] IBS DiskInfo: Size (bytes) [367001600 / 0x15e00000]
2016-11-02 23:33:54, Info [0x0606cc] IBS DiskInfo: Simple index: [1]
2016-11-02 23:33:54, Info [0x0606cc] IBS DiskInfo: MBR partition type: 0x7 (recognized)
2016-11-02 23:33:54, Info [0x0606cc] IBS DiskInfo: Active partition bit is set
2016-11-02 23:33:54, Info [0x0606cc] IBS DiskInfo: DOS drive letter [C:]
2016-11-02 23:33:54, Info [0x0606cc] IBS DiskInfo: NT path: [\Device\HarddiskVolume2]
2016-11-02 23:33:54, Info [0x0606cc] IBS DiskInfo: File system type: [NTFS]
2016-11-02 23:33:54, Info [0x0606cc] IBS DiskInfo: File system version: [3:1]
2016-11-02 23:33:54, Info [0x0606cc] IBS DiskInfo: Volume label: [Boot]
2016-11-02 23:33:54, Info [0x0606cc] IBS DiskInfo: Volume flags = [0x80464]
2016-11-02 23:33:54, Info [0x0606cc] IBS DiskInfo: Volume free space (bytes) [336084992]
2016-11-02 23:33:54, Info [0x0606cc] IBS DiskInfo: ------- Unallocated disk region --------
2016-11-02 23:33:54, Info [0x0606cc] IBS DiskInfo: Offset (bytes) [368050176 / 0x15f00000]
2016-11-02 23:33:54, Info [0x0606cc] IBS DiskInfo: Size (bytes) [42580574208 / 0x9ea000000]
2016-11-02 23:33:54, Info [0x0606cc] IBS DiskInfo: Within extended partition
2016-11-02 23:33:54, Info [0x0606cc] IBS DiskInfo: Simple index: [2]
2016-11-02 23:33:54, Info [0x0606cc] IBS DiskInfo: MBR partition type: 0xF (not recognized)
2016-11-02 23:33:54, Info PublishDiskInfoOnBlackboard: Serializing disk info...
2016-11-02 23:33:54, Info [0x0606cc] IBS GetSystemDiskNTPath: Found system disk at [\Device\Harddisk0\DR0].
2016-11-02 23:33:54, Info [0x0606cc] IBS GetSystemDiskNumber: Disk [0] is the system disk.
2016-11-02 23:33:54, Info IBS IsDiskSupported:Checking if disk [0] has the necessary driver support.
2016-11-02 23:33:54, Info IBS IsDeviceSupported:Device description is [Disk drive]
2016-11-02 23:33:54, Info IBS DumpDeviceIDs: H/w ID [SCSI\DiskVMware__Virtual_disk____1.0_]
2016-11-02 23:33:54, Info IBS DumpDeviceIDs: H/w ID [SCSI\DiskVMware__Virtual_disk____]
2016-11-02 23:33:54, Info IBS DumpDeviceIDs: H/w ID [SCSI\DiskVMware__]
2016-11-02 23:33:54, Info IBS DumpDeviceIDs: H/w ID [SCSI\VMware__Virtual_disk____1]
2016-11-02 23:33:54, Info IBS DumpDeviceIDs: H/w ID [VMware__Virtual_disk____1]
2016-11-02 23:33:54, Info IBS DumpDeviceIDs: H/w ID [GenDisk]
2016-11-02 23:33:54, Info IBS DumpDeviceIDs: Compat ID [SCSI\Disk]
2016-11-02 23:33:54, Info IBS DumpDeviceIDs: Compat ID [SCSI\RAW]
2016-11-02 23:33:54, Info IBS IsDeviceIDPresent:Found device ID [GenDisk] in hwcompat list
2016-11-02 23:33:54, Info IBS IsDeviceSupported:Device [Disk drive] is supported
2016-11-02 23:33:54, Info IBS IsDeviceSupported:Device description is [LSI Adapter, SAS 3000 series, 8-port with 1068]
2016-11-02 23:33:54, Info IBS DumpDeviceIDs: H/w ID [PCI\VEN_1000&DEV_0054&SUBSYS_197615AD&REV_01]
2016-11-02 23:33:54, Info IBS DumpDeviceIDs: H/w ID [PCI\VEN_1000&DEV_0054&SUBSYS_197615AD]
2016-11-02 23:33:54, Info IBS DumpDeviceIDs: H/w ID in hwcompat list
2016-11-02 23:33:54, Info IBS IsDeviceSupported:Device [LSI Adapter, SAS 3000 series, 8-port with 1068] is supported
2016-11-02 23:33:54, Info IBS IsDeviceSupported:Device description is [PCI Express standard Root Port]
2016-11-02 23:33:54, Info IBS DumpDeviceIDs: H/w ID [PCI\VEN_15AD&DEV_07A0&SUBSYS_07A015AD&REV_01]
2016-11-02 23:33:54, Info IBS DumpDeviceIDs: H/w ID [PCI\VEN_15AD&DEV_07A0&SUBSYS_07A015AD]
2016-11-02 23:33:54, Info IBS DumpDeviceIDs: H/w ID [PCI\VEN_15AD&DEV_07A0&CC_060400]
2016-11-02 23:33:54, Info IBS DumpDeviceIDs: H/w ID [PCI\VEN_15AD&DEV_07A0&CC_0604]
2016-11-02 23:33:54, Info IBS DumpDeviceIDs: Compat ID [PCI\VEN_15AD&DEV_07A0&REV_01]
2016-11-02 23:33:54, Info IBS DumpDeviceIDs: Compat ID [PCI\VEN_15AD&DEV_07A0]
2016-11-02 23:33:54, Info IBS DumpDeviceIDs: Compat ID [PCI\VEN_15AD&CC_060400]
2016-11-02 23:33:54, Info IBS DumpDeviceIDs: Compat ID [PCI\VEN_15AD&CC_0604]
2016-11-02 23:33:54, Info IBS DumpDeviceIDs: Compat ID [PCI\VEN_15AD]
2016-11-02 23:33:54, Info IBS DumpDeviceIDs: Compat ID [PCI\CC_060400&DT_4]
2016-11-02 23:33:54, Info IBS DumpDeviceIDs: Compat ID [PCI\CC_060400]
2016-11-02 23:33:54, Info IBS DumpDeviceIDs: Compat ID [PCI\CC_0604&DT_4]
2016-11-02 23:33:54, Info IBS DumpDeviceIDs: Compat ID [PCI\CC_0604]
2016-11-02 23:33:54, Info IBS IsDeviceIDPresent:Found device ID [PCI\CC_0604&DT_4] in hwcompat list
2016-11-02 23:33:54, Info IBS IsDeviceSupported:Device [PCI Express standard Root Port] is supported
2016-11-02 23:33:54, Info IBS IsDeviceSupported:Device description is [PCI bus]
2016-11-02 23:33:54, Info IBS DumpDeviceIDs: H/w ID [ACPI\VEN_PNP&DEV_0A03]
2016-11-02 23:33:54, Info IBS DumpDeviceIDs: H/w ID [ACPI\PNP0A03]
2016-11-02 23:33:54, Info IBS DumpDeviceIDs: H/w ID [*PNP0A03]
2016-11-02 23:33:54, Info IBS DumpDeviceIDs: Compat ID [*PNP0A08]
2016-11-02 23:33:54, Info IBS IsDeviceIDPresent:Found device ID [*PNP0A03] in hwcompat list
2016-11-02 23:33:54, Info IBS IsDeviceSupported:Device [PCI bus] is supported
2016-11-02 23:33:54, Info IBS IsDeviceSupported:Device description is [Microsoft ACPI-Compliant System]
2016-11-02 23:33:54, Info IBS DumpDeviceIDs: H/w ID [ACPI_HAL\PNP0C08]
2016-11-02 23:33:54, Info IBS DumpDeviceIDs: H/w ID [*PNP0C08]
2016-11-02 23:33:54, Info IBS IsDeviceIDPresent:Found device ID [*PNP0C08] in hwcompat list
2016-11-02 23:33:54, Info IBS IsDeviceSupported:Device [Microsoft ACPI-Compliant System] is supported
2016-11-02 23:33:54, Info IBS IsDeviceSupported:Device description is [ACPI x64-based PC]
2016-11-02 23:33:54, Info IBS DumpDeviceIDs: H/w ID [acpiapic]
2016-11-02 23:33:54, Info IBS DumpDeviceIDs: Compat ID [DETECTEDInternal\ACPI_HAL]
2016-11-02 23:33:54, Info IBS DumpDeviceIDs: Compat ID [DETECTED\ACPI_HAL]
2016-11-02 23:33:54, Info IBS IsDeviceIDPresent:Found device ID [acpiapic] in hwcompat list
2016-11-02 23:33:54, Info IBS IsDeviceSupported:Device [ACPI x64-based PC] is supported
2016-11-02 23:33:54, Info IBS DetermineDeviceSupport:Disk 0 has the necessary driver support
2016-11-02 23:33:54, Info PublishDiskInfoOnBlackboard: Successfully serialized disk info.
2016-11-02 23:33:54, Error [0x06048f] IBS CallBack_DiskConfiguration_ApplyUnattend:An error occurred while applying unattend disk configuration; hr = 0x80300002
2016-11-02 23:33:54, Info [0x0640ae] IBSLIB PublishMessage: Publishing message [Windows could not apply the unattend answer file's <DiskConfiguration> setting.]
2016-11-02 23:33:54, Info [0x0a013d] UI Accepting Cancel. Exiting Page Waiting for Server.
2016-11-02 23:33:54, Info UI Entering Page Cancel.
2016-11-02 23:33:54, Info [0x0a0035] UI Allowing Page 'Waiting for Server' to be shown
2016-11-02 23:33:54, Info [0x0a0035] UI Allowing Page 'Waiting for Server' to be shown
2016-11-02 23:33:54, Info [0x0a011c] UI WizardDialogPost::SetActive
Hi Everyone,
am trying to install windows update on my DC windows server 2008 R2. i have logged on using domain admin account and i am trying to install windows update on the DC machines but all the updates are not getting install.
i tried to stop and start windows update services but still unable to get this success.
please help to give guideline to know the cause and resolve the windows update issue.
srini
H All, I need some help.
This may not be the correct place for this but I'll give it a go!!
Physical machine with two physical processors, Xeon E5-2609v3 6-Core, so 12 Cores in total
if one was to install VMware ESXi and create two virtual machines using 50% of processors (6 CPU's) and all other resources, then install Microsoft server 2016 in each virtual machine.
bringing me to the question, what MS software/licencing do I need to purchase, with SKU's please?
Many thanks in advance.
I seem to recall (from a previous painful episode) that if you are backing up Windows Server 2008 with Server Backup; and you change the physical properties of a volume on a hard disk (change the size) then Server Backup resets - it wipes the old backup database and starts again. I want to do this again (change the size of two of the volumes) so if I remove the current backup disk using the wizard; then add a new one; will I still be able to access all the files from the old drive from within the program? Thanks for your time -it's much appreciated.
I have Exchange 2010 running on Win 2008 R2 Server, 64Bit.
I cannot open command prompt, dns, dxdiag, IIS etc. The following error appears every time:-
"The version of this file is not compatible with the version of windows you are running. Check your
computer's system information to see whether you need an x86 (32 bit) or x64 (64 Bit) version of the program and then contact the software publisher."
I have uninstalled some windows update, rebooted the server, initialized chckdsk but no change.
Some exchange 2010 tools from the TOOLBOX are not functioning as well, namely queue viewer and mail flow troubleshooter, even though a different error is displayed, i believe its something to do with the OS.
Kindly advice
schtasks /query /FO CSV | ConvertFrom-CSV | select TaskName
and will show
TaskName
-----------
\mytask
How do trim the "\" character?
The last couple of days an application which connects to a certain SSRS server on port 80 results in a lot of error messages.
Source system is W2K8 R2 with 16 Gb RAM.
MaxUserPort setting is 2024
In the application log it shows several connection problems:
An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full x.x.x.x:80
All refering to the SSRS server.
How to solve this problem, simple reboot?
I will add a screenshot once i am verified, but I have an SBS 2008 server throwing up "The server is not operational" everytime trying to reach and A/D integrated services.
Have followed the steps in similar forum post here: https://social.technet.microsoft.com/Forums/windowsserver/en-US/e7f23fce-ef57-47c7-a7fc-2b0dbdf97c36/windows-server-2008-server-in-not-operational?forum=winservergen
Will atatched dcdiag once this post is verified... hopefully someone can help in this becasue I can be restarting the server every 9-10hours to fix this issue.
results of sc query:
Microsoft Windows [Version 6.0.6002]Thanks
I've found various links on Microsoft's web site similar to the following: https://blogs.technet.microsoft.com/rmilne/2014/07/24/save-the-date-end-of-exchange-2010-windows-7-and-2008-mainstream-support-t-minus-6-months/
That lists various 2008 server versions but NOT standard. I've also found web pages similar to the following
or https://support.microsoft.com/en-us/lifecycle/search?sort=PN&alpha=Windows%20Server%202008&Filter=FilterNO, which says:
"See the latest Service Pack listing for this product for the end of support dates."
Is this last date for extended support in 2020? Thank you.