August 14, 2008 at 4:52 am
Hi all,
we have a strange behaviour in our environment.
A colleague of mine wants to setup a backup job, but backup exec 10d (and also 11) on the backup server cannot access the instance on the database server, which should be backed up.
The error in the event log is the following:
Event ID: 57860 Source: Backup Exec Type: Error Description: An error occurred while attempting to log in to the following server: "ourserver\ourinstance". SQL error number: "0000". SQL error message ""
The account, which runs BackupExec, is also member of the Builtin\Administrators group on the database server.
Another strange thing: if I start osql.exe (with -S servername\instancename -E) on the backup server, I can connect properly to the database server.
Both servers are W2k3, the backup server 32bit, DB server 64bit.
SQL Server is 64bit Std. Ed.
Does anyone got the same error on the past or has an idea what may go wrong?
Best regards
Dirk
--
May you never suffer the sentiment of spending a day without any purpose.
@DirkHondong on Twitter
August 14, 2008 at 9:38 am
Is anything else successfully connecting to the instance? If so, did the BUILTIN\Administrators group get removed?
K. Brian Kelley
@kbriankelley
August 14, 2008 at 11:53 am
Yes, beside the Builtin-Admins there is a service account (windows auth), which connects to that instance to get access to a virtual center database.
The Builtin-Admins never got removed.
Also, I put the backup account directly to the logins and granted access (e.g. without putting the account into a user group such as Builtin\Admins) with the same error mentioned above.
--
May you never suffer the sentiment of spending a day without any purpose.
@DirkHondong on Twitter
August 14, 2008 at 1:48 pm
When you check SQL Server Configuration Manager, is the TCP/IP protocol enabled? If so, is the SQL Browser service running? If so, note the port for TCP/IP, if you connect using *hostname*,*port* from remote, does that work?
K. Brian Kelley
@kbriankelley
August 14, 2008 at 2:23 pm
Yes, TCP is enabled.
Browser is running and we even tried to connect via IP and Port number.
Everything looks fine.
We also see the server with the instance in the BackupExec Browser.
But once we select the instance to choose a database for backup, we get the error.
Symantec Support is also involved, but they have no idea.
--
May you never suffer the sentiment of spending a day without any purpose.
@DirkHondong on Twitter
August 14, 2008 at 2:37 pm
If you have audit logon failures turned on at the OS level, do you see the failures in the Security event log?
K. Brian Kelley
@kbriankelley
August 15, 2008 at 4:28 am
Hi again,
I have just checked the sec-logs.
Nothing unusual to see.
It is really a strange behaviour.
My colleague runs a workaround.
First, creating a dump file via SQL manager and afterwards just backing up the dumpfile itself.
--
May you never suffer the sentiment of spending a day without any purpose.
@DirkHondong on Twitter
August 15, 2008 at 7:11 am
Can you connect to the server remotely at all?
If not, is there an error in the SQL Server error log indicating it couldn't bind to the port?
K. Brian Kelley
@kbriankelley
August 15, 2008 at 7:31 am
Yes, other remote access is possible and there are no errors in the sql log.
--
May you never suffer the sentiment of spending a day without any purpose.
@DirkHondong on Twitter
August 15, 2008 at 2:56 pm
Can you create an ODBC connection (and successfully test the connection) from the server where NetBackup is running to the named instance?
K. Brian Kelley
@kbriankelley
August 18, 2008 at 1:41 am
Hello Brian,
First, thanks for your endeavor.
I just created an ODBC conenction and it works fine.
Also, the backup server can access other database engines (SQL 2K and 2K5).
Greetings
Dirk
--
May you never suffer the sentiment of spending a day without any purpose.
@DirkHondong on Twitter
August 18, 2008 at 1:58 pm
Well, that rules out a network or SQL Server issue. That would point to the application... not sure where you go from here if Symantec support is stuck.
K. Brian Kelley
@kbriankelley
May 19, 2009 at 12:55 pm
Hi again,
although my issue is nearly one year old a colleague and I still experience the problem.
What I did last week was to install two new instances beside the existing one which we cannot access via backup exec.
I can see the new instances in backup exec but still cannot list the databases. So BE has no chance to query the instance.
On the target database server I have created again the message I have mentioned in my first post here:
An error occurred while attempting to log in to the following server:
"xxxMyDbServer\BETestInstance".
SQL error number: "0000".
SQL error message: "".
Interersting thing is that this entry was only in the app log, but not in the SQL Server log.
So I've started a trace logging all logins and logouts against the instance.
And what happened? Nothing.
When I want to list the databases from BE, I get no information via SQL Profiler but I create the error message mentioned above in the app log.
We also re-installed the BE Agent several times without any advance.
Otherwise I would try to get support from one of the invovled companies, e.g. Symantec (again) or Microsoft.
Regards
Dirk
--
May you never suffer the sentiment of spending a day without any purpose.
@DirkHondong on Twitter
Viewing 13 posts - 1 through 12 (of 12 total)
You must be logged in to reply to this topic. Login to reply