SP17.1 - Deployment Server install - error

KBohn

Active Member
Hello everyone,

We have been trying to perform the SP17.1 Deployment Server install, but
keep getting the following error when it reaches 99%:

Setup failed! The error reported by the operating system is 'The file could
not be accessed'. Please run setup again.

There is nothing reported in the Install log. We have tried several things
including shutting down most Services on the Server except the most basic
required to operate. Has anyone experienced this? Of course, every time we
try to run, we have to get a new Authorization code which is frustrating.

Thanks for your help!
Kimberley Bohn
QNX Software Systems Ltd., Canada
Xe, NT, SQL7.0, SP15
WTS W2K
 
Is the install file for the Service Pack located anywhere under the B7333 folder on the Deployment Server?? If it is, the install will fail. If this is the case, move the file out of the B7333 Folder Structure, and then try to run it, you should be fine then.



Matthew Scott
XE, SP 17.1, AS/400, Win2000 Logic Servers, Win2000 Term. Servers, Win2000 Java Servers, Central Objects in Oracle.
 
Kimberley,

I do not know what causes the problem, but here is a work-around to get
the SP installed:
just open the CD from your Windows explorer, copy the system.cab into
your SYSTEMCOMP diretory, then expand system.cab over your original
system directory.
With that you get the SP installed and do not have to ask for an SPCode.

Hope this helped, Gerd
 
Kimberely,

I had the exact same problem when I installed SP17.1 and Denver was confused about it. The problem turned out to be a file (I believe an INF) that had somehow become read-only. To fix this I went through my backed up directories under B7333 that I created prior to beginning the service pack. Based on modified dates I determined what directories had already been updated and which had not (this was only necessary because my JDE support tech could not tell me what the last directory to get updated was). I then checked all the permissions on the files in that directory and found my one problem file. I'm sorry, I wish I could tell you what directory and what INF file, but I can't remember.

If you find that this is also your problem, would you mind posting what directory and file it was for others?

Thanks, and Good Luck!

Ryan Hunt
OneWorld XE; Update2; SP17.1_B1
AS400; V4R5
DS: Win2k SP2, SQL 7.0 SP3
TSE's: Win2k(SP2) & NT4.0(SP6a) with Metaframe 1.8
 
Hi Matthew,

When I originally downloaded it, it was & then I moved it after I read that
in the instructions. Do you know if it causes this actual error?

Thanks for your help,
Kimberley
 
Hello Ryan,

I'm relieved to hear that it's not just me as JDE said it hasn't been
reported. The JDE consultant had me check the permissions on all the files
in the original System/SystemComp/OneWorld Install folders to ensure that
none are read-only. I've checked it over several times & nothing is read
only. I wish this was the problem because then we could get on with it!!!
Thanks for the info though. Out of curiosity, did you install from CD or
Download? The JDE consultant tried it their lab & it worked fine, but he
was using the CD. I have had problems in the past with download SP's, but
they said it hasn't been reported for SP17.1. The CD is on the way, but
we're still troubleshooting.

Warmest Regards,
Kimberley

Kimberley Bohn
QNX Software Systems Ltd., Canada
Xe, NT, SQL7.0, SP15 (Wanna be SP17.1)
WTS W2K
 
Hi Gerd,

I've never been much of a cowgirl with regards to JDE as it was pounded in
at all the early training sessions not to cowboy around, but this sounds
very nice indeed. If done this way, do you still get the SP information on
the 'About OneWorld' on a client? Any other possible adverse affects? Why
JDE would insist on a software protection code for a SP install is beyond
me.

Thanks alot,
Kimberley

Kimberley Bohn
QNX Software Systems Ltd., Canada
Xe, NT, SQL7.0, SP15
WTS W2K
 
Yes. I encountered this error myself. I too, am a cowboy as you said.

-Matt



Matthew Scott
XE, SP 17.1, AS/400, Win2000 Logic Servers, Win2000 Term. Servers, Win2000 Java Servers, Central Objects in Oracle.
 
Heh-Heh....I'll bet that I will see all of you cowpokes on this same list sometime in the future trying to solve an issue that was self-inflicted because you bypassed JDE's recommended procedure. Here's sincerely hoping that you don't cost your company too much money troubleshooting an issue that is related to cowboying.

Yee-Haw!!


KBohn <[email protected]> wrote: Hi Gerd,

I've never been much of a cowgirl with regards to JDE as it was pounded in
at all the early training sessions not to cowboy around, but this sounds
very nice indeed. If done this way, do you still get the SP information on
the 'About OneWorld' on a client? Any other possible adverse affects? Why
JDE would insist on a software protection code for a SP install is beyond
me.

Thanks alot,
Kimberley

Kimberley Bohn
QNX Software Systems Ltd., Canada
Xe, NT, SQL7.0, SP15
WTS W2K




--------------------------
 
Well, don't worry, I agree with you. I think I'll stick to the recommended
procedures. I checked with JDE about doing this & this was the response:

This is RISKY!! In theory it can be done, but the odds of a problem are
large and we would not be able to support you in fixing it. Just restore
form backup and go by the rules. Besides, they are talking about the CD.

No cowgirling for me!
Kimberley
 
Re: RE: SP17.1 - Deployment Server install - error

Kimberely,

I tried both the download and the CD. Since the problem was a read-only marked file, both were unsuccessful until I fixed the problem.

Good Luck & keep us posted.

Ryan Hunt
OneWorld XE; Update2; SP17.1_B1
AS400; V4R5
DS: Win2k SP2, SQL 7.0 SP3
TSE's: Win2k(SP2) & NT4.0(SP6a) with Metaframe 1.8
 
RE: RE: SP17.1 - Deployment Server install - error

Hi,

I ran the attrib -R /S *.* on the system / systemcomp / oneworld client
install folders to ensure that full permissions would be set on all files.
I just received the CD & tried it with the CD.....same error! DOH!

Thanks,

Kimberley Bohn
QNX Software Systems Ltd., Canada
Xe, NT, SQL7.0, SP10
WTS W2K
 
Hello, Kimberly,
Did you check your privileges on the deployment server? Is there enough
room? Do you belong to the local admin group?
Did you try copy all your CD-disk to the server? Did you get a similar
error? Did you try to install from your hard disk?

Regards, Alex

B7332 SP17, Oracle, Solaris

P.S. I didn't exactly understand what is the OS of the deployment server.
 
Hello Alex,
Yes, privileges are fine & lots of space available. Yes, I've tried running
as Domain Admin which is part of the local admin & I tried as local admin as
well.
I have run from CD & from hard drive, but downloaded, not copied to hard
drive from CD. I could try that next.
Thanks for the suggestions & help!
Regards,
Kimberley
 
I have also seen this a few times before. How JDE could muck up a "setup.exe" script is beyond me. However, I have found that by going INTO the .CAB and copying the files over manually this often fixes the issue. I am sure that JDE would not like to support this (show me something they WOULD like to support) - but we have never had issues applying service packs when something like this occurs.

However, I would always recommend trying to refresh the deployment server to ensure that this bug disappears whenever the customer has time to bring the deployment server down.

Jon Steel
erpSOURCING LLC

ERP Sourcing
http://www.erpsourcing.com
[email protected]
 
AW: SP17.1 - Deployment Server install - error

Hi Kimberley,

this issue looks like the same which I have had. I was able to install
the SP17.1 from CD to the Deployment Server, but when I build an update
Package I got the WinError message, access denied for SYSCOMP. But I
have enough rights on this folder, also the JDE User is an Admin.
So I created this Folder by myself and all things are o.k. right now

Hope this helps

Regards

OneWorld Xe
SP17.1
Oracle 8.1.7.1
Windows2000Advanced Server




-----Ursprüngliche Nachricht-----
Von: KBohn [mailto:[email protected]]
Gesendet: Donnerstag, 17. Januar 2002 15:49
An: Bernd Schade
Betreff: SP17.1 - Deployment Server install - error

Hello everyone,

We have been trying to perform the SP17.1 Deployment Server install, but
keep getting the following error when it reaches 99%:

Setup failed! The error reported by the operating system is 'The file
could
not be accessed'. Please run setup again.

There is nothing reported in the Install log. We have tried several
things
including shutting down most Services on the Server except the most
basic
required to operate. Has anyone experienced this? Of course, every
time we
try to run, we have to get a new Authorization code which is
frustrating.

Thanks for your help!
Kimberley Bohn
QNX Software Systems Ltd., Canada
Xe, NT, SQL7.0, SP15
WTS W2K








--------------------------
 
So did this problem ever get resolved? I'm trying to apply SP20 and get the same error message, and would appreciate any assistance. I, too, have logged a call with JDE, but it doesn't sound like they've been a lot of help yet to others.
 
Just thought I'd update you with what I found out. In downloading from the Knowledge Garden, you end up with two executables -- one for the server and one for the client. The one for the server is run ONLY to get the system.Z file (at least in the case of the HP9000). So when it tries to run the setup.exe, you can cancel out. Then you run the client's executable, which will in turn run its own setup.exe, and this will update your deployment server's system, SYSTEMCOMP, and OneWorld Client Install directories.
 

Similar threads

E9.2 Change Assistant Error for UDOs
Replies
8
Views
650
Seane6
N/A Error when ESU deployment setup
Replies
0
Views
1K
syddflyd
tiradoj
E9.2 The Chaos That is Web Deployment in 9.2.7.1 using P96470W
Replies
11
Views
3K
harshteki
Soumen
E9.2 JDE Slowness - fixed by DB Reboot
Replies
17
Views
3K
Soumen
Soumen
E9.2 DEMO Installation : Facing issue while while connecting to E1 Local
Replies
1
Views
2K
Rauf
Rauf
Back
Top