Closed GoogleCodeExporter closed 8 years ago
This is a very critical issue!
Original comment by martin.f...@blum.com
on 7 Feb 2012 at 6:46
Hello Sirs, unofficial fix can be found from
http://www.4shared.com/folder/kSaXFXcu/MxUpdate_Tool__unofficial_fix_.html.
Packages (for MxUpdate Eclipse Plugin, Update Deployment Tool and related
JavaDocs) are containing all latest from MxUpdate Tools (up to revision 854) +
changed Policy_mxJPO.java and Rule_mxJPO.java for mxupdate.V0.10.0-install.zip.
This has been tested only with V6R2012x, may not work with lower versions.
Sorry that there are needs to login to www.4shared.com to get these.
Hopefully Owner of the project will get some free time to fix this using
official way that supports not only older version or not only newer versions.
Original comment by mx.syste...@gmail.com
on 9 May 2012 at 4:25
I have tested the fix with V6R2013 and could export policy and rules now. Thank
you. However, there are still some unknown tags. Especially the the unknown
tags below the "userAccessList" make me worry. As an example I took the
"Development Part" policy from a V6R2013 ootb system:
WARNING! Url '/policy/delimiter' unknown and not parsed!
WARNING! Url '/policy/enforceLocking' unknown and not parsed!
WARNING! Url '/policy/majorsequence' unknown and not parsed!
WARNING! Url '/policy/stateDefList/stateDef/majorrevisionable' unknown and not
parsed!
WARNING! Url '/policy/stateDefList/stateDef/published' unknown and not parsed!
WARNING! Url
'/policy/stateDefList/stateDef/userAccessList/userAccess/matchOrganization'
with value 'single' unknown and not parsed!
WARNING! Url
'/policy/stateDefList/stateDef/userAccessList/userAccess/matchProject' with
value 'single' unknown and not parsed!
WARNING! Url
'/policy/stateDefList/stateDef/userAccessList/userAccess/userAccessLoginRole'
unknown and not parsed!
Original comment by Jens.Sch...@de.soliver.com
on 10 May 2012 at 7:45
Sorry Jens, personally I am not having access to any V6R2013 applications.
But do agree with you, those warnings are something that should be also
corrected if using really version V6R2013.
Hopefully Owner of the project would get time to look these.
Original comment by mx.syste...@gmail.com
on 10 May 2012 at 8:57
Hi,
can anyone please help me in the below case;
I am using MatrixOne 10.7 (Old) version.
We do face the same issue
#2 Error #1900068 eval expression failed
#1 System Error #1600000 "\1071010\src\cmd\expression.C":554
#0 Error #1600035 Expected name
I could find this in mxtrace.txt file whenever the crash happens.
The scenario is,
When User is trying to access the particular Folder in the application, the
service is getting crashed
User has added to 33 Projects and has added to 360 Folders
Can anyone please help me in this case?
If you need ny more details please let me know
Thanks,
Sayee
Original comment by sayeeviv...@gmail.com
on 11 Jul 2012 at 1:54
Hello Sayee,
sorry to hear that you are having challenges with your application.
But from problem description I understood that you are talking about usage of
application, not schema management - please correct me if I understood your
challenge wrongly.
But in case that I understood correctly - please be known that MxUpdate is
deployment tool and you should get support to your current challenges from
somewhere else.
Would like to propose that you contact to your support/development team first -
as if you contact to software vendor, they may/will ask if you first update
your core to latest.
Anyway - it may be that you are having some illegal or special characters there
in your data that is causing above challenges.
Sorry.
Original comment by yrtti...@gmail.com
on 12 Jul 2012 at 5:58
Please find updated java files:
/org/mxupdate/update/datamodel/Policy_mxJPO.java
/org/mxupdate/update/datamodel/Rule_mxJPO.java
Also remember that these are tested only using V6R2012x.
Original comment by mx.syste...@gmail.com
on 12 Nov 2012 at 6:05
Attachments:
[deleted comment]
Fixed in Revision 855
Original comment by flat...@googlemail.com
on 21 Dec 2012 at 1:44
Original comment by tim.mox...@innobix.com
on 24 Sep 2013 at 9:25
The issue is included in issues #164, #177 and #178.
Original comment by tim.mox...@innobix.com
on 25 Sep 2013 at 9:25
The issue is included in issue #164, issue #177 and issue #178.
Original comment by tim.mox...@innobix.com
on 25 Sep 2013 at 9:26
Original comment by tim.mox...@innobix.com
on 25 Sep 2013 at 9:27
Original comment by tim.mox...@innobix.com
on 7 Feb 2014 at 8:31
Original issue reported on code.google.com by
martin.f...@blum.com
on 7 Feb 2012 at 6:44Attachments: