On Fri, 12 Dec 1997, Nicholas, Murray, Haltek/AU wrote:
> Julie,
>
> Have you checked that your installation user has the necessary file
> access permissions to all levels of the directory? Same question
> regarding the user trying to run the ADSM clients.
Thanks Murray, actually I did. I was logged on with Administrator access
and checked each directory level's security info. Each one had Full
Control for the Adminstrators. I found this info by choosing the
Properties of each directory, selecting the Security tab and then
Permissions. I'm assuming this is where the proper permission info is,
please correct me if I'm wrong or missed something.
Thanks Again,
Julie
>
> Murray Nicholas
> IT Systems Consultant
> Galeforce Information Services Pty Ltd
> ----------
> From: Julianna Walter[SMTP:Julie.Walter AT UALBERTA DOT CA]
> Sent: Friday, 12 December 1997 8:14
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: NT SQL Connect Agent
>
> I'm stumped and hoping someone can help me out here.
>
> I had ADSM running fine on a winnt35 machine acting as a server. The
> name
> of the machine changed, moved locations to another building and is
> being
> accessed through Timbukto.
> Once all these changes were made of course things stopped working.
> I changed the nodename on ADSM, that's fine.
> I did all the usual starting and stopping of the Services tricks,
> didn't
> work, infact the Services installation finds the
> c:\win32app\ibm\adsm\baclient path but once I select "Y" to say that
> it is
> the correct destination it says "The system cannot find the path
> specified".
> I thought maybe things got wacky with all the moves and decided to
> start
> from scratch. Removed everything and downloaded the client again.
> When I
> tried to do the installation, wierd thing #1: When it went to extract,
> it
> could not find the adsminst.zip file that uncompresses all the files.
> This
> file usually resides in the C:\TEMP directory, hence ADSM would not
> install...instead I did a search and found it in the
> C:\Winnt35\Tempex.dir
> directory??? I moved the file into the C:\temp directory and
> everything
> extracted and installed. Wierd thing #2:
> I proceeded to see if I could get a connection to the ADSM
> server, works fine with the new name. However, the Schedule Service
> Installation is still having the same problem, it can't access the
> c:\winn32app\ibm\adsm\baclient directory. I tried installing it into
> different directories, and running it again, it picks up the change
> right
> away but as soon as I go to confirm it's the proper directory it
> still
> comes back and says it cannot find the path specified. How can this
> be
> when it just told me it found the correct path and all I'm doing is
> agreeing with it? I even tried responding NO and typing it in, still
> to no
> avail. Why can it not access this path?
>
> Someone please enlighten me, I've done all the creative thinking I can
> do.
> Could it be because I'm doing this over Timbukto? Other software has
> been
> installed through it.
>
> Thank You Ever So Much,
> Julie
>
>
> ***********************************************************************
> ***
> Julie Walter Phone: 492-9338 Fax:
> 492-1729
> Help Desk Analyst E-Mail:
> Julie.Walter AT ualberta DOT ca
> Computing and Network Services
> Rm 302 General Services Building
> University of Alberta
> Edmonton, Alberta. CA
> T6G 2H1
>
**************************************************************************
Julie Walter Phone: 492-9338 Fax: 492-1729
Help Desk Analyst E-Mail: Julie.Walter AT ualberta DOT ca
Computing and Network Services
Rm 302 General Services Building
University of Alberta
Edmonton, Alberta. CA
T6G 2H1
|
