cancel
Showing results for 
Search instead for 
Did you mean: 

B.Exec 2012 clean install...can't run a job

JustTryinToGetI
Level 6

We have B.Exec 2012 installed on our network.

I decided to test SDR, so I installed it on a Windows 2008 R2 stand-alone server  [2012 - Version 14 Rev 1798 (64-bit) ].  My storage device is a USB external. I started a Full backup of the media server. And it wrote about 12 GB to the BEData folder. As it was still a job in process, I was looking at some config settings and the prog file hung. Regrettably, I had to hard boot the server.

Here is my question

I re-run the same job and it stays in queued status. I cancel job.

I delete the job and create a new Full and that job stays in queued status. I cancel job.

I stop/start all services and  job stays in a queued status. I cancel job.

I reboot and create a tiny job to back-up and job stays in queued status.

 

Any ideas to get past this so I can start testing SDR?

1 ACCEPTED SOLUTION

Accepted Solutions

pkh
Moderator
Moderator
   VIP    Certified
You should check your USB connection which is prone to being bad

View solution in original post

5 REPLIES 5

CraigV
Moderator
Moderator
Partner    VIP    Accredited

Check to see if there aren't any pending alerts and respond to them...

VJware
Level 6
Employee Accredited Certified

Restart all BE services including the SQL instance. Check the event viewer for any related errors/warnings.

JustTryinToGetI
Level 6

There were no pending alerts.

Today I decided to run the tiny 1MB file again. It queued for about 2 hrs and then it started and completed. Weird. So I launched the Full backup and the job started after a very short initial status of "queuing".  Interestingly, the job rate is between 50-150MB/min. at present and ot yet complete.

On the job that failed, the ADAMM log had couple entries that said:

           The driver detected a controller error on \Device\Harddisk2\DR2

               - Slow the SCSI bus

               - Verify that the latest SCSI drivers and firmware are loaded.

The Server (Server 2008 is simply loaded on a desktop type box) has 2 internal SATA drives connected to the motherboard directly. There is not a S/W RAID nor H/W RAID configured.

I will load updated BIOS once job completes.

 

Question(s)

Any thoughts as to why the ADAMM log would log an error that to me appaers to be invalid?

Any thoughts why job rate would drop to a crawl? (I have reviewed TECHNote 49521. That stuff doesn't apply since I am backing up to USB drive. Although, I guess I cld do a B2D)

 

 

CraigV
Moderator
Moderator
Partner    VIP    Accredited

...did you verify that there are actually no issues with the HDD?

pkh
Moderator
Moderator
   VIP    Certified
You should check your USB connection which is prone to being bad