Windows Server 2012 DHCP Event ID: 20291
Hi,
We have a DHCP failover set up with the default settings.
We have always noticed numerous Event ID: 20291 errors in the Event Log. After following the instructions installing patches KB2919355 and KB2955135, deleting the failover relationship, and recreating it, we're still getting numerous errors with different
scopes, and the error repeats repeatedly for the same IP. Sometimes users would get duplicate IP address error.
When we click on "Display Statistics" on various scopes for each partner, they show different numbers as far as how many IPs are leased by each.
Any ideas on what this could mean? We're ready to just remove the failover relationship completely and go back to split scope.
http://blogs.technet.com/b/teamdhcp/archive/2014/02/26/dhcp-failover-patch-to-address-a-reservation-issue-and-another-issue-related-to-failover-partner-not-accepting-state-transition-from-bad-address-gt-active-has-been-released.aspx?pi47623=2
http://support.microsoft.com/en-us/kb/2955135
Source: Microsoft-Windows-DHCP-Server
Date: date/time
Event ID: 20291
Task Category: DHCP Failover
Level: Error
User: NETWORK SERVICE
Computer: DHCP-NODE
Description: A BINDING-ACK message with transaction id: Transaction_Number was sent for IP address: IP_Address with reject reason: (Reject Reason Unknown) to partner server: DHCP_Partner_Server for failover relationship: DHCP_Failover_Relationship_Name.
Hi,
According to your description, my understanding is that DHCP failover with load sharing mode, Event Log displays numerous Event ID: 20291, and the error repeats repeatedly for the same IP.
As KB 2955135 mentioned that Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. If both servers are Windows Server 2012 R2, please install KB3000850(November 2014 update rollup
for Windows Server 2012 R2), download link:
http://www.microsoft.com/en-us/download/details.aspx?id=44975
Note:
Before you install this update, you have to first remove the failover relationship, install the update to both DHCP nodes and restart them, and then reestablish the failover relationship.
Best Regards,
Eve Wang
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]
Similar Messages
-
I am trying to install WSUS role on Windows Server 2012 R2 using dedicated SQL Instance with static port on remote SQL Server 2012 SP1 CU7 on Windows Server 2012 R2.
It verifies the connection and then throws the error:
The request to add or remove features on the specified server failed. The operation cannot be completed, because the server you specified requires a restart.
WSUS Server : Windows Server 2012 R2
Remote SQL Server: 2012 SP1 CU7 hosted on Windows Server 2012 R2
Please let me know if anyone has experienced this issue.We were trying to install WSUS role on Windows Server 2012 R2 using dedicated SQL Instance with static port on remote SQL Server 2012 SP1 CU7 on Windows Server 2012 R2.
It verifies the connection and then throws the error:
The request to add or remove features on the specified server failed. The operation cannot be completed, because the server you specified requires a restart.
Same error even after rebooting the server multiple times.
WSUS Server : Windows Server Standard2012 R2
Remote SQL Server: Windows Server 2012 SP1 CU7 hosted on Windows Server 2012 R2
Event ID 7000:
The Windows Internal Database service failed to start due to the following error:
The service did not start due to a logon failure.
Event ID 7041
The MSSQL$MICROSOFT##WID service was unable to log on as NT SERVICE\MSSQL$MICROSOFT##WID with the currently configured password due to the following error:
Logon failure: the user has not been granted the requested logon type at this computer.
Service: MSSQL$MICROSOFT##WID
Domain and account: NT SERVICE\MSSQL$MICROSOFT##WID
This service account does not have the required user right "Log on as a service."
User Action
Assign "Log on as a service" to the service account on this computer. You can use Local Security Settings (Secpol.msc) to do this. If this computer is a node in a cluster, check that this user
right is assigned to the Cluster service account on all nodes in the cluster.
If you have already assigned this user right to the service account, and the user right appears to be removed, check with your domain administrator to find out if a Group Policy object associated
with this node might be removing the right.
I found following article:
"MSSQL$MICROSOFT##WID service was unable to log on as NT SERVICE\MSSQL$MICROSOFT##WID" error when you install WID in Windows Server 2012
http://support.microsoft.com/kb/2832204/en-us
To work around the issue, use one of the following methods:
Assign the Log on as a service user right to NT SERVICE\ALL SERVICES in the GPO that defines the user right.
Exclude the computer from the GPO that defines the user right.
We moved the SCCM server to OU where no policies were getting applied and then applied the new GPO to that OU. Restarted the server and we were able to install WSUS role.
Regards
PR -
Cannot create Failover Relationship between to Server 2012 DHCP Servers
Hello all!
I am trying to create failover relationships for several scopes on a Server 2012 DHCP server. This all worked in my test environment, but the production environment keeps giving me errors saying that the scope cannot be added on the target server.
Does anyone know what Error: 20010 in this case means?
Thanks.Hope this helps
http://blog.rolpdog.com/2012/11/dhcp-failover-breaks-with-custom-options.html
http://popravak.wordpress.com/2014/05/31/windows-server-2012-dhcp-failover-with-or-without-custom-dhcp-attributes/
Rgds
Milos
PS: List of errors
http://msdn.microsoft.com/en-us/library/windows/desktop/aa363378(v=vs.85).aspx -
Windows Server 2012 Failover Cluster (Hyper-V) Event Id 1196
Hi All,
I just installed Failover Cluster for Hyper-V on windows server 2012 with 2 nodes. I got following error event id 1196.
reCreated / deleted Cluster Host A record on DNS and nothing happened.
Any suggestion?
There is similar topic but it couldnt help
http://social.technet.microsoft.com/Forums/en-US/winserverClustering/thread/2ad0afaf-8d86-4f16-b748-49bf9ac447a3/
RegardsHi,
You may refer to this article to troubleshoot this issue;
Event ID 1196 — Network Name Resource Availability
http://technet.microsoft.com/en-us/library/dd354022(v=WS.10).aspx
Check the following:
Check that on the DNS server, the record for the Network Name resource still exists. If the record was accidentally deleted, or was scavenged by the DNS server, create it again, or arrange to have a network administrator create it.
Ensure that a valid, accessible DNS server has been specified for the indicated network adapter or adapters in the cluster.
Check the system event log for Netlogon or DNS events that occurred near the time of the failover cluster event. Troubleshooting these events might solve the problem that prevented the clustered Network Name resource from registering the DNS name.
For more information please refer to following MS articles:
DNS Registration with the Network Name Resource
http://blogs.msdn.com/b/clustering/archive/2009/07/17/9836756.aspx
Lawrence
TechNet Community Support -
Windows Server 2012 R2 NIC Teaming and DHCP Issue
Came across a weird issue today during a server deployment. I was doing a physical server deployment and got Windows installed and was getting ready to connect it to our network. Before connecting the Ethernet cables to the network adapters, I created a
NIC Team using Windows Server 2012 R2 built-in software with a static IP address (we'll say its 192.168.1.56). Once I plugged in the Ethernet cables, I got network access but was unable to join our domain. At this time, I deleted the NIC team and the two network
adapters got their own IP addresses issued from DHCP (192.168.1.57 and 192.168.1.58) and at this point I was able to join our domain. I recreated the NIC team and set a new static IP (192.168.1.57) and everything was working great as intended.
My issue is when I went into DHCP I noticed a random entry that was using the IP address I used for the first NIC teaming attempt (192.168.1.56), before I joined it to the domain. I call this a random entry because it is using the last 8 characters of the
MAC address as the hostname instead of the servers hostname.
It seems when I deleted the first NIC team I created (192.168.1.56), a random MAC address Server 2012 R2 generated for the team has remained embedded in the system. The IP address is still pingable even though an ipconfig /all shows the current NIC team
with the IP 192.168.1.57. There is no IP address of 192.168.1.56 configured on the current server and I have static IPs set yet it is still pingable and registering with DHCP.
I know this is slightly confusing but I am hoping someone else has encountered this issue and may be able to tell me how to fix this. Simply deleting the DHCP entry does not do the trick, it comes back.Hi,
Please confirm you have choose the right NIC team type, If you’ve previously configured NIC teaming, you’re aware NIC teams usually require the assistance of network-side
protocols. Prior to Windows 2012, using a NIC team on a server also meant enabling protocols like EtherChannel or LACP (also known as 802.1ax or 802.3ad) on network ports.
More information:
NIC teaming configure in Server 2012
http://technet.microsoft.com/en-us/magazine/jj149029.aspx
Hope this helps.
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place. -
Windows Server 2012 R2 - ALL HF's Failing to install as "Does Not Apply to this computer"
Hi,
A general question about hot fix installs.
I have multiple servers that are all Windows 2012 R2. They do not have internet connections, so I have to install the Hotfixes manually. I download the HF's from the ISO download page (https://support.microsoft.com/en-us/kb/913086) every month. I collect them and install in a bulk install during a release cycle ( a couple times a year). I just realized that NO HF's have installed since JUNE 2014. Every HF that shows up in WindowsServer2012R2 directory fail to install with a message of "The update is not applicable to your computer". Which is fine if that was true, but.... I get this message for every HF from the ISO's since June 2014. NOT one HF thinks it is applicable to my computer. Could that be the case? No HF's apply to my Server 2012 systems since June of 2014?
This is my system info, and below that is the results from attempting to install 95 HF's.
C:\TEMP>systeminfo
Host Name: MYHOST
OS Name: Microsoft Windows Server 2012 R2 Datacenter
OS Version: 6.3.9600 N/A Build 9600
OS Manufacturer: Microsoft Corporation
OS Configuration: Member Server
OS Build Type: Multiprocessor Free
Registered Owner: Windows User
Registered Organization:
Product ID: 00252-80025-36226-AA727
Original Install Date: 6/13/2014, 8:04:39 AM
System Boot Time: 3/16/2015, 2:34:45 PM
System Manufacturer: Dell Inc.
System Model: PowerEdge R720
System Type: x64-based PC
Processor(s): 2 Processor(s) Installed.
[01]: Intel64 Family 6 Model 62 Stepping 4 GenuineInt
el ~2500 Mhz
[02]: Intel64 Family 6 Model 62 Stepping 4 GenuineInt
el ~2500 Mhz
BIOS Version: Dell Inc. 2.2.2, 1/16/2014
Windows Directory: C:\Windows
System Directory: C:\Windows\system32
Boot Device: \Device\HarddiskVolume1
System Locale: en-us;English (United States)
Input Locale: en-us;English (United States)
Time Zone: (UTC-07:00) Mountain Time (US & Canada)
Total Physical Memory: 262,099 MB
Available Physical Memory: 249,337 MB
Virtual Memory: Max Size: 301,011 MB
Virtual Memory: Available: 288,015 MB
Virtual Memory: In Use: 12,996 MB
Page File Location(s): C:\pagefile.sys
Domain: mydomain.sgn
Logon Server: \\MYHOST
Hotfix(s): 25 Hotfix(s) Installed.
[01]: KB2862152
[02]: KB2868626
[03]: KB2876331
[04]: KB2888505
[05]: KB2892074
[06]: KB2893294
[07]: KB2893984
[08]: KB2898785
[09]: KB2898868
[10]: KB2898871
[11]: KB2900986
[12]: KB2901125
[13]: KB2901128
[14]: KB2909210
[15]: KB2909921
[16]: KB2912390
[17]: KB2916036
[18]: KB2919442
[19]: KB2922229
[20]: KB2923392
[21]: KB2925418
[22]: KB2930275
[23]: KB2931358
[24]: KB2931366
[25]: KB2936068
Network Card(s): 6 NIC(s) Installed.
[01]: Broadcom BCM57800 NetXtreme II 10 GigE (NDIS VB
D Client)
Connection Name: ISCSI
DHCP Enabled: No
IP address(es)
[01]: 192.168.1.30
[02]: fe80::38c9:e59c:5ac2:e0a1
[02]: Broadcom BCM57800 NetXtreme II 1 GigE (NDIS VBD
Client)
Connection Name: NIC3
Status: Hardware not present
[03]: Broadcom BCM57800 NetXtreme II 1 GigE (NDIS VBD
Client)
Connection Name: MGMT
DHCP Enabled: No
IP address(es)
[01]: 7.48.64.32
[02]: 7.48.64.30
[03]: fe80::f14e:9339:9326:c7fd
[04]: Broadcom BCM57810 NetXtreme II 10 GigE (NDIS VB
D Client)
Connection Name: SLOT 5 Port 1_swport_VMRepwan
DHCP Enabled: Yes
DHCP Server: N/A
IP address(es)
[05]: Broadcom BCM57800 NetXtreme II 10 GigE (NDIS VB
D Client)
Connection Name: NIC2
Status: Hardware not present
[06]: Broadcom BCM57810 NetXtreme II 10 GigE (NDIS VB
D Client)
Connection Name: SLOT 5 Port 2_swport_VMOpswan
DHCP Enabled: Yes
DHCP Server: N/A
IP address(es)
Hyper-V Requirements: A hypervisor has been detected. Features required for
Hyper-V will not be displayed.
I have a script that runs each HF install.. If I run them manually without the tool I get the same results so it is not the script..
Installing 95 patches
for Microsoft Windows Server 2012 R2 Datacenter x64
Repository path: U:\Patch Repository_4_1\2012_R2_HFs\
1. Windows8.1-KB2894852-v2-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
2. Windows8.1-KB2894856-v2-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
3. Windows8.1-KB2920189-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
4. Windows8.1-KB2926765-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
5. Windows8.1-KB2928120-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
6. Windows8.1-KB2931358-x64.msu patch status: ALREADY INSTALLED - SKIPPING
7. Windows8.1-KB2931366-x64.msu patch status: ALREADY INSTALLED - SKIPPING
8. Windows8.1-KB2933826-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
9. Windows8.1-KB2939576-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
10. Windows8.1-KB2953522-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
11. Windows8.1-KB2957151-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
12. Windows8.1-KB2957189-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
13. Windows8.1-KB2957689-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
14. Windows8.1-KB2961072-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
15. Windows8.1-KB2961887-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
16. Windows8.1-KB2962872-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
17. Windows8.1-KB2964718-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
18. Windows8.1-KB2964736-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
19. Windows8.1-KB2965788-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
20. Windows8.1-KB2966072-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
21. Windows8.1-KB2966826-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
22. Windows8.1-KB2966828-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
23. Windows8.1-KB2971850-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
24. Windows8.1-KB2972213-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
25. Windows8.1-KB2972280-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
26. Windows8.1-KB2973114-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
27. Windows8.1-KB2973201-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
28. Windows8.1-KB2973351-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
29. Windows8.1-KB2974008-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
30. Windows8.1-KB2976627-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
31. Windows8.1-KB2976897-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
32. Windows8.1-KB2977292-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
33. Windows8.1-KB2977629-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
34. Windows8.1-KB2978668-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
35. Windows8.1-KB2982794-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
36. Windows8.1-KB2982998-v2-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
37. Windows8.1-KB2987107-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
38. Windows8.1-KB2987114-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
39. Windows8.1-KB2988948-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
40. Windows8.1-KB2992611-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
41. Windows8.1-KB2993651-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
42. Windows8.1-KB2993958-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
43. Windows8.1-KB3000061-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
44. Windows8.1-KB3000483-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
45. Windows8.1-KB3000869-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
46. Windows8.1-KB3001237-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
47. Windows8.1-KB3002657-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
48. Windows8.1-KB3002885-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
49. Windows8.1-KB3003057-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
50. Windows8.1-KB3003381-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
51. Windows8.1-KB3003743-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
52. Windows8.1-KB3004150-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
53. Windows8.1-KB3004361-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
54. Windows8.1-KB3004365-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
55. Windows8.1-KB3005607-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
56. Windows8.1-KB3006226-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
57. Windows8.1-KB3008923-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
58. Windows8.1-KB3008925-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
59. Windows8.1-KB3010788-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
60. Windows8.1-KB3011780-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
61. Windows8.1-KB3013126-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
62. Windows8.1-KB3013455-v2-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
63. Windows8.1-KB3014029-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
64. Windows8.1-KB3018943-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
65. Windows8.1-KB3019215-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
66. Windows8.1-KB3019978-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
67. Windows8.1-KB3020393-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
68. Windows8.1-KB3021674-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
69. Windows8.1-KB3021952-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
70. Windows8.1-KB3023607-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
71. Windows8.1-KB3036197-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
72. Windows8.1-KB3021953-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
73. Windows8.1-KB3022777-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
74. Windows8.1-KB3023266-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
75. Windows8.1-KB3023562-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
76. Windows8.1-KB3024663-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
77. Windows8.1-KB3029944-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
78. Windows8.1-KB3030377-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
79. Windows8.1-KB3031432-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
80. Windows8.1-KB3032323-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
81. Windows8.1-KB3032359-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
82. Windows8.1-KB3040335-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
83. Windows8.1-KB3033408-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
84. Windows8.1-KB3033889-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
85. Windows8.1-KB3034196-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
86. Windows8.1-KB3034344-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
87. Windows8.1-KB3035017-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
88. Windows8.1-KB3035034-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
89. Windows8.1-KB3035126-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
90. Windows8.1-KB3035131-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
91. Windows8.1-KB3035132-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
92. Windows8.1-KB3037634-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
93. Windows8.1-KB3039066-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
94. Windows8.1-KB3044132-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
95. Windows8.1-KB3046049-x64.msu patch status: DOES NOT APPLY TO THIS COMPUTER
Thanks,
Dave
Hi Dave,
Would you please check CBS lg file and other relevant event logs if find more clues? On current situation, please refer to following article and check if can help you.
Update is not applicable to your computer- but it is
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] -
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. -
ASA and RADUIS on Windows server 2012
hi i have ASA5505 i want to get the Authentication from Raduis Server using NPS on windows Server 2012 i test the Raduis Server over "Kerio Control VMware Virtual Appliance" its work Perfect for testing my Setting on Raduis but with the ASA5505 i get this message "Error authentication rejected aaa failure"
Running Config
: Saved
ASA Version 9.1(3)
hostname NazcoFW
domain-name default.domain.invalid
enable password XgEKS9WizHnI9IUJ encrypted
xlate per-session deny tcp any4 any4
xlate per-session deny tcp any4 any6
xlate per-session deny tcp any6 any4
xlate per-session deny tcp any6 any6
xlate per-session deny udp any4 any4 eq domain
xlate per-session deny udp any4 any6 eq domain
xlate per-session deny udp any6 any4 eq domain
xlate per-session deny udp any6 any6 eq domain
passwd XgEKS9WizHnI9IUJ encrypted
names
interface Ethernet0/0
switchport access vlan 22
interface Ethernet0/1
interface Ethernet0/2
switchport access vlan 12
interface Ethernet0/3
interface Ethernet0/4
shutdown
interface Ethernet0/5
shutdown
interface Ethernet0/6
shutdown
interface Ethernet0/7
switchport access vlan 32
shutdown
interface Vlan1
nameif NAZCO
security-level 100
ddns update hostname OSI
dhcp client update dns server both
ip address 172.16.200.1 255.255.255.0
interface Vlan12
nameif outside4
security-level 0
ip address 172.16.4.254 255.255.255.0
interface Vlan22
nameif Outside20
security-level 0
ip address 172.16.20.254 255.255.255.0
boot system disk0:/asa913-k8.bin
ftp mode passive
dns domain-lookup NAZCO
dns server-group DefaultDNS
name-server 10.1.1.1
name-server 10.1.2.1
domain-name default.domain.invalid
same-security-traffic permit inter-interface
same-security-traffic permit intra-interface
object network HP5220
host 10.10.10.105
object network ak20
host 10.10.10.110
object network hp5520
host 192.168.2.105
object network HP7000
host 192.168.2.106
object network HP5520
host 192.168.2.105
object network ak04
host 10.10.10.110
object network HP400
host 192.168.2.107
object network out04
range 192.168.2.200 192.168.2.220
object network AK04
host 10.10.10.110
object network oooo
subnet 10.10.10.0 255.255.255.0
object network 444
host 10.10.10.110
object network OSITOINT
subnet 10.10.10.0 255.255.255.0
object-group network OSItoOUT04
network-object object out04
access-list outside20_access_in extended permit icmp any4 any4
pager lines 24
logging enable
logging asdm-buffer-size 512
logging trap informational
logging asdm informational
logging host NAZCO 10.10.10.10 17/6161
logging debug-trace
logging permit-hostdown
mtu NAZCO 1500
mtu Outside20 1500
mtu outside4 1500
no failover
icmp unreachable rate-limit 1 burst-size 1
asdm image disk0:/asdm-721.bin
no asdm history enable
arp timeout 14400
no arp permit-nonconnected
nat (NAZCO,outside4) source dynamic any interface dns
nat (NAZCO,Outside20) source dynamic any interface dns
route Outside20 0.0.0.0 0.0.0.0 172.16.20.1 1
route outside4 0.0.0.0 0.0.0.0 172.16.4.1 11
timeout xlate 3:00:00
timeout pat-xlate 0:00:30
timeout conn 1:00:00 half-closed 0:10:00 udp 0:02:00 icmp 0:00:02
timeout sunrpc 0:10:00 h323 0:05:00 h225 1:00:00 mgcp 0:05:00 mgcp-pat 0:05:00
timeout sip 0:30:00 sip_media 0:02:00 sip-invite 0:03:00 sip-disconnect 0:02:00
timeout sip-provisional-media 0:02:00 uauth 0:05:00 absolute
timeout tcp-proxy-reassembly 0:01:00
timeout floating-conn 0:00:00
dynamic-access-policy-record DfltAccessPolicy
aaa-server Keefa-Raduis protocol radius
aaa-server Keefa-Raduis (NAZCO) host 172.16.200.10
key *****
radius-common-pw *****
user-identity default-domain LOCAL
aaa authentication enable console LOCAL
aaa authentication http console LOCAL
aaa authentication serial console LOCAL
aaa authentication ssh console LOCAL
aaa authentication telnet console LOCAL
http server enable
http 0.0.0.0 0.0.0.0 NAZCO
snmp-server host NAZCO 10.10.10.196 community ***** version 2c
no snmp-server location
no snmp-server contact
snmp-server community *****
snmp-server enable traps snmp authentication linkup linkdown
snmp-server enable traps syslog
snmp-server enable traps ipsec start stop
snmp-server enable traps entity fru-insert
snmp-server enable traps remote-access session-threshold-exceeded
snmp-server enable traps connection-limit-reached
snmp-server enable traps cpu threshold rising
snmp-server enable traps ikev2 start stop
snmp-server enable traps nat packet-discard
crypto ipsec security-association pmtu-aging infinite
crypto ca trustpoint _SmartCallHome_ServerCA
crl configure
crypto ca trustpool policy
crypto ca certificate chain _SmartCallHome_ServerCA
certificate ca 6ecc7aa5a7032009b8cebcf4e952d491
308205ec 308204d4 a0030201 0202106e cc7aa5a7 032009b8 cebcf4e9 52d49130
0d06092a 864886f7 0d010105 05003081 ca310b30 09060355 04061302 55533117
30150603 55040a13 0e566572 69536967 6e2c2049 6e632e31 1f301d06 0355040b
13165665 72695369 676e2054 72757374 204e6574 776f726b 313a3038 06035504
0b133128 63292032 30303620 56657269 5369676e 2c20496e 632e202d 20466f72
20617574 686f7269 7a656420 75736520 6f6e6c79 31453043 06035504 03133c56
65726953 69676e20 436c6173 73203320 5075626c 69632050 72696d61 72792043
65727469 66696361 74696f6e 20417574 686f7269 7479202d 20473530 1e170d31
30303230 38303030 3030305a 170d3230 30323037 32333539 35395a30 81b5310b
30090603 55040613 02555331 17301506 0355040a 130e5665 72695369 676e2c20
496e632e 311f301d 06035504 0b131656 65726953 69676e20 54727573 74204e65
74776f72 6b313b30 39060355 040b1332 5465726d 73206f66 20757365 20617420
68747470 733a2f2f 7777772e 76657269 7369676e 2e636f6d 2f727061 20286329
3130312f 302d0603 55040313 26566572 69536967 6e20436c 61737320 33205365
63757265 20536572 76657220 4341202d 20473330 82012230 0d06092a 864886f7
0d010101 05000382 010f0030 82010a02 82010100 b187841f c20c45f5 bcab2597
a7ada23e 9cbaf6c1 39b88bca c2ac56c6 e5bb658e 444f4dce 6fed094a d4af4e10
9c688b2e 957b899b 13cae234 34c1f35b f3497b62 83488174 d188786c 0253f9bc
7f432657 5833833b 330a17b0 d04e9124 ad867d64 12dc744a 34a11d0a ea961d0b
15fca34b 3bce6388 d0f82d0c 948610ca b69a3dca eb379c00 48358629 5078e845
63cd1941 4ff595ec 7b98d4c4 71b350be 28b38fa0 b9539cf5 ca2c23a9 fd1406e8
18b49ae8 3c6e81fd e4cd3536 b351d369 ec12ba56 6e6f9b57 c58b14e7 0ec79ced
4a546ac9 4dc5bf11 b1ae1c67 81cb4455 33997f24 9b3f5345 7f861af3 3cfa6d7f
81f5b84a d3f58537 1cb5a6d0 09e4187b 384efa0f 02030100 01a38201 df308201
db303406 082b0601 05050701 01042830 26302406 082b0601 05050730 01861868
7474703a 2f2f6f63 73702e76 65726973 69676e2e 636f6d30 12060355 1d130101
ff040830 060101ff 02010030 70060355 1d200469 30673065 060b6086 480186f8
45010717 03305630 2806082b 06010505 07020116 1c687474 70733a2f 2f777777
2e766572 69736967 6e2e636f 6d2f6370 73302a06 082b0601 05050702 02301e1a
1c687474 70733a2f 2f777777 2e766572 69736967 6e2e636f 6d2f7270 61303406
03551d1f 042d302b 3029a027 a0258623 68747470 3a2f2f63 726c2e76 65726973
69676e2e 636f6d2f 70636133 2d67352e 63726c30 0e060355 1d0f0101 ff040403
02010630 6d06082b 06010505 07010c04 61305fa1 5da05b30 59305730 55160969
6d616765 2f676966 3021301f 30070605 2b0e0302 1a04148f e5d31a86 ac8d8e6b
c3cf806a d448182c 7b192e30 25162368 7474703a 2f2f6c6f 676f2e76 65726973
69676e2e 636f6d2f 76736c6f 676f2e67 69663028 0603551d 11042130 1fa41d30
1b311930 17060355 04031310 56657269 5369676e 4d504b49 2d322d36 301d0603
551d0e04 1604140d 445c1653 44c1827e 1d20ab25 f40163d8 be79a530 1f060355
1d230418 30168014 7fd365a7 c2ddecbb f03009f3 4339fa02 af333133 300d0609
2a864886 f70d0101 05050003 82010100 0c8324ef ddc30cd9 589cfe36 b6eb8a80
4bd1a3f7 9df3cc53 ef829ea3 a1e697c1 589d756c e01d1b4c fad1c12d 05c0ea6e
b2227055 d9203340 3307c265 83fa8f43 379bea0e 9a6c70ee f69c803b d937f47a
6decd018 7d494aca 99c71928 a2bed877 24f78526 866d8705 404167d1 273aeddc
481d22cd 0b0b8bbc f4b17bfd b499a8e9 762ae11a 2d876e74 d388dd1e 22c6df16
b62b8214 0a945cf2 50ecafce ff62370d ad65d306 4153ed02 14c8b558 28a1ace0
5becb37f 954afb03 c8ad26db e6667812 4ad99f42 fbe198e6 42839b8f 8f6724e8
6119b5dd cdb50b26 058ec36e c4c875b8 46cfe218 065ea9ae a8819a47 16de0c28
6c2527b9 deb78458 c61f381e a4c4cb66
quit
telnet timeout 5
ssh scopy enable
ssh 172.16.200.0 255.255.255.0 NAZCO
ssh timeout 5
ssh key-exchange group dh-group1-sha1
console timeout 0
management-access NAZCO
dhcp-client update dns server both
dhcpd dns
dhcpd update dns both
dhcpd address 172.16.200.20-172.16.200.89 NAZCO
dhcpd dns 172.16.20.1 172.16.4.1 interface NAZCO
dhcpd lease 1048575 interface NAZCO
dhcpd update dns both interface NAZCO
dhcpd enable NAZCO
threat-detection basic-threat
threat-detection statistics
threat-detection statistics tcp-intercept rate-interval 30 burst-rate 400 average-rate 200
ssl encryption rc4-sha1 aes128-sha1 aes256-sha1 3des-sha1
username admin password bZmVDHuxUzzxS3yz encrypted privilege 15
class-map inspection_default
match default-inspection-traffic
policy-map type inspect dns preset_dns_map
parameters
message-length maximum client auto
message-length maximum 512
policy-map global_policy
class inspection_default
inspect dns preset_dns_map
inspect ftp
inspect h323 h225
inspect h323 ras
inspect rsh
inspect rtsp
inspect esmtp
inspect sqlnet
inspect skinny
inspect sunrpc
inspect xdmcp
inspect sip
inspect netbios
inspect tftp
inspect ip-options
inspect icmp
inspect icmp error
class class-default
user-statistics accounting
service-policy global_policy global
prompt hostname context
service call-home
no call-home reporting anonymous
call-home
profile CiscoTAC-1
no active
destination address http https://tools.cisco.com/its/service/oddce/services/DDCEService
destination address email [email protected]
destination transport-method http
subscribe-to-alert-group diagnostic
subscribe-to-alert-group environment
subscribe-to-alert-group inventory periodic monthly
subscribe-to-alert-group configuration periodic monthly
subscribe-to-alert-group telemetry periodic daily
hpm topN enable
Cryptochecksum:357b7c6f861e8aa9bb3a3674a789b39b
: end
asdm image disk0:/asdm-721.bin
no asdm history enableHi
Looks like the AAA configuration is set for local
aaa authentication enable console LOCAL
aaa authentication http console LOCAL
aaa authentication serial console LOCAL
aaa authentication ssh console LOCAL
aaa authentication telnet console LOCAL
Change it to Radius
aaa-server Keefa-Raduis protocol radius
aaa-server Keefa-Raduis (NAZCO) host 172.16.200.10
key *****
radius-common-pw *****
for example :
aaa authentication telnet console Keefa-Raduis LOCAL
Now when you will do telnet to using Radius credentials, Its Should work, If radius goes down you can use LOCAL username and password as fallback method.
Cheers!
Minakshi(Do rate the helpful post) -
Server Manager Error, Windows Server 2012 Standed
Windows
Server 2012 on my desktop
and I've been in it then
open Server Manager "ServerManager.exe - This application could not be started"
error this time. In it,
the option is YES and
NO. YES is open
to the side of .net.
Please help me as soon as possible.Hi,
Please check the event viewer to get more detailed error information about this issue.
You can also remotely access it from another server by adding this server in the server manager of the remote server, and try to access the roles and features from the remote server, and tackle the problem from there.
I hope this helps. -
We have a problem with one of our deployments of Windows Server 2012 Hyper-V with a 2 node cluster connected to a iSCSI SAN.
Our setup:
Hosts - Both run Windows Server 2012 Standard and are clustered.
HP ProLiant G7, 24 GB RAM, 2 teamed NIC dedicated to Virtual Machines and Management, 2 teamed NIC dedicated to iSCSI storage. - This is the primary host and normaly all VMs run on this host.
HP ProLiant G5, 20 GB RAM, 1 NIC dedicated to Virtual Machines and Management, 2 teamed NIC dedicated to iSCSI storage. - This is the secondary host that and is intended to be used in case of failure of the primary host.
We have no antivirus on the hosts and the scheduled ShadowCopy (previous version of files) is switched of.
iSCSI SAN:
QNAP NAS TS-869 Pro, 8 INTEL SSDSA2CW160G3 160 GB i a RAID 5 with a Host Spare. 2 Teamed NIC.
Switch:
DLINK DGS-1210-16 - Both the network cards of the Hosts that are dedicated to the Storage and the Storage itself are connected to the same switch and nothing else is connected to this switch.
Virtual Machines:
3 Windows Server 2012 Standard - 1 DC, 1 FileServer, 1 Application Server.
1 Windows Server 2008 Standard Exchange Server.
All VMs are using dynamic disks (as recommended by Microsoft).
Updates
We have applied the most resent updates to the Hosts, WMs and iSCSI SAN about 3 weeks ago with no change in our problem and we continually update the setup.
Normal operation
Normally this setup works just fine and we see no real difference in speed in startup, file copy and processing speed in LoB applications of this setup compared to a single host with 2 10000 RPM Disks. Normal network speed is 10-200 Mbit, but occasionally
we see speeds up to 400 Mbit/s of combined read/write for instance during file repair
Our Problem
Our problem is that for some reason all of the VMs stops responding or responds very slowly and you can for instance not send CTRL-ALT-DEL to a VM in the Hyper-V console, or for instance start task manager when already logged in.
Symptoms (i.e. this happens, or does not happen, at the same time)
I we look at resource monitor on the host then we see that there is often an extensive read from a VHDX of one of the VMs (40-60 Mbyte/s) and a combined write speed to many files in \HarddiskVolume5\System Volume Information\{<someguid and no file extension>}.
See iamge below.
The combined network speed to the iSCSI SAN is about 500-600 Mbit/s.
When this happens it is usually during and after a VSS ShadowCopy backup, but has also happens during hours where no backup should be running (i.e. during daytime when the backup has finished hours ago according to the log files). There is however
not that extensive writes to the backup file that is created on an external hard drive and this does not seem to happen during all backups (we have manually checked a few times, but it is hard to say since this error does not seem leave any traces in event
viewer).
We cannot find any indication that the VMs themself detect any problem and we see no increase of errors (for example storage related errors) in the eventlog inside the VMs.
The QNAP uses about 50% processing Power on all cores.
We see no dropped packets on the switch.
(I have split the image to save horizontal space).
Unable to recreate the problem / find definitive trigger
We have not succeeded in recreating the problem manually by, for instance, running chkdsk or defrag in VM and Hosts, copy and remove large files to VMs, running CPU and Disk intensive operations inside a VM (for instance scan and repair a database file).
Questions
Why does all VMs stop responding and why is there such intensive Read/Writes to the iSCSI SAN?
Could it be anything in our setup that cannot handle all the read/write requests? For instance the iSCSI SAN, the hosts, etc?
What can we do about this? Should we use MultiPath IO instead of NIC teaming to the SAN, limit bandwith to the SAN, etc?Hi,
> All VMs are using dynamic disks (as recommended by Microsoft).
If this is a testing environment, it’s okay, but if this a production environment, it’s not recommended. Fixed VHDs are recommended for production instead of dynamically expanding or differencing VHDs.
Hyper-V: Dynamic virtual hard disks are not recommended for virtual machines that run server workloads in a production environment
http://technet.microsoft.com/en-us/library/ee941151(v=WS.10).aspx
> This is the primary host and normaly all VMs run on this host.
According to your posting, we know that you have Cluster Shared Volumes in the Hyper-V cluster, but why not distribute your VMs into two Hyper-V hosts.
Use Cluster Shared Volumes in a Windows Server 2012 Failover Cluster
http://technet.microsoft.com/en-us/library/jj612868.aspx
> 2 teamed NIC dedicated to iSCSI storage.
Use Microsoft MultiPath IO (MPIO) to manage multiple paths to iSCSI storage. Microsoft does not support teaming on network adapters that are used to connect to iSCSI-based storage devices. (At least it’s not supported until Windows Server 2008 R2. Although
Windows Server 2012 has built-in network teaming feature, I don’t article which declare that Windows Server 2012 network teaming support iSCSI connection)
Understanding Requirements for Failover Clusters
http://technet.microsoft.com/en-us/library/cc771404.aspx
> I have seen using MPIO suggests using different subnets, is this a requirement for using MPIO
> or is this just a way to make sure that you do not run out of IP adressess?
What I found is: if it is possible, isolate the iSCSI and data networks that reside on the same switch infrastructure through the use of VLANs and separate subnets. Redundant network paths from the server to the storage system via MPIO will maximize availability
and performance. Of course you can set these two NICs in separate subnets, but I don’t think it is necessary.
> Why should it be better to not have dedicated wireing for iSCSI and Management?
It is recommended that the iSCSI SAN network be separated (logically or physically) from the data network workloads. This ‘best practice’ network configuration optimizes performance and reliability.
Check that and modify cluster configuration, monitor it and give us feedback for further troubleshooting.
For more information please refer to following MS articles:
Volume Shadow Copy Service
http://technet.microsoft.com/en-us/library/ee923636(WS.10).aspx
Support for Multipath I/O (MPIO)
http://technet.microsoft.com/en-us/library/cc770294.aspx
Deployments and Tests in an iSCSI SAN
http://technet.microsoft.com/en-US/library/bb649502(v=SQL.90).aspx
Hope this helps!
TechNet Subscriber Support
If you are
TechNet Subscription user and have any feedback on our support quality, please send your feedback
here.
Lawrence
TechNet Community Support -
Set up Search Service App For SharePoint server 2013 on Windows server 2012 R2 not working
Hi all,
I installed SharePoint server 2013 on Windows server 2012 R2 using VirtualBox. I created a DC(domain controller) server with a domain set up on one VM and it has SQL server 2012 SP1 installed. Then SharePoint 2013 on another VM was set up to access
the DC server. Everything seems working except Search Service App which cannot be sucessfully set up. Creation process for Search service app says Successful and 4 search databases were created and look fine. But when I navigate to search service app
admin page, it gives error info:
System status: The search service is not able to connect to the machine that hosts the administration component. Verify that the administration component '386f2cd6-47ca-4b3a-aeb5-d9116772ef16' in search application 'Search Service Application 1' is in
a good state and try again.
Search Application Topology: Unable to retrieve topology component health states. This may be because the admin component is not up and running.
From event viewer, I see following errors:
(1) Error From source: SharePoint Server
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance
(b7c72eb8-cbaf-435e-b4c9-963cb6e4e745).
Reason: The object you are trying to create already exists. Try again using a different name.
Technical Support Details:
System.Runtime.InteropServices.COMException (0x80040D02): The object you are trying to create already exists. Try again using a different name.
at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize()
at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean
isAdministrationServiceJob)
(2) Error From source: SharePoint Server Search
Could not access the Search database. A generic error occurred while trying to access the database to obtain the schema version info.
Context: Application '386f2cd6-47ca-4b3a-aeb5-d9116772ef16'
(3) Warning from source: SharePoint Server Search
A database error occurred. Source: .Net SqlClient Data Provider Code: 8169 occurred 0 time(s) Description: Error ordinal: 1 Message:
Conversion failed when converting from a character string to uniqueidentifier., Class: 16, Number: 8169, State: 2 at
System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
(4) Error From source: SharePoint Server
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance
(b7c72eb8-cbaf-435e-b4c9-963cb6e4e745).
Reason: The gatherer application could not be mounted because the search administration database schema version does not match the expected backwards compatibility schema version. The database might not have been upgraded.
Technical Support Details:
System.Runtime.InteropServices.COMException (0xC0041235): The gatherer application could not be mounted because the search administration database schema version does not match the expected backwards compatibility schema version. The database might not have
been upgraded.
Since separate DC server and SharePoint server do not work, I installed SharePoint 2013 on DC server ( so DC server has everything on it now ) but it gives exactly same result. Later I installed SharePoint 2013 SP1 and still have the same problem with Search
Service app. I spent two weeks tried all suggestions available from Web and Google but SharePoint Search Service simply does not work. Config and other databases work but why Search Service has this issue seemingly related to search DB.
Could anybody please help out? You deserve a top SharePoint consultant award if you could find a solution. I am so frustrated and so tired by this issue. This seems also to be a SP set up issue.
Thanks a lot.Using new Search Service App wizard to create SSA is always a success. I could delete existing SSA and recreate it and no problem. It says successful but when I open Search Admin page from CA, it gives me errors as mentioned.
Now I used the following PS script for creating SSA from Max Mercher, but it stays at the last setps in following script:
Add-PsSnapin Microsoft.SharePoint.PowerShell -ErrorAction SilentlyContinue
$IndexLocation = "C:\Search" #Location must be empty, will be deleted during the process!
$SearchAppPoolName = "SSAPool"
$SearchAppPoolAccountName = "mydomain\admin"
$SearchServiceName = "SSA"
$SearchServiceProxyName = "SSA Proxy"
$DatabaseServer = "W12R2DC1"
$DatabaseName = "SSA"
$spAppPool = Get-SPServiceApplicationPool -Identity $SearchAppPoolName -ErrorAction SilentlyContinue
if (!$spAppPool)
$spAppPool = New-SPServiceApplicationPool -Name $SearchAppPoolName -Account $SearchAppPoolAccountName -Verbose
$ServiceApplication = Get-SPEnterpriseSearchServiceApplication -Identity $SearchServiceName -ErrorAction SilentlyContinue
if (!$ServiceApplication)
# process stays at the following step forever, already one hour now.
$ServiceApplication = New-SPEnterpriseSearchServiceApplication -Name $SearchServiceName -ApplicationPool $spAppPool.Name -DatabaseServer $DatabaseServer -DatabaseName $DatabaseName
Account mydomain\admin is an farm managed account, domain admin account, in WG_ADMIN role, It is in all SQL server roles and is DBO. I see search DBs are already on SQL server. From Event viewer, I got following errors in sequence:
(1) Crawler:Content Plugin under source Crawler:Content Plugin
Content Plugin can not be initialized - list of CSS addresses is not set.
(2) Warning for SharePoint Server Search
A database error occurred. Source: .Net SqlClient Data Provider Code: 8169 occurred 0 time(s) Description: Error ordinal: 1 Message: Conversion failed when converting from a character string to uniqueidentifier., Class: 16, Number: 8169, State: 2
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
(3) Error for SharePoint Server Search
Could not access the Search database. A generic error occurred while trying to access the database to obtain the schema version info.
Context: Application 'cbc5a055-996b-44a7-9cbc-404322f9cfdf'
(4) Error for SharePoint Server
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (b7c72eb8-cbaf-435e-b4c9-963cb6e4e745).
Reason: The gatherer application could not be mounted because the search administration database schema version does not match the expected backwards compatibility schema version. The database might not have been upgraded.
(5) Error Shared Services for SharePoint Server Search
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (b7c72eb8-cbaf-435e-b4c9-963cb6e4e745).
Reason: The object you are trying to create already exists. Try again using a different name.
Technical Support Details:
System.Runtime.InteropServices.COMException (0x80040D02): The object you are trying to create already exists. Try again using a different name.
at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize()
at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob
Above errors keep being generated. Last step for SSA creation stay there forever. Any clue what is really going on? Thanks. -
SharePoint server 2013 Search Service App on Windows server 2012 R2 not working
Hi all,
I installed SharePoint server 2013 on Windows server 2012 R2 using VirtualBox. I created a DC(domain controller) server with a domain set up on one VM and it has SQL server 2012 SP1 installed. Then SharePoint 2013 on another VM
was set up to access the DC server. Everything seems working except Search Service App which cannot be sucessfully set up. Creation process for Search service app says Successful and 4 search databases were created and look fine. But when I navigate
to search service app admin page, it gives error info:
System status: The search service is not able to connect to the machine that hosts the administration component. Verify that the administration component '386f2cd6-47ca-4b3a-aeb5-d9116772ef16' in search application 'Search Service Application 1' is
in a good state and try again.
Search Application Topology: Unable to retrieve topology component health states. This may be because the admin component is not up and running.
From event viewer, I see following errors:
(1) Error From source: SharePoint Server
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (b7c72eb8-cbaf-435e-b4c9-963cb6e4e745).
Reason: The object you are trying to create already exists. Try again using a different name.
Technical Support Details:
System.Runtime.InteropServices.COMException (0x80040D02): The object you are trying to create already exists. Try again using a different name.
at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize()
at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob)
(2) Error From source: SharePoint Server Search
Could not access the Search database. A generic error occurred while trying to access the database to obtain the schema version info.
Context: Application '386f2cd6-47ca-4b3a-aeb5-d9116772ef16'
(3) Warning from source: SharePoint Server Search
A database error occurred. Source: .Net SqlClient Data Provider Code: 8169 occurred 0 time(s) Description: Error ordinal: 1 Message: Conversion failed when converting from a character string to uniqueidentifier., Class: 16, Number: 8169, State: 2
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
(4) Error From source: SharePoint Server
Application Server Administration job failed for service instance Microsoft.Office.Server.Search.Administration.SearchServiceInstance (b7c72eb8-cbaf-435e-b4c9-963cb6e4e745).
Reason: The gatherer application could not be mounted because the search administration database schema version does not match the expected backwards compatibility schema version. The database might not have been upgraded.
Technical Support Details:
System.Runtime.InteropServices.COMException (0xC0041235): The gatherer application could not be mounted because the search administration database schema version does not match the expected backwards compatibility schema version. The database might not have
been upgraded.
Since separate DC server and SharePoint server do not work, I installed SharePoint 2013 on DC server ( so DC server has everything on it now ) but it gives exactly same result. Later I installed SharePoint 2013 SP1 and still have the same problem
with Search Service app. I spent two weeks tried all suggestions available from Web and Google but SharePoint Search Service simply does not work. Config and other databases work but why Search Service has this issue seemingly related to search DB.
Could anybody please help out? You deserve a top SharePoint consultant award if you could find a solution. I am so frustrated and so tired by this issue.
Thanks a lot.Hi,
According to your post, my understanding is that SharePoint server 2013 Search Service App did not work on Windows server 2012 R2.
Please make sure you configure Search Service Application correctly. You can refer to:Create and configure a Search service application in SharePoint Server 2013
I recommend to created new Search Service Application, and made a full crawl. Then assigned the new SSA as the default SSA for webapplications. Finnlay checked the issue doesnt occur now,
If all search related components now are online, to keep the enviroonment clean, you can delete the old SSA.
Thank you for your understanding.
Best Regards,
Linda Li
Linda Li
TechNet Community Support -
Windows Server 2012 Virtual Machine Failure
I am running Windows Server 2012 R2 Host machine. In Hyper-V, I created a WS 2012 VM. The VM starts out OK, but after a few hours of work (configure and install SharePoint 2013), starts throwing errors (Machine had to re-boot). Eventually, the VM becomes
unstable and unable to re-boot. Last attempt threw this error in Hyper-V Event Manager:
'BISP2013' has encountered a fatal error. The guest operating system reported that it failed with the following error codes: ErrorCode0: 0x7A, ErrorCode1: 0x400207A0, ErrorCode2: 0xC0000185, ErrorCode3: 0x57BA6860, ErrorCode4: 0x40F4234. If the
problem persists, contact Product Support for the guest operating system. (Virtual machine ID 7E140D89-25B9-4D3B-835B-7BB882C629BB)
This has happened on multiple attempts occasionally ending with Error 0Xc000021a. Creating WS 2012 R2 VMs does not present this problem.
Any suggestions greatly appreciated.
MarioHi Mario,
This should not happen here .
My suggestion is to download a new server2012 ISO and reinstall .
Also please refer to following "best practice configurations for sharepoint 2013":
http://technet.microsoft.com/en-us/library/ff621103(v=office.15)
Best Regards
Elton Ji
We
are trying to better understand customer views on social support experience, so your participation in this
interview project would be greatly appreciated if you have time.
Thanks for helping make community forums a great place. -
Windows Server 2012 R2 RDS + User profile Disks + App-V = Explorer.exe crashing all of the time
I have built a new RDS farm on Windows Server 2012 R2 with two Session Hosts and a combined Connect Broker/Web Access server. I had the farm up and running with User Profile Disks and all seemed OK. However, as soon as I installed the App-V 5.0 SP2 RDS
client on the session hosts, the explorer.exe process started crashing for any user logging in via the Web Access site. The process crashes and restarts every five to ten seconds. It's the same for administrators. If they log in via Web Access explorer.exe
crashes, but if they RDP directly to one of the session hosts explorer.exe is fine. If I reboot the session hosts, then the first user to log in via Web Access has a stable desktop session (and appears to have a new profile as well). However, if that user
logs out and back in again, explorer.exe starts crashing again. The only applications I have packaged at the moment are Office 2013 and Firefox.
I tried disabling User Profile Disks, but this caused a whole bunch of other problems and I eventually lost the ability to log in at all via Web Access (errors about the user profile service). As this is a small pre-production environment I completed scrapped
all of the servers and rebuilt from scratch. Again, everything appeared fine until I installed the App-V client, then explorer.exe started crashing repeatedly for all users.
Has anyone come across this issue before? I have tried installing the App-V 5.0 SP2 Hotfix Package 2, but this didn't help. I have read in a few forums that App-V doesn't work very well with User Profile Desks, but I have not heard of this particular issue.
Similarly, SP2 seems to have a lot of problems, so I am going to try removing App-V RDp Client SP2 and installing SP1. I ahev also deleted User Profile Disks for the test users to recreate their profiles, but this didn't help either.
Any other suggestions welcome!I forgot to include the application event log entry for explorer.exe crashing:
Faulting application name: explorer.exe, version: 6.3.9600.17039, time stamp: 0x53156588
Faulting module name: KERNELBASE.dll, version: 6.3.9600.17055, time stamp: 0x532954fb
Exception code: 0xc06d007e
Fault offset: 0x0000000000005bf8
Faulting process id: 0xae8
Faulting application start time: 0x01cfab3a273787fd
Faulting application path: C:\Windows\explorer.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: 69210d77-172d-11e4-80c6-0050560102d1
Faulting package full name: -
Intermittent loss of UNC path access on Windows Server 2012
Hi All,
I hope someone can help with a major headache we've been having on two Windows Server 2012 boxes since September this year. Basically, these servers will intermittently lose the ability to browse network shares from windows explorer and the only way we have
found to resolve this is to reboot. When the issue happens, we can't even log into the server as it sits at 'applying user settings' - presumably as it is failing to access the netlogon share on our DCs. If we have an active RDP session when the issue occurs,
we can connect. In this instance we see that if you enter a UNC path in Windows explorer and hit enter, nothing happens - no error messages or anything. The only way I can get any response is when trying to access the IPC$ share on another server, which gives
the following response:
\\server\ipc$ is not accessible. You might not have permission to use this resource, Contact the administrator of this server to find out if you have access permissions.
The parameter is incorrect.
Everything looks right from a physical network perspective, as we can ping from the affected servers and DNS queries are working fine. I can even run net view from powershell and see the local servers and shares on these, however any attempt to access shares
just hangs the powershell session.
If I look in the SMBClient event logs, I can see entries like the following:
Event ID 30805
The client lost its session to the server.
Error: The transport connection is now disconnected.
This is made worse by the fact that when this issue happens, we can't even cleanly reboot the server (it just hangs) and have to perform a cold boot.
The firewall has been turned off and we have taken off our antivirus software to eliminate it as a possible cause. We have even rebuilt one of these servers on a clean install of 2012 R2, but the issue re-appeared. We have also tried using different NIC
drivers (Broadcom NICs installed) to no avail. We have also tried disabling IPv6.
We have logged a ticket with Microsoft support, who have come back telling us that this could be related to a known bug with DFS in 2012 for which a fix is being tested prior to release in a few weeks. However, I can't sit around on my hands until then on
the off chance that this fix will resolve our problem. These servers are hosting our production Lync 2013 front end service and when this issue occurs it breaks the address book search and response group services, so this issue is of critical importance for
us to get resolved asap.
Any help on this would be greatly appreciated.Hi,
That's right, if you hit enter absolutely nothing happens, no error messages. It makes no difference if I try name or IP address - even trying \\localhost doesn't work. A few minutes later after trying, an entry appears in the SMBClient event logs as mentioned
in my original post. To me it looks like something deep within the networking operations of the OS is randomly breaking. Also, if I try to browse the network from Windows explorer, it just hangs. When I try to restart the workstation service, it just gets
permanently stuck in a stopping state and the server has to be cold booted. Once it boots up, everything is working fine again....until the next time. There is absolutely nothing appearing in the application or system event logs indicating the root cause.
I've checked and DNS resolution is working OK and I can telnet to other hosts on all the required ports.
I had originally thought it might be related to the Broadcom NICs as we've had issues with them in the past, but we switched over to use the 2012 inbox driver for them and the same issue happens. I should also mention that one server is a blade and the other
a rackmount box. Dell support have run full diagnostics on both and have come up clean, so it doesn't appear to be a hardware issue. The even more baffling thing is that we have a third server with identical spec and config that does not have the problem.
The only difference with this third server is that it is not part of a Lync pool pairing using DFS and sits in a remote location on a different LAN.
I had thought of trying to drop back to use SMB1 by disabling SMB2 and 3, but I'm not sure if this would adversely affect any other services.
This one really has me stumped.
Maybe you are looking for
-
Hi to all i have a report based on Time management , here i have a fields like ,start date and end date , and time in and time out , i have to calculate a no of absent days , how can i calculate , and they want to selection screen li
-
Hi My ccode currency: USD Vendor contains EUR. I want to place order in AUD, So i have changed currency in PO header (delivery/invoice tab). But I have not changed/made the exchange rate to1 and not selected the check box "Exc rate fixed" in PO hea
-
Any selection input for posting date in Confirmation Report CN48n
Hi All, Is there any way to select some date based on posting date in CN48n report, because if i have run by Plant / co.code it takes so long. Plz advice. Cheers, Nies
-
Response.redirect not working on IE when it is live but works fine on local.
Response.Redirect("http://myurl/php/test.php?username=" + LoginHelper.userName + "&password=" + LoginHelper.password); Hi All, I am trying to redirect the user to different website with username and password. I am using the code above and passing us
-
Is there anyway to create Javadocs without using dos?? i.e. by including code in my application classes to create Javadocs automatically?? I've never created Javadocs before and all the code examples on the site seem to use commands in dos to create