| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 3087.1 | | METSYS::THOMPSON | | Fri Apr 04 1997 18:53 | 6 |
| Martin,
this was a common problem in the pre V3.1 days. Are you sure the customer
really has V3.1A?
M
|
| 3087.2 | I'll check | UTRTSC::SMEETS | Workgroup support | Mon Apr 07 1997 08:56 | 15 |
| Hi Mark,
Yes, I've seen that this was a common problem in V3.1.
About 1� month ago the customer performed an upgrade from V3.1 -> V3.1A
both on the server and the client.
I could be that the upgrade at the client site didn't removed/replaced all old
images.
Anyway I'll try to check if it is really V3.1A.
Regards,
Martin
|
| 3087.3 | It looks like it is V3.1A | UTRTSC::SMEETS | Workgroup support | Mon Apr 07 1997 12:08 | 11 |
| Hi Mark,
Help About in the Cockpit shows the following data:
V3.1A Nov 19 1996
All of the Windows V3.11 users encounter this problem.
Regards,
Martin
|
| 3087.4 | | MARVIN::GOODWIN | Pete Goodwin | Mon Apr 07 1997 14:43 | 5 |
| That's the Cockpit, try looking at the EDIOBDDE.EXE image (or
EDIOBB32.EXE for 95/NT). Check the date of the file. I can't remember
if the Help menu has About which might show the version.
Pete.
|
| 3087.5 | Sizes and dates | UTRTSC::SMEETS | Workgroup support | Wed Apr 09 1997 14:25 | 16 |
| Hi Pete,
Here's the requested information obtained by pressing ALT-ENTER in the File
Manager
EDIOBDDE.EXE 123,120 02-10-96 V3.1A
EDIOBB.DLL 25,968 02-10-96 No version information
The customer also encountered GPF in conjunction with EDIMAP.EXE
EDIMAP.EXE 498,928 10-12-96 V3.1A
Regards,
Martin
|
| 3087.6 | | MARVIN::GOODWIN | Pete Goodwin | Wed Apr 09 1997 18:30 | 5 |
| It looks like V3.1A ok. I thought all the problems with GPF's in
EDIOBDDE had been fixed, maybe not. I'd suggest you log an IPMT on both
GPF's.
Pete.
|
| 3087.7 | More info needed | METSYS::POAD | http://www.digital.com/info/edi | Thu Apr 10 1997 16:17 | 39 |
| Hi Martin,
I have a WFWG V3.11 PC with CommandCenter V3.1A working OK here. Can
you provide some more info:
1) What type of database is on the Server?
2) What version of DEC/EDI is the Server?
3) What ODBC driver and version do you have on the PC?
4) What version of ObjectBroker do you have on the PC and the Server?
5) Does the Network tester work
6) Do you have the CommandCenter patch that replaces the complete kit
from our web site?
7) Does this problem happen everytime after you enter the password, or
do things sometimes work ok?
8) What was the customer doing when the GPF in the Mapping Table
Editor occured?
9) Was CommandCenter V3.1 working OK?
10) Was anything else upgraded on either the PC or Server when
CommandCenter V3.1A was installed?
11) Do the other Editors work OK?
The only thing I can think of suggesting at present is that you
uninstall the CommandCenter completely. I.e. Uninstal it, and then
rename the C:\EDICC directory, if it still exists (so as to pretend to
delete it without losing any files in it you may want). Then install
the patch kit for V3.1A. This would clear up any descrepencies with the
old V3.1 kit.
Chris
|
| 3087.8 | The answers to your question | UTRTSC::SMEETS | Workgroup support | Fri Apr 11 1997 09:08 | 54 |
| Hi Chris,
> 1) What type of database is on the Server?
Oracle Rdb
> 2) What version of DEC/EDI is the Server?
V3.1A
> 3) What ODBC driver and version do you have on the PC?
ODBC driver for Oracle Rdb V2.0...
> 4) What version of ObjectBroker do you have on the PC and the Server?
V2.6-07
> 5) Does the Network tester work
Yes
> 6) Do you have the CommandCenter patch that replaces the complete kit
> from our web site?
I'm not sure if the customer has this kit. A collegue of mine sent the
kit to the customer. How can we determine if this is the patch kit ?
> 7) Does this problem happen everytime after you enter the password, or
> do things sometimes work ok?
No, it doesn't happen all the time.
> 8) What was the customer doing when the GPF in the Mapping Table
> Editor occured?
I've to ask the customer.
> 9) Was CommandCenter V3.1 working OK?
No, also in that version GPF's occur.
> 10) Was anything else upgraded on either the PC or Server when
> CommandCenter V3.1A was installed?
No
> 11) Do the other Editors work OK?
Yes.
> The only thing I can think of suggesting at present is that you
> uninstall the CommandCenter completely. I.e. Uninstal it, and then
> rename the C:\EDICC directory, if it still exists (so as to pretend to
> delete it without losing any files in it you may want). Then install
> the patch kit for V3.1A. This would clear up any descrepencies with the
> old V3.1 kit.
Ok, I'll do this....
Regards,
Martin
|
| 3087.9 | Files copied to customer | UTRTSC::SMEETS | Workgroup support | Fri Apr 11 1997 15:47 | 12 |
| Hi Chris,
I've copied the following files to the customer.
cc16pat1.exe
monitor.exe
edimap.exe
ediprof.exe
Regards,
Martin
|