I've a recurring issue on a number of 2008 R1 servers. Replication stops completely, and any attempt to run any AD-related snap-ins or diagnostics fail.
For example:
C:\Windows\system32>dcdiag
Directory Server Diagnosis
Performing initial setup:
Trying to find home server...
Home Server = MYDC
Ldap search capabality attribute search failed on server MYDC, return
value = 81
Other tools also fail in the same manner:
C:\Windows\system32>repadmin /showreps
[d:\rtm\ds\ds\src\util\repadmin\repbind.c, 444] LDAP error 81 (Server Down) Win32 Err 58.
LDP can't connect to the server either:
ld = ldap_open("mydc", 389);
Error <0x51>: Fail to connect to mydc.
There are a couple of event log entries, but frankly I'm not sure if they are a cause or a symptom.
Event 1311:
The Knowledge Consistency Checker (KCC) has detected problems with the following directory partition.
Directory partition:
CN=Configuration,DC=ad,DC=mydomain,DC=co,DC=uk
Event 1566:
All directory servers in the following site that can replicate the directory partition over this transport are currently unavailable.
Site:
CN=MYSITE,CN=Sites,CN=Configuration,DC=ad,DC=mydomain,DC=co,DC=uk
Directory partition:
DC=ad,DC=mydomain,DC=co,DC=uk
Transport:
CN=IP,CN=Inter-Site Transports,CN=Sites,CN=Configuration,DC=ad,DC=mydomain,DC=co,DC=uk
A reboot always clears this up, and always after a month or two the same problem will crop up again on a different server. I've seen it on 5 different servers in different domains so far. Reboots are fine, but it always feels like a bit of a blunt instrument. I was hoping someone might have come across this before and be able to offer a fix.
thanks...
Is this related to: "All the TCP/IP ports that are in a TIME_WAIT status are not closed after 497 days from system startup in Windows Vista, in Windows 7, in Windows Server 2008 and in Windows Server 2008 R2" http://support.microsoft.com/kb/2553549
Related
I have some projects running with XAMPP on my computer and its running on Windows 10. I have been using XAMPP for the past 3 to 4 months with no problem at all, but yesterday suddenly after a windows update, it won't open the Apache server saying :
Error: Apache shutdown unexpectedly.
This may be due to a blocked port, missing dependencies,
improper privileges, a crash, or a shutdown by another method.
Press the Logs button to view error logs and check
the Windows Event Viewer for more clues
If you need more help, copy and post this
entire log window on the forums
I have not been able to find a solution and i tryed many things I could find online, so please if anyone could help me?
EDIT**
I have rebooted my PC a couple of times since this happend and nothing changed! However i forgot to say while posting that the MySQL server is running like it used to! Apache server don't however.
EDIT 2**
I tried many things, such as uninstalling XAMPP and installing it back again, running Apache directly from CMD to check any errors (none were displayed), changed port configurations for Apache even tho port 80 seems to be listening and I also tried installing other XAMPP-like programs (such as MAMP, WAMP) but nothing really came out and no XAMPP-like programs worked! Does anyone have any suggestions?
Also, weird thing, XAMPP runs perfectly on my second PC (Windows 7), like it used to, but I want it in this PC, since here I do my development (The other is old and slow).
Also, now XAMPP seems not to throw the "red-line errors" in it's console, it is just saying:
[Apache] Attempting to start Apache service...
And it does not seems to change.
THIS ONLY HAPPENS WHEN I RUN AS ADMIN XAMPP!
I found the solution after diging to my log/error files and this is what is was displayed;
www.example.com:443:0 server certificate does NOT include an ID which matches the server name
pid file C:/xampp/apache/logs/httpd.pid overwritten -- Unclean shutdown of previous Apache run?
www.example.com:443:0 server certificate does NOT include an ID which matches the server name
PHP Warning: 'C:\WINDOWS\SYSTEM32\VCRUNTIME140.dll' 14.0 is not compatible with this PHP build linked with 14.28 in Unknown on line 0
So i found a solution from anoher article at SO which you can find here
I want to start playing around with databases in Java to help with my university work however I can't get SQL Server to work properly. I've installed it using the wizard and selecting 'Basic' the installing SSMS. However when launching SSMS I get Error 26. When researching this it says to make sure that the SQL Server Browser service is running. Unfortunately this is the issue, every time I try to start the service it fails.
All the fixes I've seen about this topic have been related to servers on another machine where as I am trying to run the server on my own PC. I've tried them anyway but nothing has worked so far. The only thing I can find that might give you a clue in helping me is that in the log file it says that it failed to register the SPN.
When working on my local machine, I don't usually need SQL Server browser - but my SQL Server itself isn't set up to run automatically.
You can go to services (either via window and search for 'services', or in Windows 10 open the task manager, go to the last tab 'services'). Find the 'SQL Server' service (it helps to sort by description column) and right click -> start.
If you take note of the name (default is 'MSSQLSERVER') you can start the service (e.g., in a batch file, from command line) using sc start "MSSQLSERVER" (or whatever your server instance is called).
the cmd execution of registerRExt.exe
I am trying to install RRE(Revolution R Enterprise) v7.5 with RR0 3.2.2(Revolution R Open) on a SQL Server 2016 RC0 default instance. All the steps shown in the https://msdn.microsoft.com/en-us/library/mt590808.aspx have been completed and the error occurs in the Post installation Server configuration scripts. The script has also been replaced by the updated script for RC0 shown on the msdn site but still I get the same error on running the registerRExt.exe file.
The site shows while installing the instance the account name for Server Database engine has to be MSSQLSERVER, however this had also resulted in an error stating wait on database recovery handle failed which was sorted by changing the account name of Database engine to NT AUTHORITY/SYSTEM(I provided this info as it can also be the cause of the problem) . Now I need to sort the user pool failure. Any help would be appreciated..thanks in advance
SQL 2016 RC1 was just released https://blogs.technet.microsoft.com/dataplatforminsider/2016/03/18/sql-server-2016-release-candidate-1-now-available/.
SQL RC1 has a newer version 8.0.1 version of RRE. I suggest your try to install it and reply to this thread again if you hit the same failure. https://msdn.microsoft.com/library/mt590809.aspx has the details on where to find Microsoft R Open 8.0.1 and Revolution R Enterprise 8.0.1.
If the issue persists RevoScaleR\rxLibs\x64\registerrext.log would have more details on the exact failure - do share that.
I was able to sort out the issue..It was because I was installing the SQL server on domain controller and ignored the warning while install, but then changing some rules and demoting it from Server Manager worked and the install was successful.
However I do know there may be some better solution to that as all the other user accounts got reset in the process.
To brief a little, I have created 2 VM's; both VM's have same h/w and s/w configuration. They are running Windows server 2012.
Have installed SQL Server 2012 on them; both installation have 2 named instances; like
VM1 have SQLmaster
VM2 have SQLSlave
Now, when I try to connect to instance in VM2 from VM1 I am getting error:26
"SQL Network Interfaces, error: 26 - Error Locating Server/Instance
Specified"
Tried the solution/suggestions mentioned in below blogs but no luck.
http://blogs.msdn.com/b/sql_protocols/archive/2007/05/13/sql-network-interfaces-error-26-error-locating-server-instance-specified.aspx
http://social.msdn.microsoft.com/Forums/en-US/sqlsetupandupgrade/thread/69b8e727-eb51-4de1-b298-b3ff316bd071/
Any idea, how can I get rid of this.
NOTE: I am actually trying to configure "sqlserver 2012 alwayson" on this servers but getting stuck here.
Thanks.
Well, after troubling shooting for a bit I found out the solution. Below it is ... hope someone will be helped.
Resolution:
Open your network configuration(you can use the command ncpa.cpl)
Click properties
click on the IPV4 connection
On the general tab -> change the preferred DNS connection from default
(127.0.0.1) to the exact ip address of the domain controller.
I've searched Google for days, but cannot come up with any answers. A week ago, we did a server migration. We have a clustered environment where the following code works on one server, but not the other (and I cannot get it to work on my local machine for our non-clustered development environment):
rootDSE = New DirectoryEntry("LDAP://nonfullyqualifieddomain/RootDSE")
If I try the above, I get the generic error mentioned in the question title (Again, it works on one of the servers, but not the other).
However, when I do this the DirectoryEntry object is instantiated:
rootDSE = New DirectoryEntry("LDAP://fully.qualified.domain", adUserId, adPassword, AuthenticationTypes.Secure)
Based on what I see online, my best guess is that it has something to do with permissions or configurations, but I'm not familiar with the server administration side of the application. Any suggestions would be appreciated!
Every time I've got the "Server not operational" in one of the infrastructure I worked on, it was because I was trying to connect an LDAP server on a bad adress. This was due to :
Bad DNS resolution
Bad Netbios resolution
Firewall filtering
My advice it to use DNS resolution for production and test environment, and to use direct IP adress for development environment.
Be sure 389 (or 636) port is binded on the adress you use and you can connect to it. On Windows Server 2008 LDP.EXE is a good tool to test LDAP connexion (present in W2K3 ressource kit). On development computer I use Apache Directory Studio which is also a good tool to test Directory connectivity and content.
I have come across the same error in one of our legacy applications. This is a memory leak issue. To work around this, I made sure that the code was disposing of the Directory entry once done using it. Something like:
using (System.DirectoryServices.DirectoryEntry OUEntry
= new DirectoryEntry(domain, userName, userPassword))
{
// your code here
}