Jump to content

scheduler & vbscript


Recommended Posts

Posted

I have a vbscript on windows server that launches msaccess vba function of a

db located on another server. Runs fine when manually executed. When run by

scheduler, the script starts but nothing happens w/ the access file. And the

script just sits there open until administartor shuts it down at my request.

 

Any help appreciated.

  • Replies 5
  • Created
  • Last Reply
Guest Pegasus \(MVP\)
Posted

Re: scheduler & vbscript

 

 

"patti" <patti@discussions.microsoft.com> wrote in message

news:1B61D463-1B1C-4537-95A3-0BCB0358633F@microsoft.com...

>I have a vbscript on windows server that launches msaccess vba function of

>a

> db located on another server. Runs fine when manually executed. When run

> by

> scheduler, the script starts but nothing happens w/ the access file. And

> the

> script just sits there open until administartor shuts it down at my

> request.

>

> Any help appreciated.

 

I suspect it's a permission issue. Does the account used for

the scheduled task have sufficient access rights for the

database? Does the database reside on a mapped drive

(which won't exist under the scheduled task) or on a UNC

drive?

Posted

Re: scheduler & vbscript

 

 

Thanks for the help.

 

No permissions involved w/ the database itself.

UNC drive.

 

What other kinds of permissions could come into play? It runs manually but

not under scheduler.

 

 

"Pegasus (MVP)" wrote:

>

> "patti" <patti@discussions.microsoft.com> wrote in message

> news:1B61D463-1B1C-4537-95A3-0BCB0358633F@microsoft.com...

> >I have a vbscript on windows server that launches msaccess vba function of

> >a

> > db located on another server. Runs fine when manually executed. When run

> > by

> > scheduler, the script starts but nothing happens w/ the access file. And

> > the

> > script just sits there open until administartor shuts it down at my

> > request.

> >

> > Any help appreciated.

>

> I suspect it's a permission issue. Does the account used for

> the scheduled task have sufficient access rights for the

> database? Does the database reside on a mapped drive

> (which won't exist under the scheduled task) or on a UNC

> drive?

>

>

>

Guest Richard Mueller [MVP]
Posted

Re: scheduler & vbscript

 

If it runs manually, then it is a permission issue. When you run the script,

your credentials are used. What account is used when you schedule the job?

It needs to be an account with sufficient permissions in the database. Also,

if the UNC path references a share, the account needs permissions to use the

share.

 

--

Richard Mueller

Microsoft MVP Scripting and ADSI

Hilltop Lab - http://www.rlmueller.net

--

 

"patti" <patti@discussions.microsoft.com> wrote in message

news:587033D4-AC9B-436F-9BD5-2250FA05CD53@microsoft.com...

>

> Thanks for the help.

>

> No permissions involved w/ the database itself.

> UNC drive.

>

> What other kinds of permissions could come into play? It runs manually but

> not under scheduler.

>

>

> "Pegasus (MVP)" wrote:

>

>>

>> "patti" <patti@discussions.microsoft.com> wrote in message

>> news:1B61D463-1B1C-4537-95A3-0BCB0358633F@microsoft.com...

>> >I have a vbscript on windows server that launches msaccess vba function

>> >of

>> >a

>> > db located on another server. Runs fine when manually executed. When

>> > run

>> > by

>> > scheduler, the script starts but nothing happens w/ the access file.

>> > And

>> > the

>> > script just sits there open until administartor shuts it down at my

>> > request.

>> >

>> > Any help appreciated.

>>

>> I suspect it's a permission issue. Does the account used for

>> the scheduled task have sufficient access rights for the

>> database? Does the database reside on a mapped drive

>> (which won't exist under the scheduled task) or on a UNC

>> drive?

>>

>>

>>

Posted

Re: scheduler & vbscript

 

Thanks Richard.

 

you say: "It needs to be an account with sufficient permissions in the

database". I'm not clear what you mean. The db is unsecured at this moment -

no user levels, no pw so i don't see how the permissions applies. Is there

something innate w/ access that would bar auto updates & changes?

 

Or is this about permissions on the server where the db resides?

 

 

"Richard Mueller [MVP]" wrote:

> If it runs manually, then it is a permission issue. When you run the script,

> your credentials are used. What account is used when you schedule the job?

> It needs to be an account with sufficient permissions in the database. Also,

> if the UNC path references a share, the account needs permissions to use the

> share.

>

> --

> Richard Mueller

> Microsoft MVP Scripting and ADSI

> Hilltop Lab - http://www.rlmueller.net

> --

>

> "patti" <patti@discussions.microsoft.com> wrote in message

> news:587033D4-AC9B-436F-9BD5-2250FA05CD53@microsoft.com...

> >

> > Thanks for the help.

> >

> > No permissions involved w/ the database itself.

> > UNC drive.

> >

> > What other kinds of permissions could come into play? It runs manually but

> > not under scheduler.

> >

> >

> > "Pegasus (MVP)" wrote:

> >

> >>

> >> "patti" <patti@discussions.microsoft.com> wrote in message

> >> news:1B61D463-1B1C-4537-95A3-0BCB0358633F@microsoft.com...

> >> >I have a vbscript on windows server that launches msaccess vba function

> >> >of

> >> >a

> >> > db located on another server. Runs fine when manually executed. When

> >> > run

> >> > by

> >> > scheduler, the script starts but nothing happens w/ the access file.

> >> > And

> >> > the

> >> > script just sits there open until administartor shuts it down at my

> >> > request.

> >> >

> >> > Any help appreciated.

> >>

> >> I suspect it's a permission issue. Does the account used for

> >> the scheduled task have sufficient access rights for the

> >> database? Does the database reside on a mapped drive

> >> (which won't exist under the scheduled task) or on a UNC

> >> drive?

> >>

> >>

> >>

>

>

>

Posted

RE: scheduler & vbscript

 

 

 

"patti" wrote:

> I have a vbscript on windows server that launches msaccess vba function of a

> db located on another server. Runs fine when manually executed. When run by

> scheduler, the script starts but nothing happens w/ the access file. And the

> script just sits there open until administartor shuts it down at my request.

>

> Any help appreciated.


×
×
  • Create New...