Sorry I was away. I posted this description on ms newsgroup. Only response was to verify winnt/system32/sqlsrv32.dll was set in registry correctly and it it.
***************
I created my publication and then I see a new JOB in the Management/SQL
Server Agent/Jobs which is a snapshot job and it is ATCMaster-ATCMaster-18.
Then I push a subscription and then there is the other new job in the
agent/jobs which is a distribution job and it is atcmater-inhousewebtest-92.
(of course this number increases on each new attempt!<g>)
Then I have an app where I am using sqldmo
I create my dmo object, then my connetion to the database and then a job
(the snapshot 18) and then I try to start the job.
This is the right process right. First run the snapshot job then the
distribution. I have writen a similar program without sqldmo. Instead I used
snapshot.exe and then create a distribution object.
So back to this application!
Here is the code
******
Dim server As New SQLDMO.SQLServer()
server.Connect("brewster")
Dim myjob As SQLDMO.Job =
server.JobServer.Jobs.Item("BREWSTER-ATCMaster-ATCMaster-18")
myjob.Start()
*******
Simple, right?
It steps right through to myjob.start and then crashes when I try to start
with this message:
[Microsoft][ODBC SQL Server Driver][SQL Server]SQLServerAgent Error: Request
to run job BREWSTER-ATCMaster-ATCMaster-18 (from User NT AUTHORITY\SYSTEM)
refused because the job has been suspended.
This leads me to look at Enterprise Mgr where I can see the evil red X next
to the snapshot and it says Runnable=NO(the job is supended)
Status-Suspended
After this happend the first few times, that is when I started just fiddling
in Ent Mgr and deletin ghte subscription and the publication, recreating and
watching that snapshot go right to suspended status.
boo hoo <g>
Any ideas?
My goal is to write a web app that will run the replication for me so that I
can let IIS handle the security and not have to open up permissions to users
for doing the replication. Currently I have an app role on this database so
I am the only person who can run my original replication application which
is a vb5 app that worked beautifully until I locked down the server. I have
tried to get around this problem for months and this is my new theory to
test, yet I keep getting stuck with this suspend!
Thanks very much.