Unexpected reboot Windows 2008 R2 server caused by PROCEXP111. SYS

The computer was restarted after a bugcheck.  The bugcheck was: 0 x 00000050 (0xfffffa80bd8dc050, 0 x 0000000000000000, 0xfffff88008072ddd, 0 x 0000000000000000). A dump was saved in the: C:\Windows\Minidump\052313-36332-01.dmp. Report ID: 052313-36332-01.

Report of the debugger:

Microsoft (R) Windows debug 6.12.0002.633 AMD64 Version
Copyright (c) Microsoft Corporation. All rights reserved.
Loading dump file [C:\Windows\Minidump\052313-36332-01.dmp]
The mini kernel dump file: only registers and the trace of the stack are available
Symbol search path is: * invalid *.
****************************************************************************
* Loading of the symbol may be unreliable without a symbol search path.           *
* Use .symfix to get the debugger to choose a symbol path.                   *
* After adjusting your path to symbols, use .reload to refresh the locations of symbols. *
****************************************************************************
Executable search path is:
*********************************************************************
* Symbols cannot be loaded because the path is not initialized. *
*                                                                   *
* The symbol path can be defined: *.
* using the _NT_SYMBOL_PATH environment variable.                 *
* using the o - argument when starting the debugger. *
* using the .sympath and .sympath + *.
*********************************************************************
Could not load the ntoskrnl.exe, 0n2 error Win32 image
WARNING: Unable to verify timestamp for ntoskrnl.exe
ERROR: Module load completed but symbols can be loaded for ntoskrnl.exe
Windows 7 Kernel Version 7601 (Service Pack 1) MP (24 procs) free x 64
Product: Server, suite: TerminalServer SingleUserTS Enterprise
Computer name:
Kernel base = 0xfffff800 '01a1d000 PsLoadedModuleList = 0xfffff800' 01b 61670
The debugging session: 17:52:43.775 Thu May 23, 2013 (UTC + 10:00)
System Uptime: 118 days 1:53:41.084
*********************************************************************
* Symbols cannot be loaded because the path is not initialized. *
*                                                                   *
* The symbol path can be defined: *.
* using the _NT_SYMBOL_PATH environment variable.                 *
* using the o - argument when starting the debugger. *
* using the .sympath and .sympath + *.
*********************************************************************
Could not load the ntoskrnl.exe, 0n2 error Win32 image
WARNING: Unable to verify timestamp for ntoskrnl.exe
ERROR: Module load completed but symbols can be loaded for ntoskrnl.exe
Loading the kernel symbols
...............................................................
................................................................
..................
Loading user symbols
Loading unloaded module list
..................................................
*******************************************************************************
*                                                                             *
* Bugcheck analysis *.
*                                                                             *
*******************************************************************************
Use
! analyze - v to obtain detailed debugging information.
Bugcheck 50, {fffffa80bd8dc050, 0, fffff88008072ddd, 0}
The kernel symbols are FALSE. Correct symbols to do the analysis.
*************************************************************************
***                                                                   ***
***                                                                   ***
Your debugger is not using the appropriate symbols *.
***                                                                   ***
In order for this command works correctly, your symbol path *.
should point to .pdb files have the type information complete.      ***
***                                                                   ***
Some (such as the public OS symbols) .pdb files are not *.
contain the required information.  The contact group that *.
you provided with these symbols, if you need this command for *.
work.                                                          ***
***                                                                   ***
Type referenced: nt! _KPRCB *.
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
Your debugger is not using the appropriate symbols *.
***                                                                   ***
In order for this command works correctly, your symbol path *.
should point to .pdb files have the type information complete.      ***
***                                                                   ***
Some (such as the public OS symbols) .pdb files are not *.
contain the required information.  The contact group that *.
you provided with these symbols, if you need this command for *.
work.                                                          ***
***                                                                   ***
Type referenced: nt
! KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
Your debugger is not using the appropriate symbols *.
***                                                                   ***
In order for this command works correctly, your symbol path *.
should point to .pdb files have the type information complete.      ***
***                                                                   ***
Some (such as the public OS symbols) .pdb files are not *.
contain the required information.  The contact group that *.
you provided with these symbols, if you need this command for *.
work.                                                          ***
***                                                                   ***
Type referenced: nt
! _KPRCB *.
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
Your debugger is not using the appropriate symbols *.
***                                                                   ***
In order for this command works correctly, your symbol path *.
should point to .pdb files have the type information complete.      ***
***                                                                   ***
Some (such as the public OS symbols) .pdb files are not *.
contain the required information.  The contact group that *.
you provided with these symbols, if you need this command for *.
work.                                                          ***
***                                                                   ***
Type referenced: nt
! KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
Your debugger is not using the appropriate symbols *.
***                                                                   ***
In order for this command works correctly, your symbol path *.
should point to .pdb files have the type information complete.      ***
***                                                                   ***
Some (such as the public OS symbols) .pdb files are not *.
contain the required information.  The contact group that *.
you provided with these symbols, if you need this command for *.
work.                                                          ***
***                                                                   ***
Type referenced: nt! _KPRCB *.
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
Your debugger is not using the appropriate symbols *.
***                                                                   ***
In order for this command works correctly, your symbol path *.
should point to .pdb files have the type information complete.      ***
***                                                                   ***
Some (such as the public OS symbols) .pdb files are not *.
contain the required information.  The contact group that *.
you provided with these symbols, if you need this command for *.
work.                                                          ***
***                                                                   ***
Type referenced: nt
!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
Cannot load the image PROCEXP111. SYS, 0n2 error Win32
WARNING: Unable to verify timestamp for PROCEXP111. SYS
ERROR: Module load completed but symbols can not be loaded for PROCEXP111. SYS
*************************************************************************
***                                                                   ***
***                                                                   ***
Your debugger is not using the appropriate symbols *.
***                                                                   ***
In order for this command works correctly, your symbol path *.
should point to .pdb files have the type information complete.      ***
***                                                                   ***
Some (such as the public OS symbols) .pdb files are not *.
contain the required information.  The contact group that *.
you provided with these symbols, if you need this command for *.
work.                                                          ***
***                                                                   ***
Type referenced: nt! _KPRCB *.
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
Your debugger is not using the appropriate symbols *.
***                                                                   ***
In order for this command works correctly, your symbol path *.
should point to .pdb files have the type information complete.      ***
***                                                                   ***
Some (such as the public OS symbols) .pdb files are not *.
contain the required information.  The contact group that *.
you provided with these symbols, if you need this command for *.
work.                                                          ***
***                                                                   ***
Type referenced: nt! _KPRCB *.
***                                                                   ***
*************************************************************************
Probably caused by: PROCEXP111. SYS (PROCEXP111 + 1ddd)
Follow-up: MachineOwner
---------
8: kd >
! analyze - v
*******************************************************************************
*                                                                             *
* Bugcheck analysis *.
*                                                                             *
*******************************************************************************
PAGE_FAULT_IN_NONPAGED_AREA (50)
Invalid system memory was referenced.  This cannot be protected by try-except,
It must be protected by a probe.  In general, the address is simple bad or it
pointing to freed memory.
Arguments:
Arg1: fffffa80bd8dc050, memory referenced.
Arg2: 0000000000000000, value 0 = read operation, 1 = write operation.
Arg3: fffff88008072ddd, if not zero, the address of the instruction that refers to bad memory
address.
Arg4: 0000000000000000, (reserved)
Debugging information:
------------------
The kernel symbols are FALSE. Correct symbols to do the analysis.
*************************************************************************
***                                                                   ***
***                                                                   ***
Your debugger is not using the appropriate symbols *.
***                                                                   ***
In order for this command works correctly, your symbol path *.
should point to .pdb files have the type information complete.      ***
***                                                                   ***
Some (such as the public OS symbols) .pdb files are not *.
contain the required information.  The contact group that *.
you provided with these symbols, if you need this command for *.
work.                                                          ***
***                                                                   ***
Type referenced: nt
!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
Your debugger is not using the appropriate symbols *.
***                                                                   ***
In order for this command works correctly, your symbol path *.
should point to .pdb files have the type information complete.      ***
***                                                                   ***
Some (such as the public OS symbols) .pdb files are not *.
contain the required information.  The contact group that *.
you provided with these symbols, if you need this command for *.
work.                                                          ***
***                                                                   ***
Type referenced: nt
! KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
Your debugger is not using the appropriate symbols *.
***                                                                   ***
In order for this command works correctly, your symbol path *.
should point to .pdb files have the type information complete.      ***
***                                                                   ***
Some (such as the public OS symbols) .pdb files are not *.
contain the required information.  The contact group that *.
you provided with these symbols, if you need this command for *.
work.                                                          ***
***                                                                   ***
Type referenced: nt
!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
Your debugger is not using the appropriate symbols *.
***                                                                   ***
In order for this command works correctly, your symbol path *.
should point to .pdb files have the type information complete.      ***
***                                                                   ***
Some (such as the public OS symbols) .pdb files are not *.
contain the required information.  The contact group that *.
you provided with these symbols, if you need this command for *.
work.                                                          ***
***                                                                   ***
Type referenced: nt! KPRCB                                      ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
Your debugger is not using the appropriate symbols *.
***                                                                   ***
In order for this command works correctly, your symbol path *.
should point to .pdb files have the type information complete.      ***
***                                                                   ***
Some (such as the public OS symbols) .pdb files are not *.
contain the required information.  The contact group that *.
you provided with these symbols, if you need this command for *.
work.                                                          ***
***                                                                   ***
Type referenced: nt
!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
Your debugger is not using the appropriate symbols *.
***                                                                   ***
In order for this command works correctly, your symbol path *.
should point to .pdb files have the type information complete.      ***
***                                                                   ***
Some (such as the public OS symbols) .pdb files are not *.
contain the required information.  The contact group that *.
you provided with these symbols, if you need this command for *.
work.                                                          ***
***                                                                   ***
Type referenced: nt! _KPRCB *.
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
Your debugger is not using the appropriate symbols *.
***                                                                   ***
In order for this command works correctly, your symbol path *.
should point to .pdb files have the type information complete.      ***
***                                                                   ***
Some (such as the public OS symbols) .pdb files are not *.
contain the required information.  The contact group that *.
you provided with these symbols, if you need this command for *.
work.                                                          ***
***                                                                   ***
Type referenced: nt
!_KPRCB                                     ***
***                                                                   ***
*************************************************************************
*************************************************************************
***                                                                   ***
***                                                                   ***
Your debugger is not using the appropriate symbols *.
***                                                                   ***
In order for this command works correctly, your symbol path *.
should point to .pdb files have the type information complete.      ***
***                                                                   ***
Some (such as the public OS symbols) .pdb files are not *.
contain the required information.  The contact group that *.
you provided with these symbols, if you need this command for *.
work.                                                          ***
***                                                                   ***
Type referenced: nt
! _KPRCB *.
***                                                                   ***
*************************************************************************
ADDITIONAL_DEBUG_TEXT:
Use '! findthebuild' command to search for the generation of target information.
If the build information is available, run '! findthebuild s; .reload ' to set the symbol path and of loading symbols.
FAULTING_MODULE: fffff80001a1d000 nt
DEBUG_FLR_IMAGE_TIMESTAMP: 47194089
READ_ADDRESS: could not get nt! MmSpecialPoolStart
Unable to get nt! MmSpecialPoolEnd
Unable to get nt! MmPoolCodeStart
Unable to get nt
! MmPoolCodeEnd
fffffa80bd8dc050
FAULTING_IP:
PROCEXP111 + 1ddd
fffff880'08072ddd 66833805 cmp word ptr [rax], 5
MM_INTERNAL_CODE: 0
CUSTOMER_CRASH_COUNT: 1
DEFAULT_BUCKET_ID: DRIVER_FAULT_SERVER_MINIDUMP
BUGCHECK_STR: 0 X 50
CURRENT_IRQL: 0
LAST_CONTROL_TRANSFER: from fffff80001a43eec to fffff80001a9bfc0
STACK_TEXT:
fffff880 '06-60348 fffff800' 01a43eec: 00000000'00000050 fffffa80 'bd8dc050 00000000 00000000' fffff880' 06a604b0: nt + 0x7efc0
fffff880 '06 a 60350 00000000' 00000050: fffffa80 'bd8dc050 00000000 00000000' fffff880' 06a604b0 00000000' 00000000: nt + 0x26eec
fffff880 '06-60358 fffffa80' bd8dc050: 00000000 00000000' fffff880 '06a604b0 00000000 00000000' fffffa80' 7d2c61d0: 0 x 50
fffff880'06 has 60360 00000000 00000000': fffff880 '06a604b0 00000000 00000000' fffffa80' 7d2c61d0 00000000' 00000000: 0xfffffa80'bd8dc050
STACK_COMMAND: .bugcheck; Ko
FOLLOWUP_IP:
PROCEXP111 + 1ddd
fffff880'08072ddd 66833805 cmp word ptr [rax], 5
SYMBOL_NAME: PROCEXP111 + 1ddd
FOLLOWUP_NAME: MachineOwner
MODULE_NAME: PROCEXP111
NOM_IMAGE: PROCEXP111. SYS
BUCKET_ID: WRONG_SYMBOLS
Follow-up: MachineOwner
---------

Hello

Support for Windows Server is not provided in these forums. On the other hand, it please repost your question in the relevant Microsoft TechNet forum here:

http://social.technet.microsoft.com/Forums/en-us/category/windowsserver .

Thank you.      :)

Tags: Windows

Similar Questions

  • Windows 2008 R2 server slow printing

    We have about 5-6 servers Windows 2008 R2 in our virtual machine environment.  All of these servers are servers very low utilization, and they all work very well.  We have a few domain controllers, a SQL box and a few boxes of web application that is running IIS.  One of these domain controllers is a print server.  The print server works well, but it is very slow.  If you right-click on any printer that is added to any of the customers and go to properties, where the server is the management of print server, the client must wait 30 seconds or more for the upcoming dialog with the properties.  You can click between tabs, but the legs are also slow to react.

    This means that if you make changes to the print job or the margins, for example, it may take a minute of waiting between screens.

    Now, we had a physical Windows 2000 print server that has worked well until we got the VM environment, so I know the problem is in one of a few different areas.

    1. it could be the VM environment.

    2. it may be Windows 2008 R2 server config or the server software itself.

    3 might be x 64 bit cause a problem with 32-bit clients using the box.

    I have excluded #3 by a 32 bit 2008 Server on the VM environment of loading, loading of print management and then by loading a single printer and share it.  The problem is still there on the current server.  My next step is to try Windows 2003 server in virtual machine environment, but before I do, I want to throw this question very curious to the VMWare community.  All I have to do before moving on to more drastic measures?  There must be something I can do to solve the problem.

    Maybe it's the solution.  Will test:

    http://support.Microsoft.com/kb/979394

  • Disabling RC4 encryption in the Windows 2008 SP2 Server

    Hello

    I just saw through the 2868725 Ko to disable the RC4.

    According to the article, we need to install the KB update, then we need to change the values of registry keys to disable the RC4.

    However, I could not find the download for the Windows 2008 SP2 server file in the download link

    https://support.Microsoft.com/en-us/KB/2868725

    Any suggestion how to disable the RC4 in Windows 2008 SP2.

    Need help.

    Thanks in advance.

    Here is the link for the Microsoft TechNet forum:
    http://social.technet.Microsoft.com/forums/en-us/home?Forum=w7itpronetworking

    Several related to the server forum (not for Desktop/Win7)https://social.technet.microsoft.com/Forums/windowsserver/en-us/home?category=windowsserver

  • Windows 2008 storage server shows 0 KB file size

    We use Windows 2008 storage server standard with Service Pack 2. Now we are facing the issue is Some of PDF, EXCEL, DOC files show in size 0 KB file, we are unable to open this type of file, if anyone knows pl give me the solution

    Hello

    I suggest you to ask your question on the link mentioned below that this forum is best suited for your question.

    http://social.technet.Microsoft.com/forums/en-us/w7itpronetworking/

    I hope this helps!

  • My computer is connected to the Windows 2008 R2 server and some of the users on this computer receive their network drive mapped on group policy and some do not.

    My computer is connected to the Windows 2008 R2 server and some of the users on this computer receive their network drive mapped on group policy and some do not.  I find nothing in Event Viewer that shows that there is a problem.  Please let me know what to do to get the disks appears

    Original title: Network Networking file sharing file sharing file sharing file sharing discovery sharing Fileshare share shared

    Hi,

    The question you posted would be better suited in the TechNet Forums. I would recommend posting your query in the TechNet Forums.

    TechNet Forum

    http://social.technet.Microsoft.com/forums/en-us/category/WindowsServer

     

    Hope this information helps.

  • After a PtoV for a Windows 2008 R2 server, a disc is not visible

    Hello

    I just used the converter to make a PtoV for a Windows 2008 R2 server with 2 drives and the C: drive is there but the D: drive is not while there are several devices CD/DVD virtual results.

    In the converter D: drive has been cloned successfully and it is visible in the data store.

    Tahnk you for your help.

    Concerning

    Daniel

    You must check your "Disk Managment" for your disks and their mount points. HTH

  • Manager Update 4 will not scan or clean up the Windows 2008 R2 server

    I just install a Windows 2008 R2 server, and Update Manager will not analyze it.  It just says: "Failed to scan or clean up SERVERNAME because of operating system not supported or unknown.  I can scan and clean up my plain Windows 2008 servers very well.  R2 is still not supported?

    I do not remember R2 being in the list of supported operating systems, I believe that this is also the case for the 4.0u1 VUM or VUM 4.0u1.1

    You'll probably want to make sure that the release notes, but if the error message says that it is not taken in charge, probably only is not supported.

    =========================================================================

    William Lam

    VMware vExpert 2009

    Scripts for VMware ESX/ESXi and resources at: http://engineering.ucsb.edu/~duonglt/vmware/

    Twitter: @lamw

    repository scripts vGhetto

    Introduction to the vMA (tips/tricks)

    Getting started with vSphere SDK for Perl

    VMware Code Central - Scripts/code samples for developers and administrators

    VMware developer community

    If you find this information useful, please give points to "correct" or "useful".

  • VMware Server on Windows 2008 R2 Server Core installation

    Hi guys!

    I installed the latest version of Vmware server on our new Windows 2008 R2 Server core installation, but I have a problem with it. When I create a virtual computer and try to start the Web UI:

    General system error occurred: unable to connect to the virtual machine

    Do you know something about the nature of this message? The Server service not had access to the possuble vitrual machine? But how can it create if it doesn't have access? I have not found the log files created in the folder of the virtual machine.

    Thank you for your help.

    Kind regards

    Jeremy

    I think that Server Core is an unsupported operating system. Please take a look at http://www.vmware.com/pdf/vmserver2.pdf (page 25)

    concerning

    Jose Ruelas B

    http://aservir.WordPress.com

  • Can I install Windows 2008 R2 Server on a PowerEdge 2850 Server?

    I have a PowerEdge 2850 server, that when he was initially put in place (by someone else) had Windows 2003 R2 top.  However, when they put in place, the partitioned the C: drive with so little space that it is running out of space.  We got a newer Dell server and I turned that 2850 off the coast.  It was interrupted for a month or two.

    But I would like to use it as a backup of database server.  Can I install Windows 2008 R2 Server on a PowerEdge 2850 Server?

    You need to install RAID drivers during the installation of 2008R2.

    1. Configure and initialize the RAID in the CTRL-M utility.
    2. Download and extract the drivers put on USB (or CD).
    3. Start on media 2008R2.
    4. On the screen that asks you where you want to install Windows, click on load a driver link at the bottom left.
    5. Navigate to the location of the RAID drivers.
    6. Choose the drive to install, then install.

  • Problem of ThinApp IE9 for Windows 2008 R2 Server Citrix

    Hello

    I'm trying to make a package for IE9 I'll be able to run on Server 2008 R2 running Citrix 6.5

    so I made this package by installing a windows 7 ent vm workstation and I capture the IE9

    now on this virtual machine with windows 7, this package work very well and also on my pc running windows 2008 R2 it also work correctly

    but when I try to run on no matter which of my new citrix servers open IE9, and then it shows this error popup:

    "A display problem (page name) caused Internet Explorer Refresh the Web page.

    and then freeze IE9. (this happen for IE9 32-bit and 64-bit, my servers are all 64-bit)

    now, I'm working on it for a week now and I have googled all the net and I found every article I can find on this error

    and I have tried everything with no success

    now, the only difference between my PCs running on windows 2008 R2, and Citrix servers are that my pc is a physical pc running Intel i5

    and all my citrix servers running on Vmware esxi 5.1 platform and I don't put all windows update install on my pc and I have Citrix install all updates from Microsoft.

    So it can be a hardware problem in the context of the article I found say that it may be related to the video card driver, but if this is the case how it works on the virtual machine with windows 7 running on the same server esxi

    and it can also be an update from Microsoft that makes this problem or it may be something that I don't think and that I need your help

    the IE9 which are installed on my citrix server run ok and there I have no problem but the IE9 in the package I build gives me this error

    one more strange thing is that in my package I didn't enter any home page and when I run this package it take home page I put in the local server as my homepage

    I also build a package for IE7 and present a work very well and there it didn't happen for me that the homepage on the server has been set as my package's home page.

    now, I'm trying to build this package as insulated and uninsulated and it made no difference regarding my problem, or to the homepage that originate from the local server.

    so I need some help here, and I need it ASAP

    Thank you

    Your

    Tamir

    Hello

    I found the cause of my problem, after all the test I did has been updated to Microsoft KB 2670838

    who get the users name in the net as the WRONG UPDATE

    See here: http://answers.microsoft.com/en-us/windows/forum/windows_7-windows_update/kb-2670838-the-evil-update/08bfdb2b-6896-4c34-89c2-16896a25dc3d

    After I remove this update that are not at all necessary and is also define who you just have it as a prerequisite for upgrading IE to version 10

    IE9 begin to work my package.

    So if someone of you will have a problem with IE9 and time does take to load pages remove this update.

    Tamir

  • Windows Server 2003 in a Windows 2008 file server environment

    Dear all,

    I would like to install windows 2003 server as a file server in Windows 2008 R2 domain.

    I have windows 2012 standard R2 in the additional DC form.

    Please advice me good measures implement the file server in our network.

    Tony

    E-mail address is removed from the privacy *.

    Hello

    Post your question in the TechNet Server Forums, as your question kindly is beyond the scope of these Forums.

    http://social.technet.Microsoft.com/forums/WindowsServer/en-us/home?category=WindowsServer

    See you soon.

  • Windows 2008 R2 server is not displayed the second hard disk

    Hello

    We have two windows 2008 R2 servers. In what we have, two hard drive and with 130GB storage capacity. But it displays only 130GB is available. Seems like the second hard disk not recognized.

    What can be done to clear this?

    Hello

    Post your question in the TechNet Server Forums, as your question kindly is beyond the scope of these Forums.

    http://social.technet.Microsoft.com/forums/WindowsServer/en-us/home?category=WindowsServer

    See you soon.

  • Why Windows 2008 R2 Server Foundation has received limited permissions?

    I install a software of SAP on a Microsoft Windows Server 2008 R2 Server (Foundation Edition) on a HP Proliant server.

    The installation fails to access to the registry key 'HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servi '.

    The exact error message is "unable to open silsvc. An error prevents opening this key. Details: access denied. »

    When to use REGEDIT. EXE to display the registration key, it reports that access is denied to view properties (not to mention changing permissions).

    Why this registry key entry is locked against the administrator?

    What can I open as long as the user TrustedInstaller?

    Alternative workaround?

    Concerning

    Joe Oppenheim

    Hello joppenheim,

    You question would best address in TechNet for the Windows Server 2008 forum.
    Click here for a link to transfer your question in the TechNet forum.

    They have Windows Server experts who will be able to help with your problem.

    Thank you

    Marilyn

  • Reg: configuration of mail in windows 2008 srever Server

    I have install or configure the mail server in windows server 2008. I have to configure the mail server and to create user accounts.

    can you please provide me with any documentation available for the same thing.
    : Hp ml110g7 Server
    OS: Windows 2008 Server

    Hello

    Thank you for visiting the Microsoft answers community site. The question you have posted is related to Windows Server and would be better suited to the TechNet community.

    Please visit the link below to find a community that will provide the support you want.

    http://social.technet.Microsoft.com/forums/en-us/category/WindowsServer

     

    I hope this helps.

  • Windows could not start the service on the Local computer Windows event log. Windows 2008 R2 server

    When I try to start the event log service can I have on my server (Windows 2008 R2), I get the following error:

    "Windows didn't start the service on the Local computer Windows event log."

    Error 2: the system cannot find the specified file. »

    Hello

    Your question of Windows is more complex than what is generally answered in the Microsoft Answers forums. It is better suited for the public on the TechNet site. Please post your question in the below link: http://social.technet.microsoft.com/Forums/en/category/windowsserver/

Maybe you are looking for

  • Boot Fail, Kernel Panic all the time.

    My Mac Pro early 2008 does not start I have constantly to the kernel with the usual panic ""you must restart your computer. " Hold down the Power button for a few seconds or press the restart... in 4 languages. Start Up Manager all my Bootable drive

  • How to find the URL of the public website of Photostream?

    Within iOS a shared link to find the "Internet site" for a photo gallery album.  How this is achieved in Photos?

  • AO722 hard drive firmware update

    I have a netbook Acer AO722-0022.  On site downloads Web of Acer support page, at the bottom of the BIOS downloads section, an update of the firmware "to improve the performance of the hard disk" is listed.  The inscription is "WD version 9545" suppl

  • Windows 7 on HP Elitebook notebook. Upgrade to windows 10

    Windows 7 on HP Elitebook notebook. Upgrade to windows 10 is provided to the extent of 10 windows startup but ends with error 0xC1900101 - 0 x 20017 down in the SAFE_OS phase with an error during the START operation. Tried twice, the onr with firewal

  • Recovery drive D is complete after one backup

    I have an Inspiron 1720 purchased in November 2007.  The hard drive is 220 GB on which 165 GB are free.  And the restoration of the C drive part is 10 GB.  The computer is configured to make monthly backups and only of emails, documents and backup im