SQL Agent Error

I am having problems connecting to SQL in order to back up my database. The
servers are in a small workgroup, with this environment:

Backup Server
Windows NT 4
BENT 8.6 v3878
Remote Agent
SQL Agent
Open File

Remote Server
Windows NT 4
SQL 7
BENT Remote Agent (8.6.3878)

When I go to the Backup Selections tab, and click down to my remote server,
whenever I click on MS SQL Server, I get a pop-up error that states "A
communications failure has occurred." In addition to that, the following
error is placed in the NT Event Log:
Event Type: Error
Event Source: Backup Exec
Event Category: None
Event ID: 57857
User: N/A
Description:
An error occurred while attempting to log in to the following server:
"WLMSQL".
OS error message: "ConnectionOpen (CreateFile()).".
DBLIB error message: "Unable to connect: SQL Server is unavailable or does
not exist.".
Server error message: "".
Data:
0000: 00 00 00 00 09 00 00 00 ........
0008: 14 27 00 00 2e 05 00 00 .'......

I have tried changing the "attach as" user information, but even when I
enter in the correct SA info, I still get that error. What can be wrong?

Thanks.
Josh

Hi Joshua

When Backing up a SQL 7.0 Server, or SQL 2000 server, which resides in another
domain, or in a workgroup, the error "The Item Was Not Found" may appear.
This is because the Backup Exec service account, does not have rights in
the other domain, or passthru authentication is not setup inside the workgroup.
Note
----
If SQL Server v7.0 and SQL Server 2000 are installed on a single computer,
duplicate SQL Server icons may also appear in the Backup Selections tab,
or named instances of SQL Server 2000 may not appear and restore to the default
directory may not work. This situation occurs if Backup Exec does not have
proper access rights to read both SQL Server registry keys:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server and

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer

To ensure that Backup Exec has proper access rights, verify that the account
that Backup Exec uses has administrator rights to the computer that is running
SQL Server. The backup server must have access to Microsoft SQL Server. To
make sure that the Backup Exec service account has proper access, perform
one of the following:
1. If the SQL Server resides in another domain, create a trust relationship
between the two domains. Once the trust relationship has been established,
add the Backup Exec Service Account to the SQL Server's Domains "Administrators"
Group.
OR
2. If the SQL Server resides in a workgroup, create a user locally on the
SQL server, with the same username and password, as the account specified
for the Backup Exec services. Then add this user to the Administrator's group.
Acknowledgments:
Microsoft Article ID: Q308195; Backup Exec for Windows NT and Windows 2000
v8.6 Administrator's Guide.

Many thanks,
Dr

"Joshua Campbell" <Joshua.Campbell@WellmanInc-DieSpamDie.com> wrote:[color=blue]
>I am having problems connecting to SQL in order to back up my database.[/color]
The[color=blue]
>servers are in a small workgroup, with this environment:
>
>Backup Server
> Windows NT 4
> BENT 8.6 v3878
> Remote Agent
> SQL Agent
> Open File
>
>Remote Server
> Windows NT 4
> SQL 7
> BENT Remote Agent (8.6.3878)
>
>When I go to the Backup Selections tab, and click down to my remote server,
>whenever I click on MS SQL Server, I get a pop-up error that states "A
>communications failure has occurred." In addition to that, the following
>error is placed in the NT Event Log:
>Event Type: Error
>Event Source: Backup Exec
>Event Category: None
>Event ID: 57857
>User: N/A
>Description:
>An error occurred while attempting to log in to the following server:
>"WLMSQL".
> OS error message: "ConnectionOpen (CreateFile()).".
> DBLIB error message: "Unable to connect: SQL Server is unavailable or does
>not exist.".
> Server error message: "".
>Data:
>0000: 00 00 00 00 09 00 00 00 ........
>0008: 14 27 00 00 2e 05 00 00 .'......
>
>I have tried changing the "attach as" user information, but even when I
>enter in the correct SA info, I still get that error. What can be wrong?
>
>Thanks.
>Josh
>
>
>
>[/color]

Okay, so you're saying that I should make sure that the account that the
Backup Exec services run under on the backup server are admins on the SQL
server, right? In a workgroup environment, how do I do that? When in user
admin on the SQL server and I click on Add in the Administrator group, I
can't change servers. Or, (according to #2 below) should I create an
account on both servers, using the same username and password, assuming that
it will just assume the server name part? I never was good at trusts...

Thanks.
Joshua



"Backup Dr." <backupexecdr@terra.com> wrote in message
news:3d6343de$1@hronntp01....[color=blue]
>
> Hi Joshua
>
> When Backing up a SQL 7.0 Server, or SQL 2000 server, which resides in[/color]
another[color=blue]
> domain, or in a workgroup, the error "The Item Was Not Found" may appear.
> This is because the Backup Exec service account, does not have rights in
> the other domain, or passthru authentication is not setup inside the[/color]
workgroup.[color=blue]
> Note
> ----
> If SQL Server v7.0 and SQL Server 2000 are installed on a single computer,
> duplicate SQL Server icons may also appear in the Backup Selections tab,
> or named instances of SQL Server 2000 may not appear and restore to the[/color]
default[color=blue]
> directory may not work. This situation occurs if Backup Exec does not have
> proper access rights to read both SQL Server registry keys:
>
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server and
>
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer
>
> To ensure that Backup Exec has proper access rights, verify that the[/color]
account[color=blue]
> that Backup Exec uses has administrator rights to the computer that is[/color]
running[color=blue]
> SQL Server. The backup server must have access to Microsoft SQL Server. To
> make sure that the Backup Exec service account has proper access, perform
> one of the following:
> 1. If the SQL Server resides in another domain, create a trust[/color]
relationship[color=blue]
> between the two domains. Once the trust relationship has been established,
> add the Backup Exec Service Account to the SQL Server's Domains[/color]
"Administrators"[color=blue]
> Group.
> OR
> 2. If the SQL Server resides in a workgroup, create a user locally on the
> SQL server, with the same username and password, as the account specified
> for the Backup Exec services. Then add this user to the Administrator's[/color]
group.[color=blue]
> Acknowledgments:
> Microsoft Article ID: Q308195; Backup Exec for Windows NT and Windows 2000
> v8.6 Administrator's Guide.
>
> Many thanks,
> Dr
>
> "Joshua Campbell" <Joshua.Campbell@WellmanInc-DieSpamDie.com> wrote:[color=green]
> >I am having problems connecting to SQL in order to back up my database.[/color]
> The[color=green]
> >servers are in a small workgroup, with this environment:
> >
> >Backup Server
> > Windows NT 4
> > BENT 8.6 v3878
> > Remote Agent
> > SQL Agent
> > Open File
> >
> >Remote Server
> > Windows NT 4
> > SQL 7
> > BENT Remote Agent (8.6.3878)
> >
> >When I go to the Backup Selections tab, and click down to my remote[/color][/color]
server,[color=blue][color=green]
> >whenever I click on MS SQL Server, I get a pop-up error that states "A
> >communications failure has occurred." In addition to that, the following
> >error is placed in the NT Event Log:
> >Event Type: Error
> >Event Source: Backup Exec
> >Event Category: None
> >Event ID: 57857
> >User: N/A
> >Description:
> >An error occurred while attempting to log in to the following server:
> >"WLMSQL".
> > OS error message: "ConnectionOpen (CreateFile()).".
> > DBLIB error message: "Unable to connect: SQL Server is unavailable or[/color][/color]
does[color=blue][color=green]
> >not exist.".
> > Server error message: "".
> >Data:
> >0000: 00 00 00 00 09 00 00 00 ........
> >0008: 14 27 00 00 2e 05 00 00 .'......
> >
> >I have tried changing the "attach as" user information, but even when I
> >enter in the correct SA info, I still get that error. What can be wrong?
> >
> >Thanks.
> >Josh
> >
> >
> >
> >[/color]
>[/color]

I changed the service account info as directed in #2 and it works now. I
don't know why it stopped working, but at least it works now.

Thanks!
Josh


"Joshua Campbell" <Joshua.Campbell@WellmanInc-DieSpamDie.com> wrote in
message news:3d6374e2$1@hronntp01....[color=blue]
> Okay, so you're saying that I should make sure that the account that the
> Backup Exec services run under on the backup server are admins on the SQL
> server, right? In a workgroup environment, how do I do that? When in[/color]
user[color=blue]
> admin on the SQL server and I click on Add in the Administrator group, I
> can't change servers. Or, (according to #2 below) should I create an
> account on both servers, using the same username and password, assuming[/color]
that[color=blue]
> it will just assume the server name part? I never was good at trusts...
>
> Thanks.
> Joshua
>
>
>
> "Backup Dr." <backupexecdr@terra.com> wrote in message
> news:3d6343de$1@hronntp01....[color=green]
> >
> > Hi Joshua
> >
> > When Backing up a SQL 7.0 Server, or SQL 2000 server, which resides in[/color]
> another[color=green]
> > domain, or in a workgroup, the error "The Item Was Not Found" may[/color][/color]
appear.[color=blue][color=green]
> > This is because the Backup Exec service account, does not have rights in
> > the other domain, or passthru authentication is not setup inside the[/color]
> workgroup.[color=green]
> > Note
> > ----
> > If SQL Server v7.0 and SQL Server 2000 are installed on a single[/color][/color]
computer,[color=blue][color=green]
> > duplicate SQL Server icons may also appear in the Backup Selections tab,
> > or named instances of SQL Server 2000 may not appear and restore to the[/color]
> default[color=green]
> > directory may not work. This situation occurs if Backup Exec does not[/color][/color]
have[color=blue][color=green]
> > proper access rights to read both SQL Server registry keys:
> >
> > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server and
> >
> > HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer
> >
> > To ensure that Backup Exec has proper access rights, verify that the[/color]
> account[color=green]
> > that Backup Exec uses has administrator rights to the computer that is[/color]
> running[color=green]
> > SQL Server. The backup server must have access to Microsoft SQL Server.[/color][/color]
To[color=blue][color=green]
> > make sure that the Backup Exec service account has proper access,[/color][/color]
perform[color=blue][color=green]
> > one of the following:
> > 1. If the SQL Server resides in another domain, create a trust[/color]
> relationship[color=green]
> > between the two domains. Once the trust relationship has been[/color][/color]
established,[color=blue][color=green]
> > add the Backup Exec Service Account to the SQL Server's Domains[/color]
> "Administrators"[color=green]
> > Group.
> > OR
> > 2. If the SQL Server resides in a workgroup, create a user locally on[/color][/color]
the[color=blue][color=green]
> > SQL server, with the same username and password, as the account[/color][/color]
specified[color=blue][color=green]
> > for the Backup Exec services. Then add this user to the Administrator's[/color]
> group.[color=green]
> > Acknowledgments:
> > Microsoft Article ID: Q308195; Backup Exec for Windows NT and Windows[/color][/color]
2000[color=blue][color=green]
> > v8.6 Administrator's Guide.
> >
> > Many thanks,
> > Dr
> >
> > "Joshua Campbell" <Joshua.Campbell@WellmanInc-DieSpamDie.com> wrote:[color=darkred]
> > >I am having problems connecting to SQL in order to back up my database.[/color]
> > The[color=darkred]
> > >servers are in a small workgroup, with this environment:
> > >
> > >Backup Server
> > > Windows NT 4
> > > BENT 8.6 v3878
> > > Remote Agent
> > > SQL Agent
> > > Open File
> > >
> > >Remote Server
> > > Windows NT 4
> > > SQL 7
> > > BENT Remote Agent (8.6.3878)
> > >
> > >When I go to the Backup Selections tab, and click down to my remote[/color][/color]
> server,[color=green][color=darkred]
> > >whenever I click on MS SQL Server, I get a pop-up error that states "A
> > >communications failure has occurred." In addition to that, the[/color][/color][/color]
following[color=blue][color=green][color=darkred]
> > >error is placed in the NT Event Log:
> > >Event Type: Error
> > >Event Source: Backup Exec
> > >Event Category: None
> > >Event ID: 57857
> > >User: N/A
> > >Description:
> > >An error occurred while attempting to log in to the following server:
> > >"WLMSQL".
> > > OS error message: "ConnectionOpen (CreateFile()).".
> > > DBLIB error message: "Unable to connect: SQL Server is unavailable or[/color][/color]
> does[color=green][color=darkred]
> > >not exist.".
> > > Server error message: "".
> > >Data:
> > >0000: 00 00 00 00 09 00 00 00 ........
> > >0008: 14 27 00 00 2e 05 00 00 .'......
> > >
> > >I have tried changing the "attach as" user information, but even when I
> > >enter in the correct SA info, I still get that error. What can be[/color][/color][/color]
wrong?[color=blue][color=green][color=darkred]
> > >
> > >Thanks.
> > >Josh
> > >
> > >
> > >
> > >[/color]
> >[/color]
>
>[/color]

I made these changes and it worked once. Then I had to reboot my system and
now it will not work any more. The account that runs the services on the
Backup Server uses the same username and password of an administrator on the
SQL server.

What else could be wrong?

Thanks.
Josh




"Backup Dr." <backupexecdr@terra.com> wrote in message
news:3d6343de$1@hronntp01....[color=blue]
>
> Hi Joshua
>
> When Backing up a SQL 7.0 Server, or SQL 2000 server, which resides in[/color]
another[color=blue]
> domain, or in a workgroup, the error "The Item Was Not Found" may appear.
> This is because the Backup Exec service account, does not have rights in
> the other domain, or passthru authentication is not setup inside the[/color]
workgroup.[color=blue]
> Note
> ----
> If SQL Server v7.0 and SQL Server 2000 are installed on a single computer,
> duplicate SQL Server icons may also appear in the Backup Selections tab,
> or named instances of SQL Server 2000 may not appear and restore to the[/color]
default[color=blue]
> directory may not work. This situation occurs if Backup Exec does not have
> proper access rights to read both SQL Server registry keys:
>
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server and
>
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer
>
> To ensure that Backup Exec has proper access rights, verify that the[/color]
account[color=blue]
> that Backup Exec uses has administrator rights to the computer that is[/color]
running[color=blue]
> SQL Server. The backup server must have access to Microsoft SQL Server. To
> make sure that the Backup Exec service account has proper access, perform
> one of the following:
> 1. If the SQL Server resides in another domain, create a trust[/color]
relationship[color=blue]
> between the two domains. Once the trust relationship has been established,
> add the Backup Exec Service Account to the SQL Server's Domains[/color]
"Administrators"[color=blue]
> Group.
> OR
> 2. If the SQL Server resides in a workgroup, create a user locally on the
> SQL server, with the same username and password, as the account specified
> for the Backup Exec services. Then add this user to the Administrator's[/color]
group.[color=blue]
> Acknowledgments:
> Microsoft Article ID: Q308195; Backup Exec for Windows NT and Windows 2000
> v8.6 Administrator's Guide.
>
> Many thanks,
> Dr
>
> "Joshua Campbell" <Joshua.Campbell@WellmanInc-DieSpamDie.com> wrote:[color=green]
> >I am having problems connecting to SQL in order to back up my database.[/color]
> The[color=green]
> >servers are in a small workgroup, with this environment:
> >
> >Backup Server
> > Windows NT 4
> > BENT 8.6 v3878
> > Remote Agent
> > SQL Agent
> > Open File
> >
> >Remote Server
> > Windows NT 4
> > SQL 7
> > BENT Remote Agent (8.6.3878)
> >
> >When I go to the Backup Selections tab, and click down to my remote[/color][/color]
server,[color=blue][color=green]
> >whenever I click on MS SQL Server, I get a pop-up error that states "A
> >communications failure has occurred." In addition to that, the following
> >error is placed in the NT Event Log:
> >Event Type: Error
> >Event Source: Backup Exec
> >Event Category: None
> >Event ID: 57857
> >User: N/A
> >Description:
> >An error occurred while attempting to log in to the following server:
> >"WLMSQL".
> > OS error message: "ConnectionOpen (CreateFile()).".
> > DBLIB error message: "Unable to connect: SQL Server is unavailable or[/color][/color]
does[color=blue][color=green]
> >not exist.".
> > Server error message: "".
> >Data:
> >0000: 00 00 00 00 09 00 00 00 ........
> >0008: 14 27 00 00 2e 05 00 00 .'......
> >
> >I have tried changing the "attach as" user information, but even when I
> >enter in the correct SA info, I still get that error. What can be wrong?
> >
> >Thanks.
> >Josh
> >
> >
> >
> >[/color]
>[/color]