Jump to content

Recommended Posts

Posted

We have a package (provided by company, not created by us) that fails to allocate. The error in the event viewer of a failing machine is:

 

Error 1606. Could not access network location WindowsFolder\.

 

Any ideas?

Posted

@Hightower:

 

Not exactly sure but it would seem that it wants to place files into the C:\WINDOWS dir of which it probably has restrictions on. Normally a program would want to place in C:\Program Files which has appropriate permissions to do this.

 

Just a stab in the dark. :) :)

Posted
@Hightower:

 

Not exactly sure but it would seem that it wants to place files into the C:\WINDOWS dir of which it probably has restrictions on. Normally a program would want to place in C:\Program Files which has appropriate permissions to do this.

 

Just a stab in the dark. :) :)

 

Yes, the package does need to put some files in the Windows folder (DLL's/OCX files), but I've never known this to be a problem. Looking through our Q: drive it seems quite a lot of packages install files to C:\WINDOWS and these packages work fine.

Posted

@Hightower:

 

maybe specific reg keys needed to facilitate this?

Have you tried to install manually on clean machine using regmon to capture and assess?

Or even create a package from the MSI and run acl detective?

What app is it anyway? :)

Posted

By the sounds of things you are running a RM CC3 network, as you mention the Q: drive for your packages.

 

Have you tried to install the package manualy? if so does this work?

That would tell you if there is something wrong with the package or with permisions which I doubt as AppAgent runs as SYSTEM, in turn having full system access.

Posted

The software is LJ_PLC_ROBOT_STUDENT. The package contains about 5 MSI's, and an Add.bat file. I wasn't here when it was introduced, but I think the idea is to log on locally and run the Add.bat file. The thing is, it needs installing to about 100 machines and I'll be damned if I'm going to do that.

 

So I created a package of it, trying both the files they gave us, and the files direct from the CD, but it gets the same error when installing (the 1606 one). I've also tried logging on locally to install the package (that I created) and I get the same error. If I try to allocate out their package I get the same error. The only time it properly installs is by running the Add.bat file locally logged on.

 

I've even tried creating a package like this:

 

1) First scan

2) Run add.bat

3) Second scan

 

and I still get the same error :mad:

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...