Only last environment installed on Fat client works

mtrottier

Well Known Member
8.12 tools release 8.96.1.4

Only the last Envronment installed on the fat client can be logged into. Logging into any env other than the last one installed get messages like this in the jde.log:

4496/4872 MAIN_THREAD Tue Jan 29 18:25:58.197000 Jdb_ctl.c3489
Starting OneWorld

4496/4872 MAIN_THREAD Tue Jan 29 18:26:09.947000 Odbc_u1.c901
ODB0000163 - wSQLNumResultCols failure. rc=-1

4496/4872 MAIN_THREAD Tue Jan 29 18:26:09.947001 Odbc_u1.c901
ODB0000164 - STMT:00 [42S02][208] [Microsoft][ODBC SQL Server Driver][SQL Server]Invalid object name 'SPEC_DVF101108.DBO.F98740DVF101108'.

4496/4872 MAIN_THREAD Tue Jan 29 18:26:09.947002 Odbc_u1.c901
ODB0000164 - STMT:01 [42000][8180] [Microsoft][ODBC SQL Server Driver][SQL Server]Statement(s) could not be prepared.

4496/4872 MAIN_THREAD Tue Jan 29 18:26:09.947003 Odbc_u1.c909
ODB0000155 - SQLNumResultsCols failed. Table F98740DVF101108, ODBC DSN EnterpriseOne Local.

4496/4872 MAIN_THREAD Tue Jan 29 18:26:09.947004 Jdbodbc.c3273
ODB0000027 - JDBODBC_DescribeTable failed. Table F98740DVF101108.


If I install the last full PD and then the last PY package I can only login to PY. If I then go back and install the last PD again I can login to PD but cannot login to PY.

I know the problem has to do with the local package spec files in the local MSSQL server but the fact that it works for that last installed environment and no others is confusing.

As I also mentioned it is important to note that each package seems to be OK becuase if it is the last one installed then the environment works witout issues and no messages appear in the JDE.LOG file.

I'm so confused
 
I seem to recall that there were issues with that Tools Release. Is there any way you can go back to 8.96.1.3 or move forward to 8.96.2.x?
 
We have been running this tools release for months.
This issue just started recently.
 
we have same problem on 8.12 TR 8.97.02 only on some workstation .... on mine there isn't this poblem. We are not able to understand why.

Do you solve your problem?
thanks
Gigi
 
I have not found a solution yet.
And yes it only happens on some fat clients.
I even uninstalled all of JDE and the local MSQL and reinstalled but the problem remains.
 
This issue started in 8.96.1.4 and was fixed in 8.96.2.2. What they tried to do is clean up the old .mdf and .ldf files automatically for the path code being installed instead of having them collect and the developers PC eventually run low on disk space and have them delete them manually. Instead of deleting the old files for the path code being installed it deleted all .mdf and .ldf files for ALL path codes on the PC. They basically backed it out in 8.96.2.2, so the issue with old .mdf and .ldf files are back. Oracle gave me a POC for 8.96.1.4 for this issue at the time. You can request one from them or you should be able to restore your setup.exe from your previous tools release.
 
CNCjunior1, your response doesn't seem to match with what gigi wrote because gigi is on 897 and still has the issue. It also wouldn't explain why it is not a problem on every fat client.
 
[ QUOTE ]
8.12 tools release 8.96.1.4

Only the last Envronment installed on the fat client can be logged into.

[/ QUOTE ]

It matches YOUR issue which was the original post, which is what I was responding to, which was the exact same issue we had with 8.96.1.4 also. I haven't tested 8.97 yet so I can't say what Gigi's issue may be.
 
You need to Upgrade your tools release. There was a issue that only allowed=20
the latest package to be accessed.


In a message dated 1/29/2008 7:51:03 P.M. Central Standard Time,
[email protected] writes:

8.12 tools release 8.96.1.4

Only the last Envronment installed on the fat client can be logged into.
Logging into any env other than the last one installed get messages like th is in
the jde.log:

4496/4872 MAIN_THREAD Tue Jan 29 18:25:58.197000 Jdb_ctl.c3489
Starting OneWorld

4496/4872 MAIN_THREAD Tue Jan 29 18:26:09.947000 Odbc_u1.c901
ODB0000163 - wSQLNumResultCols failure. rc=3D-1

4496/4872 MAIN_THREAD Tue Jan 29 18:26:09.947001 Odbc_u1.c901
ODB0000164 - STMT:00 [42S02][208] [Microsoft][ODBC SQL Server Driver][SQL
Server]Invalid object name 'SPEC_DVF101108.DBO.F98740DVF101108'.

4496/4872 MAIN_THREAD Tue Jan 29 18:26:09.947002 Odbc_u1.c901
ODB0000164 - STMT:01 [42000][8180] [Microsoft][ODBC SQL Server Driver][SQL
Server]Statement(s) could not be prepared.

4496/4872 MAIN_THREAD Tue Jan 29 18:26:09.947003 Odbc_u1.c909
ODB0000155 - SQLNumResultsCols failed. Table F98740DVF101108, ODBC DSN
EnterpriseOne Local.

4496/4872 MAIN_THREAD Tue Jan 29 18:26:09.947004 Jdbodbc.c3273
ODB0000027 - JDBODBC_DescribeTable failed. Table F98740DVF101108.


If I install the last full PD and then the last PY package I can only login
to PY. If I then go back and install the last PD again I can login to PD bu t
cannot login to PY.

I know the problem has to do with the local package spec files in the local
MSSQL server but the fact that it works for that last installed environment
and no others is confusing.

As I also mentioned it is important to note that each package seems to be O K
becuase if it is the last one installed then the environment works witout
issues and no messages appear in the JDE.LOG file.

I'm so confused
Mike Trottier Independent CNC Consultant Onsite and Dial-up Support
B731,B732,B733,XE, ERP 8 AS400,Unix,NT Oracle,SQL #801 557-8368
 
Do you have a call number or Solution number that I can use to confirm this with JDE helpdesk?

I don't want to upgrade my tools release unless I know it will resolve the problem or if there is a work around.

According to the post from gigi he is still having a similar issue with tools release 8.12 TR 8.97.02
 
Did you check the spec directories of your other installed path codes after installing a full package to see if the .mdf and .ldf files exist for the other path codes installed? If they do still exist then your issue may be something different from what I, and many other that I've spoken to, have experienced with that release.

The issue that I'm refering to is reported in SAR 8613961. I also recently installed 8.96.2.2, which first included this SAR, and the issue was not present anymore either. If you search JDEList you'll find other posts with people experiencing the same issue after installing releases 8.96.1.4 and after. If you like I can send you the POC that JDE provided me for the 8.96.1.4 release and you can test to see if that resolves your issue or not.
 
I found a work around!

I have been building all my Full Packages to include the OH4A Web Development feature.
I've been using these packages long before the problem started.
I re-install the packages that included the OH4A feature only I clicked "custom" and deselected the web objects. (I re-installed the full builds for DV,PY and PD)
I then installed an update package with just the Web Dev special feature.
I can now access all environments.

It is not perfect and I don't know why it has just started being a problem but it is a work around.
 
I'm sure I've missed something here so bear with me, but isn't this the whole reason for having to use the SnapShot.exe program? We are just coming up on 8.12 and our developers found that situation you describe. But we were told by GSC that with 8.12 we MUST use SnapShot to switch environments on a fat client.
 
Not true. I've got a few clients on your Tools Release (8.96.1.3), and I have no such issue with them. As far as I know, this issue came up with 8.96.1.4, and I've had to skip up to 8.96.2.2 to avoid the issue when I've had to update the Tools Release.
 
Sorry Mike, probably cncjunior1 is right....my collegue after 8.97.02 installation has substituted setup.exe under deployment directory "OneWorld Client Install" with 8.96.1.5 setup.exe due to a bug during installation client. So I have your problem installing 8.97.0.2 client using 8.96.1.5 setup.exe.

I'm apologized for misunderstanding....
Gigi
 
Well, this is all very interesting again!

Do the people that have no problem installing multiple pathcodes on the same Fat Client use the local HTML server?? That's where we had our problems. There is a SolID 200971533 and the JDE E1 TR8.96 HTML Web Server Install manual that tell you NOT to install mult-pathcodes on a Fat Client.

If you don't use the local JAS maybe all works OK?
 
This is an interesting thread!

I'll put in my AUD0.02 worth. We have a couple of fat clients with 3 path codes installed (all in our dev/test system - not production). I'm not sure if there were any "tricks" to doing that as it was about 18 months ago. We also use the fat clients for web development. The trick for that is it only works for one pathcode at a time (to use a different pathcode for web development you need to change the pathcode in an ini file or two).

Over the next week we are setting up some training computers the same way. I'll update this thread with our experience (if I remember).
 
That sounds more and more like the difference between our installations. When I install a client PC, I save the web development piece as a separate install. I install the E1 client first, with all applicable path codes, then put on the web development feature.

I also create batch files to automatically switch INI files for the environment that the user will use.

To test this, we'll need somebody who is having this issue, make sure they don't have the web development feature installing with the full package, then do as described above.

It looks like Mike Trottier has already found that this works for him. Anybody else want to give it a try?
 
I'm not sure if I'll have time tomorrow, I could cut a new VM Dev client fairly easy. I'd like a little more detail about how you "..save the web development piece as a separate install." and then what batch files do you have to switch INI files. And what's the trick inside the INIs?

Cause I think the SnapShot thingy is a real kludge and often causes problems if you don't wait for the beep!
 
The web development piece is a setup file that is run from a place under the "OneWorld Client Install" directory. Look for ThirdParty\WebDevFeature, and you'll see 3 setup files, one for each type of local web client you might be using (WebSphere Express 5, WAS Express 6, or OAS).

Normally, you would build these into your package as a feature, but you don't have to. You could just build a full package or update package as normal, without the web dev feature, deploy the package to the fat client, and you'd have a normal, working fat client. If the PC needed the web dev feature, you could just go to that directory and run the setup file manually.

Once that's done, you always need to look through the JDE.INI, JAS.INI, and JDBJ.INI files to make sure they point to the right environment. At this point, what I do is have several of those INI files around, each configured for a different path code. I create batch files to copy the appropriate INI files to the proper locations, and then launch activeconsole.exe, one batch file for each path code.

It's a bit of work to set up the first time, but after that, you can just make copies of everything for use on other PCs. It's certainly a lot easier than relying on people to use SNAPSHOT properly.
 
Back
Top