T.R | Title | User | Personal Name | Date | Lines |
---|
3286.1 | same problem .... but ! | BACHUS::ROELANDTS | Wa d'es ma da ve ne stuut | Mon Nov 20 1995 08:51 | 27 |
3286.2 | Should I report this? | CIVPR1::SIMMONS | Mike Simmons (301) 918-5597 | Fri Dec 01 1995 17:46 | 1 |
3286.3 | Is there any fix for this problem??? | CTHU56::L_PELLAND | Luc Pelland. Hull. DTN 640-7218 | Tue Jan 09 1996 10:57 | 10 |
3286.4 | rename UCX$*.DAT files | UTOPIE::FRUEHWIRTH_M | | Tue Jan 16 1996 07:46 | 15 |
3286.5 | Do all the database have to be change? | CTHU56::L_PELLAND | Luc Pelland. Hull. DTN 640-7218 | Mon Jan 22 1996 11:33 | 6 |
3286.6 | SET SERVICE problem - trying to fix | ALEXWS::ARKADY | Arkady Zilberberg, Israel | Mon Mar 25 1996 03:15 | 9 |
3286.7 | Don't see problem going from 3.1 -> 4.1 ECO 3-Why not? | CIVPR1::SIMMONS | Mike Simmons (301) 918-5597 | Wed Jan 29 1997 21:06 | 4 |
| I just upgraded from UCX v3.1 to v4.1 ECO 3 and I did *not* have to re-create
the services as I did going from v3.3 to v4.0. Does skipping v3.3 and/or v4.0
avoid this problem, or is there a fix in v4.1 ECO 3? Note: If I upgrade
3.3->4.0->4.1 (no ECO), I *do* have to re-create all UCX services.
|
3286.8 | solved in V4.1 | BACHUS::ROELANDTS | Wa d'es ma da ve ne stuut | Thu Jan 30 1997 02:55 | 9 |
|
I read somewhere that this was solved in V4.1, so upgrading from UCX
V3.x to V4.1 should not see the error, but due to brain dammage I can't
remember exactly where.
Rgds,
Guy
|
3286.9 | intentionally fixed :-) | UTRTSC::KNOPPERS | Oswald Knoppers | Thu Jan 30 1997 08:41 | 22 |
| I haven seen this in any of the release note for V4.1 and ECO's but it is
mentioned in the release notes of ECO 3 and beyond for UCX V4.0:
Images:
UCX$ACCESS_SHR.EXE UCX V4.0-10C
Problem:
If UCX was upgraded to a newer version then any
UCX SET SERVICE would fail with
"UCX-E-INVRECORD, Invalid information" message.
Solution:
Fixed the incorrect record validity check (reverse condition).
Reference:
CFS.43237
Oswald
|