Windows Server 2012 Hangs After a While

Good day,
My server hangs after a while then I have to hard boot it. I get the error 'Online data retrieval occurs under all my roles. Once I reboot it then the error disappears.
Please help!!
Thanks,
Mao

First of all, you would need to make sure that your server meets the hardware requirements to run Windows Server 2012 + the applications you use.
For Windows Server 2012 System Requirements, you can refer to that: https://technet.microsoft.com/en-us/library/dn303418.aspx
You can also proceed like the following:
Install available Windows Updates (To be tested first)
Install recent versions of your drivers, firmware and BIOS
Uninstall all unused programs
Run chkdsk /r /f and sfc /scannow
Do a clean boot
If this does not help then you can temporary disable security software in use and try again.
This posting is provided AS IS with no warranties or guarantees , and confers no rights.
Ahmed MALEK
My Website Link
My Linkedin Profile
My MVP Profile

Similar Messages

Activate windows server 2012 R2 after evaluation expired

I installed windows server 2012 R2 evaluation version on 4 servers. The evaluation expired and the servers are shutting down automatically now. When I try to put the license key, it is not accepting it. I could activate some other servers with same license
key; but before the evaluation time expired. I used the same media to install these serves as well. Kindly let me know if there is a way or workaround to make these servers licensed.
Regards.

Hi,
Did the problematic Windows Server 2012 R2 connect to Internet when attempt to activate the server? Please also
refer to Converting evaluation versions of Windows Server 2012 to full retail versions section in following article and check if can help you.
Evaluation Versions and Upgrade Options for
Windows Server 2012
à
When I try to put the license key, it is not accepting it.
By the way, did you get any error message when can’t activate the problematic server?
If any update, please feel free to let me know.
Hope this helps.
Best regards,
Justin Gu
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

Windows Server 2012 R2 Will Support for UEFI boot in WDS.

Hi
Currently we had issue in WDS while deploying the image via UEFI boot in the DELL Optiplex 3010. We already deployed the Windows 8 install image and boot image in the Windows Server 2012 R2. After selecting the Network boot its show Start PXE IPV4 and it
will immediately flicker and get back to Network Boot option. Any one please help me out of this.....
But the same is working in Legacy boot and it doesn't activate the Windows 8.

Hi,
As I cannot confirm the exact settings on your side, please see the suggestions provided in following thread:
WDS: EFI BIOS won't PXE boot into EFI mode
http://social.technet.microsoft.com/Forums/windowsserver/en-US/ceca6149-bedd-4860-8a7f-a1c83bf99aa4/wds-efi-bios-wont-pxe-boot-into-efi-mode?forum=winserversetup
The same issue is discussed a lot in this thread and several possible suggestions are provided. See if it is helpful. If there is anything unclear please just let us know.
If you have any feedback on our support, please send to [email protected]

Windows Server 2012 R2 "The password is incorrect. Try again."

Hi,
I tried to login to my Windows Server 2012 R2 and I got this message "The password is incorrect. Try again." Although the username and password are absolutely correct.
Any thoughts. Thanks.

Hi,
I have been investigating this behavior for a while, I am wondering that have you migrated your domain from 2003 to 2012 recently?
Because I can reproduce this issue by migrating a Windows Server 2003 domain to Windows Server 2012 domain, after the Domain Controller changes its password.
Here are some similar threads below about this issue, which got me testing this behavior in the first place:
DC - refuses administrator log on
http://social.technet.microsoft.com/Forums/windowsserver/en-US/e16fcdda-8e5a-4b30-bbe0-d847bcb68b4e/dc-refuses-administrator-log-on?forum=winserverDS
KRB_AP_ERR_MODIFIED 4 Random on Member Server in upgraded Domain 2003 to 2012 R2
http://social.technet.microsoft.com/Forums/windowsserver/en-US/4d8a4018-5969-4c6c-99b1-b446711e1dd4/krbaperrmodified-4-random-on-member-server-in-upgraded-domain-2003-to-2012-r2?forum=winserverDS
I am still trying to figure out how and why this issue happens, and consulting with some experts. I will keep you posted once I have progress.
Have a nice day!
Amy

Windows server 2012 R2 problem

I have a problem in windows server 2012 R2. After sudden turn off the server 2012 R2 due to power failure the drive letters ( except 'C' drive) of the Hard discs is automatically changed i.e data of 'E' drive is seen in
"F" drive & so on. Kindly let us know the solution of this problem. regards

Hi this is in the wrong forum should be 2012 R2 windows server forum.
But in answer to your question, this can happen if ISCSI drives or SAN drives have been disconnected and reconnected, and perhaps the DVD or CD driver has stolen the orginal Driver Letter. without information on your exact configuration it is to difficult
to diagnose.
I ve seen this also happen when a USB memory stick has been left in the server.
This isn't something that would happen normally.!
you can easily change the drive letters back to the original in Disk Manager. you might have to move one first to say 'Z' then move it back to the correct letter last.
regards
Mark

Install SQL Server 2012 SP1 on a Windows Server 2012 R2 Failover Cluster - hangs at "Running discovery on remote machine" on VMWare VSphere 5.5 Update 1

Hi,I'm trying to install SQL Server 2012 SP1 on the first node of a Windows Server 2012 R2 failover cluster.The install hangs whilst displaying the "Please wait while Microsoft SQL Server 2012 Servce
Pack 1 Setup processes the current operation." message.The detail.txt log file shows as follows:(01) 2014-07-17 15:36:35 Slp: -- PidInfoProvider : Use cached PID (01) 2014-07-17 15:36:35 Slp: -- PidInfoProvider
: NormalizePid is normalizing input pid (01) 2014-07-17 15:36:35 Slp: -- PidInfoProvider : NormalizePid found a pid containing dashes, assuming pid is normalized, output pid (01) 2014-07-17 15:36:35 Slp: -- PidInfoProvider : Use cached
PID (01) 2014-07-17 15:36:35 Slp: Completed Action: FinalCalculateSettings, returned True (01) 2014-07-17 15:36:35 Slp: Completed Action: ExecuteBootstrapAfterExtensionsLoaded, returned True (01) 2014-07-17 15:36:35 Slp: ---------------------------------------------------------------------- (01) 2014-07-17 15:36:35 Slp: Running Action: RunRemoteDiscoveryAction (01) 2014-07-17 15:36:36 Slp: Running discovery on local machine (01) 2014-07-17 15:36:36 Slp: Discovery on local machine is complete (01) 2014-07-17
15:36:36 Slp: Running discovery on remote machine: XXX-XXX-01After about 4 hours and 10 minutes, the step seems to time out and move on, however it doesn't seem to have discovered what it needs to and the setup subsuently fails

Hi,
Sorry Information you provided did not helped can you post content of both summary file and details,txt file on shared location for analysis.
Can you download Service pack again and try once more
Please mark this reply as answer if it solved your issue or vote as helpful if it helped so that other forum members can benefit from it.
My TechNet Wiki Articles

Windows Server Essentials error occurred while configuring on Windows Server 2012 R2 Standard

am attempting to install the Windows Server Essentials on a new domain controller in a new domain and forest. I go to add roles and features and select essentials. The config wizard says it is Updating and Preparing the Server and
That is all the information that you need to provide. Your server is being prepared for use and may restart more than once. This may take up to 30 minutes.
It goes to 3% and the encounters an error saying An error occurred while configuring Windows Server Essentials. Please try again. I don't seem to find anything in the log to indicate why it fails.

Hi boe_d,
Based on your description, did you mean that this error was occurred in process of installing the Windows Server
Essentials Experience Role on Windows Server 2012 R2 Standard? If I misunderstand, please don’t hesitate to let me know.
If it is, have you re-tried the role installation? Please check if still go to 3% and then get the same error
message.
In addition, please add
ServerAdmin$ account to the Logon as a service Group Policy, and then monitor the result. For more details, please refer to the following article.
You may be unable to run post-deployment configuration wizard after you install the Windows Server Essentials
Experience role
http://blogs.technet.com/b/sbs/archive/2013/12/04/you-may-be-unable-to-run-post-deployment-configuration-wizard-after-you-install-the-windows-server-essentials-experience-role.aspx
If this issue still exists, please navigate to: %windir%\Logs\CBS folder and check the CBS log file if you
can find any error that depend on the Essentials Experience Role setup time.
Hope this helps.
Best regards,
Justin Gu

Error during configuration process while installing obiee 11.1.1.7.0 in windows server 2012

HI..
I'm having an issue while installing obiee 11g(11.1.1.7.0) in windows server 2012 and using the database as ms sql server 2008. During configuration process after the installation process is completed , here the process is stopped at "Step:executing opmnctl start configuration_obisch1" status "failed"
Here is the error:
Error
    opmnctl task failed
    Step Executing: opmnctl start coreapplication_obisch1 failed
    Configuration Action "Executing opmnctl start coreapplication_obisch1 " has failed. please check log files...
any help would be great
thanks..

Friend,
Installer file size is:
Size: *1.23 GB (1,323,085,837 bytes).*
Size on disk: *1.23 GB (1,323,089,920 bytes).*
I tested also disabling antivirus on my PC and disconnect the power cord before starting the installation of JDeveloper. In both tests the result was the same.
Some additional recommendations to solve this case.
Thank you for supporting.
Edited by: Luis_vkacito on Nov 15, 2012 6:48 AM

Windows Server 2012 Standard - HP OfficeJet Pro 8600 Plus printer not working after promoting to Domain Controller / AD Services

An associate and myself installed the built-in drivers for the HP OfficeJet Pro 8600 Plus multi-function (network) printer on a Windows Server 2012 Standard server installation and everything worked fine whenever I want to print anything directly from the
Windows Server machine (there's a reason for this, so please understand that ;) ).
We were able to print without any problems from the Windows Server 2012 machine, using the drivers from Microsoft. Mainly, because HP has not listed any specific support for Windows Server 2012, only Windows Server 2008 R2, however, the drivers that
came with Windows 2012 seem to work very well.
PROBLEM: I later had to promote the Windows Server 2012 to a Domain Controller, and created the Active Directory configurations, even enabled the Print Services. After doing all of that, the HP printer will not print anything. It's like all print
requests directly from the Windows Server go to Nil.
Has anyone encountered a problem like this before? The only thing I can think of is that after perhaps something affected printing directly once we promoted the server to being a DC, and added other features / roles. I even tried installing the
HP drivers for Windows Server 2008 R2, and the results are still the same...nothing prints. Trust me, the printer is set as the Default Printer and even when choosing to print, we make sure the HP OfficeJet Pro is selected, and is on, as other Windows
Client PC's can print to it directly.
Does anyone have any suggestions we could try? Thanks in advance.

While it is quite a while since this was posted - I can concur a similar issue exists.
We have spent the better part of a day trying to work out why other HP printers work fine but our 8620 prints are not printing and going to Nil. The print server is hosted on a shared DC. Comparing to the initial posters details, for some reason
it seems to be most commonly related to the OfficeJet Pro 8600/8610/8620/8630 series printers.
I ended up doing a print server migration from the domain controller to stand alone host and all printers now work from a single server rather than a mix. Domain controller OSes varied from 2008, 2012, 2012 R2 (tested with multiple) and only after
all of those failed then tried a stand alone server os machine as a last resort which worked fine. Printing directly from Win 7 / 8 /8.1 clients to the IP always worked.

Unable to Install Windows Server 2012 R2; system aborts and reboots after first blue Windows logo appears

System: Dell PowerEdge sc1420 with dual xeon and Adaptec 2420SA SATA RAID (supported by OS); 10 GB memory (2x4, rank 2, organization x4, in DIMM1 & DIMM2; 2x1, registered, organization x8, in DIMM3 & DIMM4)
This computer is currently running Windows Server 2008 R2 Enterprise which was installed with no problems.
Objective: clean install of Windows Server 2012 R2 Standard on an otherwise unused RAID array disk set.
All attempts to boot from DVD result in loading of files (grey progress bar on bottom of screen), brief dark screen, then black screen with a blue windows logo for about 2 seconds and then a flash of about 10 lines of error notifications on a black screen
for about 1/4 second (unreadable), and then a reboot of the computer.
Coreinfo.exe confirms that cpus DO support NX and PAE; do NOT support VMX (virtual machine enhancements).
Attempts to run memtest.exe from boot disk tool-menu startup result in an error message that the memtest.exe file is corrupt.
Running memtest.exe from Windows 2008 R2 install disk results in all memory tests passed!
Attempted booting with multiple DVD's (some +R, some -R, all verified) burned from .iso. These DVD's were used successfully to install Windows Server 2012 R2 on an HP Pavilion. Also changed DVD drives just to rule out DVD hardware.
Running CHKDSK from Windows 2012 R2 on HP Pavilion shows no problems; running CHKDSK from Windows 2008 R2 on the Dell system on the same disks shows some problems. Running checkdisk on the Windows 2008 R2 install disk from the Windows 2008 R2 installed
system shows no problems. All disks burned and verified on same system.
Also attempted to boot from USB thumbdrive with copy of DVD on it. Same results: system loads files then reboots at first Windows logo. So that would rule out disk quality issues per se??
Started to try an upgrade rather clean install to see if any errors were announced. None were announced as the system went through much of the process. I aborted somewhere along the way before committing to the upgrade because 1) the most likely
outcome was it would not boot after install (I don't really need the practice in restoring); and 2) even if it did reboot, having a system that can't be repaired by booting the install disk is pointless.
All disks and raid arrays are recognized and usable by RAID controller card and by Windows Server 2008 R2. Disks are within spec for use with Adaptec 2420SA (1TB @ 300).
Is VMX (aka VT-x) actaully required for ANY install even though Hyper-V is not intended to be used? If so, it is too bad that the Microsoft system requirements (
http://technet.microsoft.com/en-us/library/dn303418.aspx ) don't make that clear. And lack of VMX support really doesn't explain the memtest.exe "corruption" issue.
Or is it maybe something unique about the files on 2012 R2 disk (or disk image on USB) that are causing some problem with the chipset processing? But why?
My vote would be for the latter of the issues, but I have no clue why or if it is remediable. Suggestions?

So here is what I think is the final understanding of this problem:
First, one additional piece of important information: The computer successfully moves into and through the Windows Boot Loader phase and succeeding phase ONLY for Windows 8.1 32-bit, but NOT for Windows 8.1 64-bit nor for Windows
Server 2012 R2 (only 64-bit).
The Windows Boot Manager phase (which precedes the Windows Boot Loader phase) is either 32-bit or 64-bit (64 –bit for this case) and is loaded by the 16-bit stub program (Bootmgr) which starts in real mode.
Windows Boot Loader of course runs in either 32-bit or 64-bit (64 –bit for this case) according to the product being installed.
By inference, the essential problem is occurring in conjunction with the loading of a WIM file to start the Windows Boot Manager.
The boot manager starts ok and generally shows its essential screens (Windows Boot Manager; Advanced Boot Options) or proceeds to load files for transition into Windows startup in the succeeding Windows Boot Loader phase (that doesn’t “boot” but rather
loads the system). This is best confirmed by the announced corruption of the memtest.exe file when selecting Windows Memory Diagnostic from the Windows Boot Manager Screen.
If allowed to continue loading files to pass control to the Windows Boot Manager, the type of abort and resulting immediate restart that occurs is that which you would associate with unhandled cpu exceptions (invalid instruction, memory out of range,
wild interrupt, etc.) that most of us have not commonly seen for 20 years (since beginning to use well behave OS’s from Windows NT 3.1 and on).
So, the problem obviously is due to a failure to properly mount the WIM file and/or properly access it (probably the latter) when running in 64-bit protected mode.
This is independent of the hardware on which the install disk is actually mounted (DVD or USB-flash), so it is NOT a hardware problem
per se.
Since the WIM is mounted early in the process, Boot Manager may well have loaded it using BIOS routines to access the physical device on which it resides rather than loading 32-bit or 64-bit drivers of its own.
Hence, if the BIOS does not “mount” the WIM in a way that is later fully compatible with access from the 64-bit systems being loaded, it could cause apparent file corruption.
If it is only partially incompatible some functionality may appear quite usable (like loading files) until later detected.
This is vague on my part, because the exact nature of the incompatibility cannot be readily determined from the information available.
But the consequence is the same: the system cannot boot from the install disk, either for initial installation or repairs.
Incidental conclusion: The 64-bit boot manager code for Windows Server 2008 does not exhibit this faulty behavior, but the 64-bit code for Windows Server 2012 does.
So the problem is not inherent with loading 64-bit server OS’s.
Expectations: If the system were to be upgraded using the features of the install disk while running an installed OS, say Windows Server 2008 R2, it might well succeed and yield a fully functional system upgraded to Windows Server 2012
R2 (because the installed operating system is started from discrete files, not from a WIM file).
However, in order to perform a disaster recovery using Windows resources (such as image backups from Windows Server Backup), one would have to presumably boot from a Windows Server 2012 64-bit install disk or Windows Server USB recovery drive.
Of course we know that the Windows Server install disk will not boot and we can be fairly sure that the problem will migrate to any Windows Server USB recovery drive that is created.
My inspection of a Windows 7 System Repair CD shows that is based exclusively on boot.wim, not discrete files!
Of course a generated image for a WIM for Windows 2012 USB recovery drive
might not have the flaw that drives this behavior, but it probably would.
Problem conclusion: A BIOS upgrade would be required for compatibility with Windows Server 2014 clean installation
and any maintenance; and none is available from the OEM.
Problem not resolved, but understood for future reference.
Thanks to Tim whose comments helped me focus my thinking.

Strange errors regarding RPC and WMI after migrating Hyper-V from Windows Server 2008 R2 to Windows Server 2012 cluster...

Hi all;
Suppose I have created a two-node Hyper-V cluster with a fibre channel shared storage in Windows Server 2012. Everything work fine except some issues. One of the is that when I want to configure the cluster to add a VM as its cluster resource, the following
error message appears:
An error occurred while determining the state of this clustered role in the cluster. The remote procedure call failed with error 800706BE.
Any ideas?
Thanks
Please VOTE as HELPFUL if the post helps you and remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading
the thread.

Thanks for your reply…
I have tested many possible solutions without any success. The actions that I have done so far are mentioned in the following and the results of them have been said, too.
When I restart the servers, everything are good but after some times when I reopen Failover Cluster Manager on one of the servers, the snap-in related to my cluster name does not load. Please look at the following figure:
And when I want to connect to my cluster name, the following error message appears:
Note: The above problem appears randomly regarding to servers. In the other hand, after the restart, one of the servers acts as the above statement.
The following error message is the result of the DTCPing utility:
++++++++++++hosts
++++++++++++
06-11, 10:02:15.346-->Error(0x424) at clutil.cpp @256
06-11, 10:02:15.346-->-->OpenCluster
06-11, 10:02:15.356-->-->1060(The specified service does not exist as an installed service.)
++++++++++++++++++++++++++++++++++++++++++++++
     DTCping 1.9 Report for ADMINISTRATOR1
++++++++++++++++++++++++++++++++++++++++++++++
RPC server is ready
++++++++++++Validating Remote Computer Name++++++++++++
06-11, 10:02:20.428-->Start DTC connection test
Name Resolution:
SRV04-->172.16.140.11-->SRV04
06-11, 10:02:32.448-->Start RPC test (ADMINISTRATOR1-->SRV04)
Problem:fail to invoke remote RPC method
Error(0x6D9) at dtcping.cpp @303
-->RPC pinging exception
-->1753(There are no more endpoints available from the endpoint mapper.)
RPC test failed
And
06-11, 10:26:10.837-->Error(0x424) at clutil.cpp @256
06-11, 10:26:10.837-->-->OpenCluster
06-11, 10:26:10.837-->-->1060(The specified service does not exist as an installed service.)
++++++++++++++++++++++++++++++++++++++++++++++
     DTCping 1.9 Report for ADMINISTRATOR1
++++++++++++++++++++++++++++++++++++++++++++++
RPC server is ready
++++++++++++Validating Remote Computer Name++++++++++++
06-11, 10:26:14.947-->Start DTC connection test
Name Resolution:
SRV04-->172.16.140.11-->SRV04
06-11, 10:26:26.967-->Start RPC test (ADMINISTRATOR1-->SRV04)
Problem:fail to invoke remote RPC method
Error(0x6D9) at dtcping.cpp @303
-->RPC pinging exception
-->1753(There are no more endpoints available from the endpoint mapper.)
RPC test failed
And
++++++++++++hosts
++++++++++++
06-11, 10:47:51.510-->Error(0x424) at clutil.cpp @256
06-11, 10:47:51.510-->-->OpenCluster
06-11, 10:47:51.510-->-->1060(The specified service does not exist as an installed service.)
++++++++++++++++++++++++++++++++++++++++++++++
     DTCping 1.9 Report for ADMINISTRATOR1
++++++++++++++++++++++++++++++++++++++++++++++
RPC server is ready
++++++++++++Validating Remote Computer Name++++++++++++
06-11, 10:47:55.020-->Start DTC connection test
Name Resolution:
SRV03-->172.16.140.10-->SRV03
06-11, 10:48:06.830-->Start RPC test (ADMINISTRATOR1-->SRV03)
Problem:fail to invoke remote RPC method
Error(0x6D9) at dtcping.cpp @303
-->RPC pinging exception
-->1753(There are no more endpoints available from the endpoint mapper.)
RPC test failed
The following output is the result of running PortQuery on port 135 on both servers:
=============================================
Starting portqry.exe -n srv03 -e 135 -p TCP ...
Querying target system called:
srv03
Attempting to resolve name to IP address...
Name resolved to 172.16.140.10
querying...
TCP port 135 (epmap service): LISTENING
Using ephemeral source port
Querying Endpoint Mapper Database...
Server's response:
UUID: d95afe70-a6d5-4259-822e-2c84da1ddb0d
ncacn_ip_tcp:srv03[49152]
UUID: 906b0ce0-c70b-1067-b317-00dd010662da
ncacn_ip_tcp:srv03[49285]
UUID: 906b0ce0-c70b-1067-b317-00dd010662da
ncacn_ip_tcp:srv03[49285]
UUID: 906b0ce0-c70b-1067-b317-00dd010662da
ncacn_ip_tcp:srv03[49285]
UUID: 367abb81-9844-35f1-ad32-98f038001003
ncacn_ip_tcp:srv03[49159]
UUID: b97db8b2-4c63-11cf-bff6-08002be23f2f Microsoft Cluster Server API
ncacn_ip_tcp:srv03[49156]
UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncacn_np:srv03[\\pipe\\lsass]
UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncacn_ip_tcp:srv03[49155]
UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncacn_np:srv03[\\pipe\\lsass]
UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncacn_ip_tcp:srv03[49155]
UUID: 12345778-1234-abcd-ef00-0123456789ac
ncacn_np:srv03[\\pipe\\lsass]
UUID: 12345778-1234-abcd-ef00-0123456789ac
ncacn_ip_tcp:srv03[49155]
UUID: 12345778-1234-abcd-ef00-0123456789ac
ncacn_ip_tcp:srv03[49157]
UUID: 7f1343fe-50a9-4927-a778-0c5859517bac DfsDs service
ncacn_np:srv03[\\PIPE\\wkssvc]
UUID: 3473dd4d-2e88-4006-9cba-22570909dd10 WinHttp Auto-Proxy Service
ncacn_np:srv03[\\PIPE\\W32TIME_ALT]
UUID: 1ff70682-0a51-30e8-076d-740be8cee98b
ncacn_np:srv03[\\PIPE\\atsvc]
UUID: 378e52b0-c0a9-11cf-822d-00aa0051e40f
ncacn_np:srv03[\\PIPE\\atsvc]
UUID: 86d35949-83c9-4044-b424-db363231fd0c
ncacn_np:srv03[\\PIPE\\atsvc]
UUID: 86d35949-83c9-4044-b424-db363231fd0c
ncacn_ip_tcp:srv03[49154]
UUID: 3a9ef155-691d-4449-8d05-09ad57031823
ncacn_np:srv03[\\PIPE\\atsvc]
UUID: 3a9ef155-691d-4449-8d05-09ad57031823
ncacn_ip_tcp:srv03[49154]
UUID: a398e520-d59a-4bdd-aa7a-3c1e0303a511 IKE/Authip API
ncacn_np:srv03[\\PIPE\\atsvc]
UUID: a398e520-d59a-4bdd-aa7a-3c1e0303a511 IKE/Authip API
ncacn_ip_tcp:srv03[49154]
UUID: 552d076a-cb29-4e44-8b6a-d15e59e2c0af IP Transition Configuration endpoint
ncacn_np:srv03[\\PIPE\\atsvc]
UUID: 552d076a-cb29-4e44-8b6a-d15e59e2c0af IP Transition Configuration endpoint
ncacn_ip_tcp:srv03[49154]
UUID: 2e6035b2-e8f1-41a7-a044-656b439c4c34 Proxy Manager provider server endpoint
ncacn_np:srv03[\\PIPE\\atsvc]
UUID: 2e6035b2-e8f1-41a7-a044-656b439c4c34 Proxy Manager provider server endpoint
ncacn_ip_tcp:srv03[49154]
UUID: c36be077-e14b-4fe9-8abc-e856ef4f048b Proxy Manager client server endpoint
ncacn_np:srv03[\\PIPE\\atsvc]
UUID: c36be077-e14b-4fe9-8abc-e856ef4f048b Proxy Manager client server endpoint
ncacn_ip_tcp:srv03[49154]
UUID: c49a5a70-8a7f-4e70-ba16-1e8f1f193ef1 Adh APIs
ncacn_np:srv03[\\PIPE\\atsvc]
UUID: c49a5a70-8a7f-4e70-ba16-1e8f1f193ef1 Adh APIs
ncacn_ip_tcp:srv03[49154]
UUID: 98716d03-89ac-44c7-bb8c-285824e51c4a XactSrv service
ncacn_np:srv03[\\PIPE\\atsvc]
UUID: 98716d03-89ac-44c7-bb8c-285824e51c4a XactSrv service
ncacn_ip_tcp:srv03[49154]
UUID: 1a0d010f-1c33-432c-b0f5-8cf4e8053099 IdSegSrv service
ncacn_np:srv03[\\PIPE\\atsvc]
UUID: 1a0d010f-1c33-432c-b0f5-8cf4e8053099 IdSegSrv service
ncacn_ip_tcp:srv03[49154]
UUID: c9ac6db5-82b7-4e55-ae8a-e464ed7b4277 Impl friendly name
ncacn_np:srv03[\\PIPE\\atsvc]
UUID: c9ac6db5-82b7-4e55-ae8a-e464ed7b4277 Impl friendly name
ncacn_ip_tcp:srv03[49154]
UUID: c9ac6db5-82b7-4e55-ae8a-e464ed7b4277 Impl friendly name
ncacn_np:srv03[\\PIPE\\srvsvc]
UUID: 30b044a5-a225-43f0-b3a4-e060df91f9c1
ncacn_np:srv03[\\PIPE\\atsvc]
UUID: 30b044a5-a225-43f0-b3a4-e060df91f9c1
ncacn_ip_tcp:srv03[49154]
UUID: 30b044a5-a225-43f0-b3a4-e060df91f9c1
ncacn_np:srv03[\\PIPE\\srvsvc]
UUID: f6beaff7-1e19-4fbb-9f8f-b89e2018337c Event log TCPIP
ncacn_np:srv03[\\pipe\\eventlog]
UUID: f6beaff7-1e19-4fbb-9f8f-b89e2018337c Event log TCPIP
ncacn_ip_tcp:srv03[49153]
UUID: 30adc50c-5cbc-46ce-9a0e-91914789e23c NRP server endpoint
ncacn_np:srv03[\\pipe\\eventlog]
UUID: 30adc50c-5cbc-46ce-9a0e-91914789e23c NRP server endpoint
ncacn_ip_tcp:srv03[49153]
UUID: 3c4728c5-f0ab-448b-bda1-6ce01eb0a6d5 DHCP Client LRPC Endpoint
ncacn_np:srv03[\\pipe\\eventlog]
UUID: 3c4728c5-f0ab-448b-bda1-6ce01eb0a6d5 DHCP Client LRPC Endpoint
ncacn_ip_tcp:srv03[49153]
UUID: 3c4728c5-f0ab-448b-bda1-6ce01eb0a6d6 DHCPv6 Client LRPC Endpoint
ncacn_np:srv03[\\pipe\\eventlog]
UUID: 3c4728c5-f0ab-448b-bda1-6ce01eb0a6d6 DHCPv6 Client LRPC Endpoint
ncacn_ip_tcp:srv03[49153]
UUID: 76f226c3-ec14-4325-8a99-6a46348418af
ncacn_np:srv03[\\PIPE\\InitShutdown]
UUID: d95afe70-a6d5-4259-822e-2c84da1ddb0d
ncacn_np:srv03[\\PIPE\\InitShutdown]
Total endpoints found: 51
==== End of RPC Endpoint Mapper query response ====
portqry.exe -n srv03 -e 135 -p TCP exits with return code 0x00000000.
And
=============================================
Starting portqry.exe -n srv04 -e 135 -p TCP ...
Querying target system called:
srv04
Attempting to resolve name to IP address...
Name resolved to 172.16.140.11
querying...
TCP port 135 (epmap service): LISTENING
Using ephemeral source port
Querying Endpoint Mapper Database...
Server's response:
UUID: d95afe70-a6d5-4259-822e-2c84da1ddb0d
ncacn_ip_tcp:srv04[1025]
UUID: 906b0ce0-c70b-1067-b317-00dd010662da
ncacn_ip_tcp:srv04[1143]
UUID: 906b0ce0-c70b-1067-b317-00dd010662da
ncacn_ip_tcp:srv04[1143]
UUID: 906b0ce0-c70b-1067-b317-00dd010662da
ncacn_ip_tcp:srv04[1143]
UUID: 367abb81-9844-35f1-ad32-98f038001003
ncacn_ip_tcp:srv04[1065]
UUID: b97db8b2-4c63-11cf-bff6-08002be23f2f Microsoft Cluster Server API
ncacn_ip_tcp:srv04[1057]
UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncacn_np:srv04[\\pipe\\lsass]
UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncacn_ip_tcp:srv04[1028]
UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncacn_np:srv04[\\pipe\\lsass]
UUID: 0b1c2170-5732-4e0e-8cd3-d9b16f3b84d7 RemoteAccessCheck
ncacn_ip_tcp:srv04[1028]
UUID: 12345778-1234-abcd-ef00-0123456789ac
ncacn_np:srv04[\\pipe\\lsass]
UUID: 12345778-1234-abcd-ef00-0123456789ac
ncacn_ip_tcp:srv04[1028]
UUID: 12345778-1234-abcd-ef00-0123456789ac
ncacn_ip_tcp:srv04[1084]
UUID: 7f1343fe-50a9-4927-a778-0c5859517bac DfsDs service
ncacn_np:srv04[\\PIPE\\wkssvc]
UUID: 1ff70682-0a51-30e8-076d-740be8cee98b
ncacn_np:srv04[\\PIPE\\atsvc]
UUID: 378e52b0-c0a9-11cf-822d-00aa0051e40f
ncacn_np:srv04[\\PIPE\\atsvc]
UUID: 86d35949-83c9-4044-b424-db363231fd0c
ncacn_np:srv04[\\PIPE\\atsvc]
UUID: 86d35949-83c9-4044-b424-db363231fd0c
ncacn_ip_tcp:srv04[1027]
UUID: 3a9ef155-691d-4449-8d05-09ad57031823
ncacn_np:srv04[\\PIPE\\atsvc]
UUID: 3a9ef155-691d-4449-8d05-09ad57031823
ncacn_ip_tcp:srv04[1027]
UUID: a398e520-d59a-4bdd-aa7a-3c1e0303a511 IKE/Authip API
ncacn_np:srv04[\\PIPE\\atsvc]
UUID: a398e520-d59a-4bdd-aa7a-3c1e0303a511 IKE/Authip API
ncacn_ip_tcp:srv04[1027]
UUID: 552d076a-cb29-4e44-8b6a-d15e59e2c0af IP Transition Configuration endpoint
ncacn_np:srv04[\\PIPE\\atsvc]
UUID: 552d076a-cb29-4e44-8b6a-d15e59e2c0af IP Transition Configuration endpoint
ncacn_ip_tcp:srv04[1027]
UUID: 2e6035b2-e8f1-41a7-a044-656b439c4c34 Proxy Manager provider server endpoint
ncacn_np:srv04[\\PIPE\\atsvc]
UUID: 2e6035b2-e8f1-41a7-a044-656b439c4c34 Proxy Manager provider server endpoint
ncacn_ip_tcp:srv04[1027]
UUID: c36be077-e14b-4fe9-8abc-e856ef4f048b Proxy Manager client server endpoint
ncacn_np:srv04[\\PIPE\\atsvc]
UUID: c36be077-e14b-4fe9-8abc-e856ef4f048b Proxy Manager client server endpoint
ncacn_ip_tcp:srv04[1027]
UUID: c49a5a70-8a7f-4e70-ba16-1e8f1f193ef1 Adh APIs
ncacn_np:srv04[\\PIPE\\atsvc]
UUID: c49a5a70-8a7f-4e70-ba16-1e8f1f193ef1 Adh APIs
ncacn_ip_tcp:srv04[1027]
UUID: 98716d03-89ac-44c7-bb8c-285824e51c4a XactSrv service
ncacn_np:srv04[\\PIPE\\atsvc]
UUID: 98716d03-89ac-44c7-bb8c-285824e51c4a XactSrv service
ncacn_ip_tcp:srv04[1027]
UUID: 1a0d010f-1c33-432c-b0f5-8cf4e8053099 IdSegSrv service
ncacn_np:srv04[\\PIPE\\atsvc]
UUID: 1a0d010f-1c33-432c-b0f5-8cf4e8053099 IdSegSrv service
ncacn_ip_tcp:srv04[1027]
UUID: c9ac6db5-82b7-4e55-ae8a-e464ed7b4277 Impl friendly name
ncacn_np:srv04[\\PIPE\\atsvc]
UUID: c9ac6db5-82b7-4e55-ae8a-e464ed7b4277 Impl friendly name
ncacn_ip_tcp:srv04[1027]
UUID: c9ac6db5-82b7-4e55-ae8a-e464ed7b4277 Impl friendly name
ncacn_np:srv04[\\PIPE\\srvsvc]
UUID: 30b044a5-a225-43f0-b3a4-e060df91f9c1
ncacn_np:srv04[\\PIPE\\atsvc]
UUID: 30b044a5-a225-43f0-b3a4-e060df91f9c1
ncacn_ip_tcp:srv04[1027]
UUID: 30b044a5-a225-43f0-b3a4-e060df91f9c1
ncacn_np:srv04[\\PIPE\\srvsvc]
UUID: f6beaff7-1e19-4fbb-9f8f-b89e2018337c Event log TCPIP
ncacn_np:srv04[\\pipe\\eventlog]
UUID: f6beaff7-1e19-4fbb-9f8f-b89e2018337c Event log TCPIP
ncacn_ip_tcp:srv04[1026]
UUID: 30adc50c-5cbc-46ce-9a0e-91914789e23c NRP server endpoint
ncacn_np:srv04[\\pipe\\eventlog]
UUID: 30adc50c-5cbc-46ce-9a0e-91914789e23c NRP server endpoint
ncacn_ip_tcp:srv04[1026]
UUID: 3c4728c5-f0ab-448b-bda1-6ce01eb0a6d5 DHCP Client LRPC Endpoint
ncacn_np:srv04[\\pipe\\eventlog]
UUID: 3c4728c5-f0ab-448b-bda1-6ce01eb0a6d5 DHCP Client LRPC Endpoint
ncacn_ip_tcp:srv04[1026]
UUID: 3c4728c5-f0ab-448b-bda1-6ce01eb0a6d6 DHCPv6 Client LRPC Endpoint
ncacn_np:srv04[\\pipe\\eventlog]
UUID: 3c4728c5-f0ab-448b-bda1-6ce01eb0a6d6 DHCPv6 Client LRPC Endpoint
ncacn_ip_tcp:srv04[1026]
UUID: 76f226c3-ec14-4325-8a99-6a46348418af
ncacn_np:srv04[\\PIPE\\InitShutdown]
UUID: d95afe70-a6d5-4259-822e-2c84da1ddb0d
ncacn_np:srv04[\\PIPE\\InitShutdown]
Total endpoints found: 50
==== End of RPC Endpoint Mapper query response ====
portqry.exe -n srv04 -e 135 -p TCP exits with return code 0x00000000.
I have read the KB197814 and did the steps in it, restarted both servers, but the problem did not resolved.
I have check both servers for RPC Service status and in both servers it has started.
The both servers are alive and can ping each other by their IP address and name.
The firewall of both servers is off and I stopped the Windows Firewall service COMPLETELY.
Any services and applications that are depending on RPC have problems. For example when I want o remotely manages the services on these servers by using Services.msc console, the following error message appears:
Error 1726: The remote procedure call failed.
Please VOTE as HELPFUL if the post helps you and remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading
the thread.

My 10.9.0.1 internal mac was ruined after the installation of Windows Server 2012 on boot camp

Hi Everyone. I've been trying to install Windows Server 2012 on my boot camp. Well, soon after the 2012 was installed, my mac os 10.9.0.1 was ruined. When I pressed on the option key while the imac was booting, I can see the icon of "10.9.0.1 recovery". But after I chose it, the apple tried very hard to boot it up with a progress bar below the apple icon. The computer shut down itself after the progress bar reached the end. I've tried boot it up with the installation CD and tried to repair the Macintosh HD in Disk Uitilites but no use. It was said the hard drive cannot be repaired and better be reformat. Currently I can only boot up my mac from my SuperDuper external clone drive. Anyone could give me wise advices to fix this problem please?

The "wise advices" I can offer are:
Read the Boot Camp documentation before trying to reinstall Windows Server. Windows Server is not supported by Boot Camp
Erase and reformat your hard drive. Reinstall OSx then restore your data from your backup.
Use a virtual machine like Parallels, Fusion, or VirtualBox to install Windows Server

Windows Server 2012 R2 hangs at a certain timing.

Hello all,
I have a server (Windows Server 2012 R2 Datacenter Edition) using Hyper-V manager. It is hosting Live VMs now. For two Saturdays in a row, it hangs at a certain timing early morning at around 3am. There are two events that i seen, one of them is event 6008
and the other is event 41. Both of them doesn't seems to tell me anything after i googled for these events.
There is no dump files being created even though it is configured to do so. I have checked the scheduler but i also found nothing.
Anybody have any idea on how to troubleshoot and prevent that from happening?
The screenshot i had taken:
http://i60.tinypic.com/155kyzm.jpg
http://i60.tinypic.com/200us0g.jpg
http://i61.tinypic.com/nlwydk.jpg
http://i57.tinypic.com/bvpyr.jpg

Hello,
Is there anyone that can help me with this? I am out of ideas..

Error while uninstalling and then re installing sharepoint 2013 on same server(windows server 2012)

Hi All,
I have installed SharePoint 2013 prerequisites successfully on windows server 2012. While installing SharePoint 2013, system struck on for several minutes. I have restart my system manually. Later I then installed prerequisites which showed a successful
lessage. But When I try to install SharePoint 2013. I am getting the following error:
trial editions and lincensed editions of SharePoint, Project Server, and Office Web apps products may not be installed on the same server.
I am unable to find solution for this issue. what is the solution for this?
Thanks in Advance..
Prem Kumar

To be honest, the quickest thing you could do (and what I would do regardless) is re-build the server (re-install Windows).
Trevor Seward
Follow or contact me at...
&nbsp&nbsp
This post is my own opinion and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

CRM 2015 installation hangs without errors on Windows Server 2012 installed in a VM

I have installed a Windows Server 2012 and SQL Server 2012 on a VM using VMware Player and then installed Dynamics CRM 2013, working out all the configuration problems.
The installation hanged once without errors and when I tried it again it was installed, no problems. Dynamics CRM 2013 works without issue.
Then I copied the machine, uninstalled the Dynamics CRM 2013 and started installing CRM 2015. However this time without errors the installation hangs even though I tried more than 5 times.
There are no errors, installation program is not unresponsive and task manager shows nothing out of the ordinary.
I have also tried this on multiple physical and virtual PCs to no avail.

Try to Delete the registry files of CRM before you start the installation : HKEY_LOCAL_MACHINESOFTWAREMicrosoftMSCRM

Windows Server 2012 Hangs After a While

Similar Messages

Maybe you are looking for