This forum is closed to new posts and responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:

HCL Software Customer Support Portal for U.S. Federal Government clients
HCL Software Customer Support Portal


Aug 22, 2015, 6:11 PM
1 Posts

ATTEMPT TO ACCESS SERVER by <SERVERNAME> was denied

  • Category: Replication
  • Platform: Windows
  • Release: 9.0.1
  • Role: Administrator
  • Tags:
  • Replies: 3

My four production servers have not been replicating since 8/19 at around 1 PM US CDT. I get thousands of messages like these in the logs.

08/19/2015 01:02:27 PM ATTEMPT TO ACCESS SERVER by <SERVERNAME> was denied
08/19/2015 01:02:31 PM Error connecting to server
<SERVERNAME>: Server error: You are not authorized to use the server
08/19/2015 01:02:31 PM Error occurred when trying to notify DDM server [
<SERVERNAME>] to collect: You are not authorized to use the server

The most recent event in the environment was upgrade from 8.5.3 to 9.0.1 FP4 on 7/29/2015. Windows patches were also applied and the server restarted around 9 PM US CDT on 8/18/2015.

The servers are in two clustered pairs with scheduled replication between the pairs every 15 minutes to keep names.nsf, etc., up to date.

The O, OU and server certs/IDs all expire in the year 2022. All are 64 bit certs, which sounds old to me, but I can't find any references online that this certificate strength has be deprecated.

The Server document > Security > Access server setting has never had LocalDomainServers in it, but */<DOMAINNAME> has always been in the field so I don't think that is an issue. However, IBM asked that I add LocalDomainServers, which has been done and the servers restarted last night. This did not solve the issue. This environment configuration (four prod servers in two clustered pairs on Windows VM 64 bit) has been installed and working with this configuration since September 2013.

Does anyone have any ideas what can be causing this? It seems to have come out of nowhere.

Thanks.

Aug 22, 2015, 6:58 PM
34 Posts
Deny access group

Hi,

do you use Deny Access Groups? I would check the "Not access server" field, are there replication conflicts of servers in your directory?

Check $users and $server for duplicates.

Are all servers updated to 9.0.1?

And check your server notes.ini for:

server_restricted

 

Regards

Chris

Aug 22, 2015, 8:32 PM
212 Posts
DDM error

check to ensure that you only have one server running DDM, and that you have a proper DDM heirarchy set up.  Check to see if the server is trying to collect DDM stats from itself.  This sounds like something is occurring with the DDM configuration.

Aug 25, 2015, 1:01 PM
48 Posts
Re "ATTEMPT TO ACCESS SERVER by <SERVERNAME> was denied"
Hi Gregg

Re

"ATTEMPT TO ACCESS SERVER by <SERVERNAME> was denied"

This error message is typically generated due to a server access
setting in the server document.


To troubleshoot this issue, check the Server document to see if the "Only Allow Server Access to Users Listed in This Address Book" field is set to Yes.  This field is located in the Server Access section of the Server document.

If this is the case, try adding the  server name explicitly  to the "Access Server" field.  Even though leaving this field blank means "none allows all," the server name or LocalDomainServers group must be added to this field.

Hope this helps
TomOC

This forum is closed to new posts and responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:

HCL Software Customer Support Portal for U.S. Federal Government clients
HCL Software Customer Support Portal