How do you connect to the SQL server through BENT? Via an SA user, windows
administrator user or a separate windows user?

Did you just change the local administrator password on the media server, or
the domain administrator password (assuming the media and sql servers are
separate).

If they are on the same server, is SQL running successfully?

If SQL is running successfully, and either SQL is on the media server, or it
was the domain administrator password that you changed, check if the SQL
Server Agent Service is running, and if not, is it (unlike the SQL Server
service) set to run as the administrator? If so you'll need to change the
login info for the service.

Keith

"Darin Duncan" wrote in message
news:3eb91678@hronntp01....
> I am using Backup Exec ver. 8.6 for on Windows 2000 Server w/ SP3.
>
> I have been having good backups until last night's. The only thing that
has
> changed is that I changed the administrative password. After last night's
> backup failed, I was able to successfully change the connect as
information
> for all of my servers. What is got me confused is that under the "Job
> Definitions" tab I can successfully browse to the SQL server and connect.
> However, when I run the backup job, it errors out with the following
> message:
>
> The SQL server is not responding. DBCC aborted.
>
> Can someone please tell me what I am doing wrong?
>
> Thank you,
>
> --
> Darin Duncan, MCSE (NT 4.0)
> Dixie Chopper IT Dept.
> http://www.dixiechopper.com
>
>

The password that I changed was for the Domain Administrator account.

The media sever and the SQL server are separate machines. The SQL server
agent service is running.

The odd thing to me is that in the Job Definition, I can successfully
connect to the SQL server and select the databases for backup. The connect
as criteria for the SQL server itself is the domain administrator account
and the criteria for the SQL agent is "sa" user name with no password.

It makes no sense to me for it to connect under the job definition but not
while the job is running.

Thanks,

Darin


"Keith Langmead" wrote in message
news:3eba8aa8@hronntp01....
> How do you connect to the SQL server through BENT? Via an SA user, windows
> administrator user or a separate windows user?
>
> Did you just change the local administrator password on the media server,
or
> the domain administrator password (assuming the media and sql servers are
> separate).
>
> If they are on the same server, is SQL running successfully?
>
> If SQL is running successfully, and either SQL is on the media server, or
it
> was the domain administrator password that you changed, check if the SQL
> Server Agent Service is running, and if not, is it (unlike the SQL Server
> service) set to run as the administrator? If so you'll need to change the
> login info for the service.
>
> Keith
>
> "Darin Duncan" wrote in message
> news:3eb91678@hronntp01....
> > I am using Backup Exec ver. 8.6 for on Windows 2000 Server w/ SP3.
> >
> > I have been having good backups until last night's. The only thing that
> has
> > changed is that I changed the administrative password. After last
night's
> > backup failed, I was able to successfully change the connect as
> information
> > for all of my servers. What is got me confused is that under the "Job
> > Definitions" tab I can successfully browse to the SQL server and
connect.
> > However, when I run the backup job, it errors out with the following
> > message:
> >
> > The SQL server is not responding. DBCC aborted.
> >
> > Can someone please tell me what I am doing wrong?
> >
> > Thank you,
> >
> > --
> > Darin Duncan, MCSE (NT 4.0)
> > Dixie Chopper IT Dept.
> > http://www.dixiechopper.com
> >
> >
>
>

Well kinda.

When you are in the BEWS admin program, it runs under the security
context of the logged in user. When the job runs, it runs under the
context of the BEWS service account. That's why you see many people
here on the forum saying that they always logon to BEWS as the service
account.

Darin Duncan wrote:

>The password that I changed was for the Domain Administrator account.
>
>The media sever and the SQL server are separate machines. The SQL server
>agent service is running.
>
>The odd thing to me is that in the Job Definition, I can successfully
>connect to the SQL server and select the databases for backup. The connect
>as criteria for the SQL server itself is the domain administrator account
>and the criteria for the SQL agent is "sa" user name with no password.
>
>It makes no sense to me for it to connect under the job definition but not
>while the job is running.
>
>Thanks,
>
>Darin
>
>
>"Keith Langmead" wrote in message
>news:3eba8aa8@hronntp01....
>
>
>>How do you connect to the SQL server through BENT? Via an SA user, windows
>>administrator user or a separate windows user?
>>
>>Did you just change the local administrator password on the media server,
>>
>>
>or
>
>
>>the domain administrator password (assuming the media and sql servers are
>>separate).
>>
>>If they are on the same server, is SQL running successfully?
>>
>>If SQL is running successfully, and either SQL is on the media server, or
>>
>>
>it
>
>
>>was the domain administrator password that you changed, check if the SQL
>>Server Agent Service is running, and if not, is it (unlike the SQL Server
>>service) set to run as the administrator? If so you'll need to change the
>>login info for the service.
>>
>>Keith
>>
>>"Darin Duncan" wrote in message
>>news:3eb91678@hronntp01....
>>
>>
>>>I am using Backup Exec ver. 8.6 for on Windows 2000 Server w/ SP3.
>>>
>>>I have been having good backups until last night's. The only thing that
>>>
>>>
>>has
>>
>>
>>>changed is that I changed the administrative password. After last
>>>
>>>
>night's
>
>
>>>backup failed, I was able to successfully change the connect as
>>>
>>>
>>information
>>
>>
>>>for all of my servers. What is got me confused is that under the "Job
>>>Definitions" tab I can successfully browse to the SQL server and
>>>
>>>
>connect.
>
>
>>>However, when I run the backup job, it errors out with the following
>>>message:
>>>
>>>The SQL server is not responding. DBCC aborted.
>>>
>>>Can someone please tell me what I am doing wrong?
>>>
>>>Thank you,
>>>
>>>--
>>>Darin Duncan, MCSE (NT 4.0)
>>>Dixie Chopper IT Dept.
>>>http://www.dixiechopper.com
>>>
>>>
>>>
>>>
>>
>>
>
>
>
>

Please forgive my ignorance, but how do I do that and what do I need to do
once I do get that accomplished?

Darin

"Ken Putnam" wrote in message
news:3EBAA56F.3080003@nospam_usa.net...
> Well kinda.
>
> When you are in the BEWS admin program, it runs under the security
> context of the logged in user. When the job runs, it runs under the
> context of the BEWS service account. That's why you see many people
> here on the forum saying that they always logon to BEWS as the service
> account.
>
> Darin Duncan wrote:
>
> >The password that I changed was for the Domain Administrator account.
> >
> >The media sever and the SQL server are separate machines. The SQL server
> >agent service is running.
> >
> >The odd thing to me is that in the Job Definition, I can successfully
> >connect to the SQL server and select the databases for backup. The
connect
> >as criteria for the SQL server itself is the domain administrator account
> >and the criteria for the SQL agent is "sa" user name with no password.
> >
> >It makes no sense to me for it to connect under the job definition but
not
> >while the job is running.
> >
> >Thanks,
> >
> >Darin
> >
> >
> >"Keith Langmead" wrote in message
> >news:3eba8aa8@hronntp01....
> >
> >
> >>How do you connect to the SQL server through BENT? Via an SA user,
windows
> >>administrator user or a separate windows user?
> >>
> >>Did you just change the local administrator password on the media
server,
> >>
> >>
> >or
> >
> >
> >>the domain administrator password (assuming the media and sql servers
are
> >>separate).
> >>
> >>If they are on the same server, is SQL running successfully?
> >>
> >>If SQL is running successfully, and either SQL is on the media server,
or
> >>
> >>
> >it
> >
> >
> >>was the domain administrator password that you changed, check if the SQL
> >>Server Agent Service is running, and if not, is it (unlike the SQL
Server
> >>service) set to run as the administrator? If so you'll need to change
the
> >>login info for the service.
> >>
> >>Keith
> >>
> >>"Darin Duncan" wrote in message
> >>news:3eb91678@hronntp01....
> >>
> >>
> >>>I am using Backup Exec ver. 8.6 for on Windows 2000 Server w/ SP3.
> >>>
> >>>I have been having good backups until last night's. The only thing
that
> >>>
> >>>
> >>has
> >>
> >>
> >>>changed is that I changed the administrative password. After last
> >>>
> >>>
> >night's
> >
> >
> >>>backup failed, I was able to successfully change the connect as
> >>>
> >>>
> >>information
> >>
> >>
> >>>for all of my servers. What is got me confused is that under the "Job
> >>>Definitions" tab I can successfully browse to the SQL server and
> >>>
> >>>
> >connect.
> >
> >
> >>>However, when I run the backup job, it errors out with the following
> >>>message:
> >>>
> >>>The SQL server is not responding. DBCC aborted.
> >>>
> >>>Can someone please tell me what I am doing wrong?
> >>>
> >>>Thank you,
> >>>
> >>>--
> >>>Darin Duncan, MCSE (NT 4.0)
> >>>Dixie Chopper IT Dept.
> >>>http://www.dixiechopper.com
> >>>
> >>>
> >>>
> >>>
> >>
> >>
> >
> >
> >
> >
>

Rather than logging on to the BEWS server as you, logon as the BEWS
service account (what ever user-id you specified at install time). Then
just run the BEWS console as normal. any browsing you do now, should
have the same effects as when the job runs (unless you have selected
"Attach As" for some shares or databases.

Darin Duncan wrote:

>Please forgive my ignorance, but how do I do that and what do I need to do
>once I do get that accomplished?
>
>Darin
>
>"Ken Putnam" wrote in message
>news:3EBAA56F.3080003@nospam_usa.net...
>
>
>>Well kinda.
>>
>>When you are in the BEWS admin program, it runs under the security
>>context of the logged in user. When the job runs, it runs under the
>>context of the BEWS service account. That's why you see many people
>>here on the forum saying that they always logon to BEWS as the service
>>account.
>>
>>Darin Duncan wrote:
>>
>>
>>
>>>The password that I changed was for the Domain Administrator account.
>>>
>>>The media sever and the SQL server are separate machines. The SQL server
>>>agent service is running.
>>>
>>>The odd thing to me is that in the Job Definition, I can successfully
>>>connect to the SQL server and select the databases for backup. The
>>>
>>>
>connect
>
>
>>>as criteria for the SQL server itself is the domain administrator account
>>>and the criteria for the SQL agent is "sa" user name with no password.
>>>
>>>It makes no sense to me for it to connect under the job definition but
>>>
>>>
>not
>
>
>>>while the job is running.
>>>
>>>Thanks,
>>>
>>>Darin
>>>
>>>
>>>"Keith Langmead" wrote in message
>>>news:3eba8aa8@hronntp01....
>>>
>>>
>>>
>>>
>>>>How do you connect to the SQL server through BENT? Via an SA user,
>>>>
>>>>
>windows
>
>
>>>>administrator user or a separate windows user?
>>>>
>>>>Did you just change the local administrator password on the media
>>>>
>>>>
>server,
>
>
>>>>
>>>>
>>>or
>>>
>>>
>>>
>>>
>>>>the domain administrator password (assuming the media and sql servers
>>>>
>>>>
>are
>
>
>>>>separate).
>>>>
>>>>If they are on the same server, is SQL running successfully?
>>>>
>>>>If SQL is running successfully, and either SQL is on the media server,
>>>>
>>>>
>or
>
>
>>>>
>>>>
>>>it
>>>
>>>
>>>
>>>
>>>>was the domain administrator password that you changed, check if the SQL
>>>>Server Agent Service is running, and if not, is it (unlike the SQL
>>>>
>>>>
>Server
>
>
>>>>service) set to run as the administrator? If so you'll need to change
>>>>
>>>>
>the
>
>
>>>>login info for the service.
>>>>
>>>>Keith
>>>>
>>>>"Darin Duncan" wrote in message
>>>>news:3eb91678@hronntp01....
>>>>
>>>>
>>>>
>>>>
>>>>>I am using Backup Exec ver. 8.6 for on Windows 2000 Server w/ SP3.
>>>>>
>>>>>I have been having good backups until last night's. The only thing
>>>>>
>>>>>
>that
>
>
>>>>>
>>>>>
>>>>has
>>>>
>>>>
>>>>
>>>>
>>>>>changed is that I changed the administrative password. After last
>>>>>
>>>>>
>>>>>
>>>>>
>>>night's
>>>
>>>
>>>
>>>
>>>>>backup failed, I was able to successfully change the connect as
>>>>>
>>>>>
>>>>>
>>>>>
>>>>information
>>>>
>>>>
>>>>
>>>>
>>>>>for all of my servers. What is got me confused is that under the "Job
>>>>>Definitions" tab I can successfully browse to the SQL server and
>>>>>
>>>>>
>>>>>
>>>>>
>>>connect.
>>>
>>>
>>>
>>>
>>>>>However, when I run the backup job, it errors out with the following
>>>>>message:
>>>>>
>>>>>The SQL server is not responding. DBCC aborted.
>>>>>
>>>>>Can someone please tell me what I am doing wrong?
>>>>>
>>>>>Thank you,
>>>>>
>>>>>--
>>>>>Darin Duncan, MCSE (NT 4.0)
>>>>>Dixie Chopper IT Dept.
>>>>>http://www.dixiechopper.com
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>
>
>
>
>

How do you logon as a service account? I have never logged onto the server
console as any user other than the domain administrator account (this
includes when I installed).


"Ken Putnam" wrote in message
news:3EBAAF01.2000308@nospam_usa.net...
> Rather than logging on to the BEWS server as you, logon as the BEWS
> service account (what ever user-id you specified at install time). Then
> just run the BEWS console as normal. any browsing you do now, should
> have the same effects as when the job runs (unless you have selected
> "Attach As" for some shares or databases.
>
> Darin Duncan wrote:
>
> >Please forgive my ignorance, but how do I do that and what do I need to
do
> >once I do get that accomplished?
> >
> >Darin
> >
> >"Ken Putnam" wrote in message
> >news:3EBAA56F.3080003@nospam_usa.net...
> >
> >
> >>Well kinda.
> >>
> >>When you are in the BEWS admin program, it runs under the security
> >>context of the logged in user. When the job runs, it runs under the
> >>context of the BEWS service account. That's why you see many people
> >>here on the forum saying that they always logon to BEWS as the service
> >>account.
> >>
> >>Darin Duncan wrote:
> >>
> >>
> >>
> >>>The password that I changed was for the Domain Administrator account.
> >>>
> >>>The media sever and the SQL server are separate machines. The SQL
server
> >>>agent service is running.
> >>>
> >>>The odd thing to me is that in the Job Definition, I can successfully
> >>>connect to the SQL server and select the databases for backup. The
> >>>
> >>>
> >connect
> >
> >
> >>>as criteria for the SQL server itself is the domain administrator
account
> >>>and the criteria for the SQL agent is "sa" user name with no password.
> >>>
> >>>It makes no sense to me for it to connect under the job definition but
> >>>
> >>>
> >not
> >
> >
> >>>while the job is running.
> >>>
> >>>Thanks,
> >>>
> >>>Darin
> >>>
> >>>
> >>>"Keith Langmead" wrote in message
> >>>news:3eba8aa8@hronntp01....
> >>>
> >>>
> >>>
> >>>
> >>>>How do you connect to the SQL server through BENT? Via an SA user,
> >>>>
> >>>>
> >windows
> >
> >
> >>>>administrator user or a separate windows user?
> >>>>
> >>>>Did you just change the local administrator password on the media
> >>>>
> >>>>
> >server,
> >
> >
> >>>>
> >>>>
> >>>or
> >>>
> >>>
> >>>
> >>>
> >>>>the domain administrator password (assuming the media and sql servers
> >>>>
> >>>>
> >are
> >
> >
> >>>>separate).
> >>>>
> >>>>If they are on the same server, is SQL running successfully?
> >>>>
> >>>>If SQL is running successfully, and either SQL is on the media server,
> >>>>
> >>>>
> >or
> >
> >
> >>>>
> >>>>
> >>>it
> >>>
> >>>
> >>>
> >>>
> >>>>was the domain administrator password that you changed, check if the
SQL
> >>>>Server Agent Service is running, and if not, is it (unlike the SQL
> >>>>
> >>>>
> >Server
> >
> >
> >>>>service) set to run as the administrator? If so you'll need to change
> >>>>
> >>>>
> >the
> >
> >
> >>>>login info for the service.
> >>>>
> >>>>Keith
> >>>>
> >>>>"Darin Duncan" wrote in message
> >>>>news:3eb91678@hronntp01....
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>>I am using Backup Exec ver. 8.6 for on Windows 2000 Server w/ SP3.
> >>>>>
> >>>>>I have been having good backups until last night's. The only thing
> >>>>>
> >>>>>
> >that
> >
> >
> >>>>>
> >>>>>
> >>>>has
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>>changed is that I changed the administrative password. After last
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>night's
> >>>
> >>>
> >>>
> >>>
> >>>>>backup failed, I was able to successfully change the connect as
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>information
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>>for all of my servers. What is got me confused is that under the
"Job
> >>>>>Definitions" tab I can successfully browse to the SQL server and
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>connect.
> >>>
> >>>
> >>>
> >>>
> >>>>>However, when I run the backup job, it errors out with the following
> >>>>>message:
> >>>>>
> >>>>>The SQL server is not responding. DBCC aborted.
> >>>>>
> >>>>>Can someone please tell me what I am doing wrong?
> >>>>>
> >>>>>Thank you,
> >>>>>
> >>>>>--
> >>>>>Darin Duncan, MCSE (NT 4.0)
> >>>>>Dixie Chopper IT Dept.
> >>>>>http://www.dixiechopper.com
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>
> >>>>
> >>>
> >>>
> >>>
> >>>
> >
> >
> >
> >
>

When you installed BEWS, you were asked for an account to run as. If
you have forgotten what it was, you can check from the services applet.
Drill down to any of the BackupExec services and click on properties.

Then logout and login as that account.

Darin Duncan wrote:

>How do you logon as a service account? I have never logged onto the server
>console as any user other than the domain administrator account (this
>includes when I installed).
>
>
>"Ken Putnam" wrote in message
>news:3EBAAF01.2000308@nospam_usa.net...
>
>
>>Rather than logging on to the BEWS server as you, logon as the BEWS
>>service account (what ever user-id you specified at install time). Then
>>just run the BEWS console as normal. any browsing you do now, should
>>have the same effects as when the job runs (unless you have selected
>>"Attach As" for some shares or databases.
>>
>>Darin Duncan wrote:
>>
>>
>>
>>>Please forgive my ignorance, but how do I do that and what do I need to
>>>
>>>
>do
>
>
>>>once I do get that accomplished?
>>>
>>>Darin
>>>
>>>"Ken Putnam" wrote in message
>>>news:3EBAA56F.3080003@nospam_usa.net...
>>>
>>>
>>>
>>>
>>>>Well kinda.
>>>>
>>>>When you are in the BEWS admin program, it runs under the security
>>>>context of the logged in user. When the job runs, it runs under the
>>>>context of the BEWS service account. That's why you see many people
>>>>here on the forum saying that they always logon to BEWS as the service
>>>>account.
>>>>
>>>>Darin Duncan wrote:
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>>The password that I changed was for the Domain Administrator account.
>>>>>
>>>>>The media sever and the SQL server are separate machines. The SQL
>>>>>
>>>>>
>server
>
>
>>>>>agent service is running.
>>>>>
>>>>>The odd thing to me is that in the Job Definition, I can successfully
>>>>>connect to the SQL server and select the databases for backup. The
>>>>>
>>>>>
>>>>>
>>>>>
>>>connect
>>>
>>>
>>>
>>>
>>>>>as criteria for the SQL server itself is the domain administrator
>>>>>
>>>>>
>account
>
>
>>>>>and the criteria for the SQL agent is "sa" user name with no password.
>>>>>
>>>>>It makes no sense to me for it to connect under the job definition but
>>>>>
>>>>>
>>>>>
>>>>>
>>>not
>>>
>>>
>>>
>>>
>>>>>while the job is running.
>>>>>
>>>>>Thanks,
>>>>>
>>>>>Darin
>>>>>
>>>>>
>>>>>"Keith Langmead" wrote in message
>>>>>news:3eba8aa8@hronntp01....
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>How do you connect to the SQL server through BENT? Via an SA user,
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>windows
>>>
>>>
>>>
>>>
>>>>>>administrator user or a separate windows user?
>>>>>>
>>>>>>Did you just change the local administrator password on the media
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>server,
>>>
>>>
>>>
>>>
>>>>>>
>>>>>>
>>>>>or
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>the domain administrator password (assuming the media and sql servers
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>are
>>>
>>>
>>>
>>>
>>>>>>separate).
>>>>>>
>>>>>>If they are on the same server, is SQL running successfully?
>>>>>>
>>>>>>If SQL is running successfully, and either SQL is on the media server,
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>or
>>>
>>>
>>>
>>>
>>>>>>
>>>>>>
>>>>>it
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>was the domain administrator password that you changed, check if the
>>>>>>
>>>>>>
>SQL
>
>
>>>>>>Server Agent Service is running, and if not, is it (unlike the SQL
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>Server
>>>
>>>
>>>
>>>
>>>>>>service) set to run as the administrator? If so you'll need to change
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>the
>>>
>>>
>>>
>>>
>>>>>>login info for the service.
>>>>>>
>>>>>>Keith
>>>>>>
>>>>>>"Darin Duncan" wrote in message
>>>>>>news:3eb91678@hronntp01....
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>>I am using Backup Exec ver. 8.6 for on Windows 2000 Server w/ SP3.
>>>>>>>
>>>>>>>I have been having good backups until last night's. The only thing
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>that
>>>
>>>
>>>
>>>
>>>>>>>
>>>>>>>
>>>>>>has
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>>changed is that I changed the administrative password. After last
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>night's
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>>backup failed, I was able to successfully change the connect as
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>information
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>
>>>>>>>for all of my servers. What is got me confused is that under the
>>>>>>>
>>>>>>>
>"Job
>
>
>>>>>>>Definitions" tab I can successfully browse to the SQL server and
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>connect.
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>>>>>However, when I run the backup job, it errors out with the following
>>>>>>>message:
>>>>>>>
>>>>>>>The SQL server is not responding. DBCC aborted.
>>>>>>>
>>>>>>>Can someone please tell me what I am doing wrong?
>>>>>>>
>>>>>>>Thank you,
>>>>>>>
>>>>>>>--
>>>>>>>Darin Duncan, MCSE (NT 4.0)
>>>>>>>Dixie Chopper IT Dept.
>>>>>>>http://www.dixiechopper.com
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>>
>>>
>>>
>>>
>>>
>
>
>
>

I think that fixed the problem. I'll know for sure tomorrow morning (after
the backup is to run tonight).

Thank you,

Darin

"Ken Putnam" wrote in message
news:3EBAB294.5050701@nospam_usa.net...
> When you installed BEWS, you were asked for an account to run as. If
> you have forgotten what it was, you can check from the services applet.
> Drill down to any of the BackupExec services and click on properties.
>
> Then logout and login as that account.
>
> Darin Duncan wrote:
>
> >How do you logon as a service account? I have never logged onto the
server
> >console as any user other than the domain administrator account (this
> >includes when I installed).
> >
> >
> >"Ken Putnam" wrote in message
> >news:3EBAAF01.2000308@nospam_usa.net...
> >
> >
> >>Rather than logging on to the BEWS server as you, logon as the BEWS
> >>service account (what ever user-id you specified at install time). Then
> >>just run the BEWS console as normal. any browsing you do now, should
> >>have the same effects as when the job runs (unless you have selected
> >>"Attach As" for some shares or databases.
> >>
> >>Darin Duncan wrote:
> >>
> >>
> >>
> >>>Please forgive my ignorance, but how do I do that and what do I need to
> >>>
> >>>
> >do
> >
> >
> >>>once I do get that accomplished?
> >>>
> >>>Darin
> >>>
> >>>"Ken Putnam" wrote in message
> >>>news:3EBAA56F.3080003@nospam_usa.net...
> >>>
> >>>
> >>>
> >>>
> >>>>Well kinda.
> >>>>
> >>>>When you are in the BEWS admin program, it runs under the security
> >>>>context of the logged in user. When the job runs, it runs under the
> >>>>context of the BEWS service account. That's why you see many people
> >>>>here on the forum saying that they always logon to BEWS as the service
> >>>>account.
> >>>>
> >>>>Darin Duncan wrote:
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>
> >>>>>The password that I changed was for the Domain Administrator account.
> >>>>>
> >>>>>The media sever and the SQL server are separate machines. The SQL
> >>>>>
> >>>>>
> >server
> >
> >
> >>>>>agent service is running.
> >>>>>
> >>>>>The odd thing to me is that in the Job Definition, I can successfully
> >>>>>connect to the SQL server and select the databases for backup. The
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>connect
> >>>
> >>>
> >>>
> >>>
> >>>>>as criteria for the SQL server itself is the domain administrator
> >>>>>
> >>>>>
> >account
> >
> >
> >>>>>and the criteria for the SQL agent is "sa" user name with no
password.
> >>>>>
> >>>>>It makes no sense to me for it to connect under the job definition
but
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>not
> >>>
> >>>
> >>>
> >>>
> >>>>>while the job is running.
> >>>>>
> >>>>>Thanks,
> >>>>>
> >>>>>Darin
> >>>>>
> >>>>>
> >>>>>"Keith Langmead" wrote in message
> >>>>>news:3eba8aa8@hronntp01....
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>>How do you connect to the SQL server through BENT? Via an SA user,
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>windows
> >>>
> >>>
> >>>
> >>>
> >>>>>>administrator user or a separate windows user?
> >>>>>>
> >>>>>>Did you just change the local administrator password on the media
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>server,
> >>>
> >>>
> >>>
> >>>
> >>>>>>
> >>>>>>
> >>>>>or
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>>the domain administrator password (assuming the media and sql
servers
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>are
> >>>
> >>>
> >>>
> >>>
> >>>>>>separate).
> >>>>>>
> >>>>>>If they are on the same server, is SQL running successfully?
> >>>>>>
> >>>>>>If SQL is running successfully, and either SQL is on the media
server,
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>or
> >>>
> >>>
> >>>
> >>>
> >>>>>>
> >>>>>>
> >>>>>it
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>>was the domain administrator password that you changed, check if the
> >>>>>>
> >>>>>>
> >SQL
> >
> >
> >>>>>>Server Agent Service is running, and if not, is it (unlike the SQL
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>Server
> >>>
> >>>
> >>>
> >>>
> >>>>>>service) set to run as the administrator? If so you'll need to
change
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>the
> >>>
> >>>
> >>>
> >>>
> >>>>>>login info for the service.
> >>>>>>
> >>>>>>Keith
> >>>>>>
> >>>>>>"Darin Duncan" wrote in
message
> >>>>>>news:3eb91678@hronntp01....
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>>I am using Backup Exec ver. 8.6 for on Windows 2000 Server w/ SP3.
> >>>>>>>
> >>>>>>>I have been having good backups until last night's. The only thing
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>that
> >>>
> >>>
> >>>
> >>>
> >>>>>>>
> >>>>>>>
> >>>>>>has
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>>changed is that I changed the administrative password. After last
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>night's
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>>>backup failed, I was able to successfully change the connect as
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>information
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>>>for all of my servers. What is got me confused is that under the
> >>>>>>>
> >>>>>>>
> >"Job
> >
> >
> >>>>>>>Definitions" tab I can successfully browse to the SQL server and
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>connect.
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>>>However, when I run the backup job, it errors out with the
following
> >>>>>>>message:
> >>>>>>>
> >>>>>>>The SQL server is not responding. DBCC aborted.
> >>>>>>>
> >>>>>>>Can someone please tell me what I am doing wrong?
> >>>>>>>
> >>>>>>>Thank you,
> >>>>>>>
> >>>>>>>--
> >>>>>>>Darin Duncan, MCSE (NT 4.0)
> >>>>>>>Dixie Chopper IT Dept.
> >>>>>>>http://www.dixiechopper.com
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>
> >>>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>>>
> >>>
> >>>
> >>>
> >>>
> >
> >
> >
> >
>