Failed to log on to Microsoft Windows with Symantec Backup Exec 2012
When we try to make backup selections with Backup Exec in Windows 2008R2 we receive a message with error that says: Failed to log on to Microsoft Windows. The OS is Windows 2008R2 SP1 and the App is Symantec Backup Exec 2012 SP1 This problema started with one or two clients from the begining of the installation and continue with the others in the las days, we have 3 weeks with the servers installed. We enabled the debug log of Backup Exec 2012 to review why is this happening and faund the next log: [10496] 2012-07-13T11:46:31.751 [ndmp\ndmpcomm] - Could not resolve the "bews-ndmp" or the "ndmp" service, error code: 10109, using port 10000 [10496] 2012-07-13T11:46:31.752 [ndmp\ndmpcomm] - ndmpConnectEx: 'SERVER NAME' resolves to the local machine itself. So, we will try and connect to a loopback address ... [10496] 2012-07-13T11:46:31.752 [ndmp\ndmpcomm] - ndmpConnectEx : Control Connection information: A connection was established between end-points [::1]:59820 and [::1]:10000. [5832] 2012-07-13T11:46:31.953 [ndmp\ndmpcomm] - ndmpRun: Control connection accepted : connection established between end-points [::1]:10000 and [::1]:59820 [10496] 2012-07-13T11:46:31.953 [ndmp\ndmpclient] - NDMP version 3 connection CONNECTED [10752] 2012-07-13T11:46:31.966 [ndmp\ndmpsrvr] - sslOpen() : Opening SSL for: 00000000EB196B9F [10752] 2012-07-13T11:46:31.966 [ndmp\ndmpsrvr] - sslOpen(): certinfo = 00000000E8C53E5F ; sslConn = 00000000DF7AD96F [10496] 2012-07-13T11:46:31.966 [ndmp\ndmpclient] - connectClientAuth(): agent is on local loopback, skipping SSL connection... [10752] 2012-07-13T11:46:32.032 [ndmp\ndmpsrvr] - ndmpdConnectClientAuth(): agent is on local loopback, skipping SSL connection... [10752] 2012-07-13T11:46:32.035 [ndmp\ndmpsrvr] - Username for Logon: DOMAIN\backupexec [10752] 2012-07-13T11:46:32.036 + impersonator.cpp (416): [10752] 2012-07-13T11:46:32.036 | BELogonUser: beclass::IsThisMe() returned error: 87 [10752] 2012-07-13T11:46:32.036 + impersonator.cpp (478): [10752] 2012-07-13T11:46:32.036 | LogonType set = [LOGON32_LOGON_BATCH][0x4] [10752] 2012-07-13T11:46:32.090 + impersonator.cpp (505): [10752] 2012-07-13T11:46:32.090 | LogonUser failed: Logon failure: the user has not been granted the requested logon type at this computer. [10752] 2012-07-13T11:46:32.090 [ndmp\ndmpsrvr] - LogonuserError: 1385 [10752] 2012-07-13T11:46:32.090 [ndmp\ndmpsrvr] - LogonUser failed for user: DOMAIN\backupexec [10496] 2012-07-13T11:46:32.090 [ndmp\ndmpcomm] - ERROR: 69 Error: Windows LogonUser API failed. [10496] 2012-07-13T11:46:32.090 [ndmp\ndmpclient] - *** getLastNDMPError Calling to get last NDMP Error. [10752] 2012-07-13T11:46:32.091 [ndmp\ndmpsrvr] - In ndmpdGetLastError:: Callback to get last NDMP Error. [10496] 2012-07-13T11:46:32.091 [BESocket] - @@@@@@@MyCloseSocket called with sockfd = 1340(0x53c) retval = 0 [10752] 2012-07-13T11:46:32.091 [ndmp\ndmpcomm] - ndmp_readit: Caught message on closed connection. Socket 0x328 len 0x0 [10752] 2012-07-13T11:46:32.091 [ndmp\ndmpcomm] - ndmp_readit: ErrorCode :: 0 : [10752] 2012-07-13T11:46:32.091 [ndmp\tpfmt] - FreeFormatEnv( cur_fmt=0 ) [10752] 2012-07-13T11:46:32.091 [ndmp\tpfmt] - FreeFormatEnv( cur_fmt=0 ) [10752] 2012-07-13T11:46:32.092 [ndmp\ndmpsrvr] - sslClose() : Closing SSL for: 00000000EB196B9F [10752] 2012-07-13T11:46:32.092 [BESocket] - @@@@@@@MyCloseSocket called with sockfd = 808(0x328) retval = 0 [10496] 2012-07-13T11:46:42.080 [dsss] + dsserver.cpp (744): [10496] 2012-07-13T11:46:42.080 [dsss] | DS_CloseSelectionService [10496] 2012-07-13T11:46:42.080 [dsss] + dsserver.cpp (623): [10496] 2012-07-13T11:46:42.080 [dsss] | DS session handle: 000000000D6E5300(0000000000F575F0) closed. [8160] 2012-07-13T11:46:42.080 [dsss\srv] - DsWorkerThread terminating with exit code 0 After review the log we could find these message errors: - Could not resolve the "bews-ndmp" or the "ndmp" service, error code: 10109, using port 10000 | BELogonUser: beclass::IsThisMe() returned error: 87 | LogonUser failed: Logon failure: the user has not been granted the requested logon type at this computer. LogonuserError: 1385 LogonUser failed for user: DOMAIN\backupexec ERROR: 69 Error: Windows LogonUser API failed. - *** getLastNDMPError Calling to get last NDMP Error. In ndmpdGetLastError:: Callback to get last NDMP Error. Looking what these errors means I found this with NET HELMSG in DOS window: People from support of Symantec says this problema is whith Windows and they could not do anything. Some body else have been Works with problem?
July 13th, 2012 1:44pm

[10752] 2012-07-13T11:46:32.090 | LogonUser failed: Logon failure: the user has not been granted the requested logon type at this computer. Are you sure the account is a local admin on the server? The erromessages indicate a connectivity issue. See what happens when you try to connect to the server from the backup server witha standard \\server\c$ command. My Knee Jerk Reaction.BlankMonkey
Free Windows Admin Tool Kit Click here and download it now
July 13th, 2012 4:09pm

The server access without problem by windows explorer, the issue only is presented with the application, people from Symantec detected the error number and discard the Application as the problem, they suggested the OS has a BUG and we need assistant from Microsoft. This problem started with the acces to one of eight client servers, and continue growing up today with 6 servers with problems. Thank you!Microsoft TechNet Forums
July 19th, 2012 11:29pm

This is an application problem not related to windows Servers. It's better to ask this question in Symantec Backup Exec Forum for assistance. http://www.symantec.com/connect/backup-and-recovery/forums/backup-execDon't be a prick ! Be reasonable and provide your feedback. Say something whether the suggestion was helpful or not, mark a reply as answer or click on to vote helpful if any suggestion really helps you, don't leave that choice to moderators, let the credit go to a contributor who has invested his precious time on your questions. Please be informed that, moderators are also humans and they also make mistakes ;-) Last but not the least, Unmark as answer if any post doesn't answer your question/s !!!
Free Windows Admin Tool Kit Click here and download it now
July 20th, 2012 2:07am

This is an application problem not related to windows Servers. It's better to ask this question in Symantec Backup Exec Forum for assistance. http://www.symantec.com/connect/backup-and-recovery/forums/backup-execDon't be a prick ! Be reasonable and provide your feedback. Say something whether the suggestion was helpful or not, mark a reply as answer or click on to vote helpful if any suggestion really helps you, don't leave that choice to moderators, let the credit go to a contributor who has invested his precious time on your questions. Please be informed that, moderators are also humans and they also make mistakes ;-) Last but not the least, Unmark as answer if any post doesn't answer your question/s !!!
July 20th, 2012 2:07am

The server access without problem by windows explorer, the issue only is presented with the application, people from Symantec detected the error number and discard the Application as the problem, they suggested the OS has a BUG and we need assistant from Microsoft. Sorry to say this but Symantec Support always does this kind of job, that is passing ball on the others court. You better escalate this with Symantec again.Don't be a prick ! Be reasonable and provide your feedback. Say something whether the suggestion was helpful or not, mark a reply as answer or click on to vote helpful if any suggestion really helps you, don't leave that choice to moderators, let the credit go to a contributor who has invested his precious time on your questions. Please be informed that, moderators are also humans and they also make mistakes ;-) Last but not the least, Unmark as answer if any post doesn't answer your question/s !!!
Free Windows Admin Tool Kit Click here and download it now
July 20th, 2012 2:09am

Hello Oscar. I am a Product Mgr for BE at Symantec. Do you have a Tech Support case ID# If you can get that to me, I will follow up and see what we can do. Feel free to DM me if you like.
July 20th, 2012 10:07am

Hi Matt, the Case Number is: 418-475-113 I allready change my OS to Windows 2003R2 and will start testing today at night, next week I will describe results in this forum. OscarMicrosoft TechNet Forums
Free Windows Admin Tool Kit Click here and download it now
July 20th, 2012 10:23am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics