|
Note: In MS SQL there is a
thing called, simply, JOBS. These are scheduled task files that
perform their tasks at scheduled times. Both POSBO and SiteManager
have 'JOBS'. Handling and executing these JOBS is the responsibility
of the SQLServerAgent service that starts when the MSSQLServer
service starts. So if the SQLServerAgent service is not running
the JOBS will not be executed.
Sometimes when setting
up or goofing with SiteManager the JOBS are not setup properly
(or lost). Without MSSQL Enterprise Manager a good way to
check this to look in the root of the system (or C:) drive
and look for the JOB Log files. They are named "KYRUSSiteManager
- n - JobName.job" (n = 1,2,3,4,5 or 6). Jobs 1,2 &
3 should be dated 10:00 PM of the previous evening and jobs
4, 5 & 6 should be dated the current date and within the
last minute or so (they are updated every minute).
If these log files are
not there then there is a good chance that you are not getting
a backup (besides the other functions that JOBS is supposed
to perform).
To set the JOBS back up simply
run this osql command below then log in to SiteManager.
osql -E -dsitemanager -Q"update
networkcommjob set added = 0"
(-E is the same as -Usa -Padmin
except it uses NT trusted connection. So if you are doing
this from another machine and using the -Sservername osql
switch you also need to use the traditional login -Usa -Padmin)
|