There were some copy problems in older versions of Rose that could
cause this type of error. If you can, best bet would be to upgrade
to avoid this type of problem in the future.
Regarding fixing the file, here is a technote that discusses fixing
problem files that might help:
----------------------------------------------------------------------
To fix a problem file:
----------------------------------------------------------------------
1) !MAKE A BACKUP (COPY) OF ANY MODEL FILE YOU MAY BE EDITING FIRST!
2) Open the copy of the corrupted file. The .MDL file is a straight text file
and therefore is readable in any text editor.
3) Locate the line specified in the error message:
(3.1) Syntax errors already identify the line triggering the error:
(3.2) If file freezes or crashes during loading:
(3.2.1) ROSE 4.0 or status bar shows something other 100% loaded:
(3.2.1) ROSE 98 or status bar shows 100% loaded:
4) Known problems:
(4.1) Supplier or client not yet defined.
(4.2) Illegal attachment points:
(4.3) Problem with documentation section.
(4.4) Extraneous characters.
(4.5) decimal point incompatability
5) Restart Rose and go to the diagram including the involved objects.
6) Finalize any changes.
7) If you don't have a clean backup or are having difficulties
----------------------------------------------------------------------
1) !MAKE A BACKUP (COPY) OF ANY MODEL FILE YOU MAY BE EDITING FIRST!
2) Open the copy of the corrupted file. The .MDL file is a straight text file
and therefore is readable in any text editor.
3) Locate the line specified in the error message:
(3.1) Syntax errors already identify the line triggering the error:
Error (<error number>) at file line <line number>
Line <line number> references the line in the .mdl file
EXAMPLE> Error: Error (3439) at file line <1048>.
Error (<error number>)
Does not directly referrence a error in a list.
Rather the number within the parenthesis referrences a mapping file
that is called when parsing the file to do code generation. So what
this means is the error occurred at line 3439 within that file. So
there is no straight forward list of (error number) and what that
error means. The way we decode these errors is to look at that
mapping file and see what routine is being called and then make an
inferrence based upon what is being done, and what might then cause a
failure withing this routine. When there is a straightforward cause,
then the mapping file and Rose will return a more meaningful error,
along the lines as "object does not exists" or whatever.
at file line <line number>
line <line number> references the .mdl file.
In moses cases of these errors, it indicated that there is a problem
with the syntax in the model file itself at that line number.
Check known problem list below:
(3.2) If file freezes or crashes during loading:
(3.2.1) ROSE 4.0 or status bar shows something other 100% loaded:
Notice the load status bar. At what point does it stop?
This will tell us _aproximately_ where the problem line is.
For example:
Rose crashes or freezes when the load status says 48%.
Open the file in an editor. Page down to bottom of file.
How many lines?
If the file was 1000 lines, then the problem is aproximately
at line 480. [total lines * percent] 1000 * .48
NOTE: that this will give apx. location. Sometimes this is
right on, sometimes it may be off by 100 or so lines depending
upon file size.
Determing exact location of problem:
Add some character to the beginning of this line, for example,
"***"
*** (object RoleView "$UNNAMED$3" @4
Save. Now try to open file again in Rose.
If Rose reads this line you should get a error in the log:
11:31:00| Error: Petal syntax error at line 102 near '*'
You can then continue to move this intentional error down
thru the file to find the exact line. As long as you get
the above error, Rose is reading this line. As soon as you no
longer get the error and Rose crashes or freezes, you know
you've gone past the problem line.
(3.2.1) ROSE 98 or status bar shows 100% loaded:
With 4.0 you would almost always get a % loaded message telling
you the point of crash, i.e. 48% loaded.
With 98 it almost always goes to 100% if it crashes during load.
Try going into to model file with editor.
The mdl file is a straight text file, by using dummy markers we
can determine where the crash is, and then usually fix the file.
1) Open .mdl file in a text editor.
2) Determine the length of the file.
3) Add an intentional syntax error 50% of the way.
For example,
mdl file is 16000 lines
start line 8000 with
**error
4) Save.
Keep the model open in the editor so you can repeat the steps.
5) Open model in Rose.
You should get one of two possible results:
There are Errors. See the log for details.
13:46:53| Error: Petal syntax error at line 8000 near '*'
You have not hit the code that is causing the crash.
Move the marker back another 50%, save and repeat test.
Or
Crash.
You have passed the point of the crash.
Move the marker up another 50%, save and repeat test.
Once you have determined the section of code that Rose
is crashing in, check known problem list below:
4) Known problems:
(4.1) Supplier or client not yet defined.
Object in the model file makes reference to another object
not yet defined in the model file.
For example:
(object RoleView "$UNNAMED$3" @4
Parent_View @3
location (58, 274)
quidu "344F950A0334"
client @3
supplier @2
line_style 0)
If you go to "supplier @2" and then search UP towards top
of document you should find @2 previously defined:
(object ClassView "Class" "$UNNAMED$1" @2
If not defined, the file won't open.
This error comes about when deleting/copying/moving things
around. More common in 4.0 than 98. Most cases that causes this in
4.0 where address but they may still be an odd situation or two
where you might run into this in 98. If this problem continues to
repeat itself be sure to contact tech support.
Easiest solution is usually to make note of this object, remove
this section, open up the file in Rose and add it back. This is not
always an option however, as deleting this section can cause other
forward reference problems.
Another option is to move the definition above this point.
For Example,
"**<" markers in the following section of code, show that point
at which a syntax error occurs and point that the crash occurs.
"--->" identifies the actual line causing the crash.
After indentifying the location, check to make sure there are
no undefined references located in this section.
(object AssociationViewNew "includes" @244
location (1852, 1037)
label (object SegLabel @245
Parent_View @244
location (1852, 932)
font (object Font
italics TRUE)
anchor 1
anchor_loc 1
nlines 1
max_width 156
justify 0
label "includes"
pctDist 0.516667
height 106
orientation 0)
stereotype TRUE
line_color 3342489
quidu "36065EB801A3"
**<ERROR roleview_list (list RoleViews
**<CRASH (object RoleView "Parent Component" @246
Parent_View @244
location (845, 650)
label (object SegLabel @247
Parent_View @246
location (1729, 710)
anchor 1
anchor_loc 1
nlines 1
max_width 360
justify 0
label "+Parent Component"
pctDist 0.559820
height 41
orientation 1)
stereotype TRUE
line_color 3342489
quidu "36065EB801A5"
client @244
---> real source of error supplier @248
vertices (list Points
(1852, 1037)
(1852, 750)
(1404, 751))
Searching on @248 up towards top of file finds no matches.
Client and supplier must be previously defined in the file before use.
2 options to clear:
1) Delete this section. This is the quick and dirty way and clears
the problem in most cases.
However if underlying definitions depend upon this item then
more errors may be introduced futher below.
You may be able to delete these other sections,
depending upon number and whether or not they are also referenced.
2) Find definition that is being referenced and move it
immediately above this section.
In above example, @248 was define as the following section.
Moving this directly above " object AssociationViewNew "includes" @244 "
section, clears the problem.
(object ClassView "Class" "Logical View::Domain
Model::Functionality::Functionality" @248
ShowCompartmentStereotypes TRUE
SuppressOperation TRUE
IncludeAttribute TRUE
IncludeOperation TRUE
location (1264, 752)
label (object ItemLabel
Parent_View @248
location (1133, 645)
nlines 1
max_width 262
justify 0
label "Functionality")
icon_style "Label"
line_color 3342489
quidu "35B7AC9E005F"
compartment (object Compartment
Parent_View @248
location (1133, 700)
icon_style "Label"
anchor 2
nlines 2
max_width 212)
width 280
height 236)
NOTE: The crash caused by the forward reference problem has been fixed in
98i,
so I would say loading with 98i (currently in beta) is your best bet for
debugging
these problems if you have access to this beta. Instead of crashing, 98i
gives
you the cryptic error message you've probably seen in the past, but at
least
you will know what line to look at.
(4.2) Illegal attachment points:
(object AssocAttachView "" @1029
client @1023
supplier @985
line_style 1
origin_attachment (-4130, 75)
terminal_attachment (-4040, 75)
anchor 2)
Attachment points cannot be negative.
(4.3) Problem with documentation section.
This problem is only known to occur when files are being transferred
from one location to another (by email or ftp for example). Somewhere
along the line, extra carriage returns are added to the file in the
documentation section.
For example:
CORRECT syntax:
(object Class "x"
quid "3456467103AC"
documentation
|this is the first line of the documentation
|this is the second line of the documentation
|this is the third line of the documentation
))
INCORRECT syntax:
(object Class "x"
quid "3456467103AC"
documentation
|this is the first line of the documentation
|this is the second line of the documentation
|this is the third line of the documentation
))
To correct, delete the blank lines inbetween the '|' lines.
(4.4) Extraneous characters.
This problem usually results from extraneous characters being added
to the beginning or end of the file when transferring the file
from one location to another (such as a text email attachment).
For example:
--PART-BOUNDARY=.2971006439.ZM1000.com
Content-Description: Transferred from mail from [EMAIL PROTECTED]
cc:Mail note part Content-Type: text/plain ; charset=us-ascii
(object Petal
version 40)
... more code ...
value (value Text "")))))
quid "346243370037"))
--PART-BOUNDARY=.2971006439.ZM1000.com--
To Fix:
Remove all extraneous characters before first lines of model file:
(object Petal
version 40)
Remove all extraneious characters after last lines of model file:
value (value Text "")))))
quid "346243370037"))
(4.5) decimal point incompatability
PROBLEM:
Attempting to open file causes following error:
Error: Petal syntax error at line 12 near '0'
Opening up the model file and looking at line 12
12 -> rightMargin 0,000000
leftMargin 0,000000
topMargin 0,000000
bottomMargin 0,000000
pageOverlap 0,000000
I create a new test model and compared:
rightMargin 0.000000
leftMargin 0.250000
topMargin 0.250000
bottomMargin 0.500000
pageOverlap 0.250000
The problem is with the comma,
If you change the "," to a "." here in this .mdl
file then it opens without problems.
ANSWER:
Most likely you are running into a decimal point incompatability.
Rose can only read files that use periods for floating point
numbers, not commas. To fix this, you'll have to manually change
your petal file to use periods instead of commas using a text
editor. You'll only need to do this once, but to prevent it from
happening in the future you need to change the number settings for
English to use period instead of comma for the decimal symbol (in
control panel/regional settings). You *can* continue to use commas
for the decimal symbol, but you have to do it by choosing a
different language in the regional settings.
FOLLOWUP:
I changed rose.ini according to your proposal, but it
didn't work. I checked the different Rose 98 Versions
of my co-workers, all the same number and the same
rose.ini with comma and zero
8054.1 in Help/About
and in rose.ini:
rightMargin 0,000000
leftMargin 0,000000
topMargin 0,000000
bottomMargin 0,000000
pageOverlap 0,00000
Then I had the idea to look at regional settings
under WinNT and checked the decimal symbol, but it
was comma as well on mine as on my co-workers. To
test it I changed it to pt and suddenly I could save
and reload Rose 98 files. After rechanging it to
comma, I could read the Rose 98 pt files, but when
saving them, I couldn't reload them again.
But the magic was that with my co-workers Rose 98
Installation I could save and reopen Rose 98 files,
no matter if decimal symbol was set to pt or comma.
So where is the difference.
The difference is that my co-worker previously
reinstalled WinNT and used the GERMAN version, but I
still have the ENGLISH version installed.
So (I presume most surely) under English WinNT Rose
98 only accepts pt as decimal symbol in Regional
Settings of WinNT, but with the German version of
WinNT it doesn't matter whether it's pt or comma.
So I will have to reinstall WinNT sooner or later,
because German versions of other programs on my PC
work only with comma as decimal symbol correct.
5) Restart Rose and go to the diagram including the involved objects.
6) Finalize any changes.
7) If you don't have a clean backup or are having difficulties in
attempting to fix the file by editing it, please send problem file to
technical support and we will attempt to fix it here.
Also to avoid potentially getting stuck, make sure you create backup
files in Rose. To enable this option in Rose go to,
Tools:Option General Tab, Save
check [] Create Backup Files
or better yet also,
check [] Keep Two Backup Files
(NOTE: for this option (two backups) to work, Create Backup Files
also needs to be checked!)
This option maintains two backup files: the most recent and the
baseline copy:
Backup File (most recent or only): <filename>.md~
Alternate Backup File (least recent): <filename>.md%
For more information on this see Help:
- Names of Temporary & Backup Files
- Create Backup Files
- Keep Two Backup Files
----------------------------------------------------------------------
Patrick Kennedy
Rational Support
On Jul 17, 12:20, Kaerst Grit wrote:
> Subject: (ROSE) strange behaviour in Rose 98
>
> Hi
>
> I have a very strange behaviour in Rose 98.
>
> I have a modell with some categories that are saved in cat-files. I can load
> the model and change something in one category. When I close Rose it crashes
> and when I open the project again I get the errormessage: "Error: Error
> (3623) at file line 4609" and the category is shown empty. I tried the same
> with other categories in the same modell, but I have no crash when I close
> it and I have also not that error message when I open it again.
>
> It seems like that there must be a problem in that special cat-file but I
> have no clue how to find the problem or how to fix it.
>
> Does anyone of you have had similar trouble in the past??? ... The problem
> also happens even if I don't change anything at all but only make a "save"
> on that file and close Rose then ...
>
> Thanks
> Grit
> ************************************************************************
> * Rose Forum is a public venue for ideas and discussions.
> * For technical support, visit http://www.rational.com/support
> *
> * Admin.Subscription Requests: [EMAIL PROTECTED]
> * Archive of messages:
http://www.rational.com/products/rose/usergroups/rose_forum.jtmpl
> * Other Requests: [EMAIL PROTECTED]
> *
> * To unsubscribe from the list, please send email
> *
> * To: [EMAIL PROTECTED]
> * Subject:<BLANK>
> * Body: unsubscribe rose_forum
> *
> *************************************************************************
>-- End of excerpt from Kaerst Grit
************************************************************************
* Rose Forum is a public venue for ideas and discussions.
* For technical support, visit http://www.rational.com/support
*
* Admin.Subscription Requests: [EMAIL PROTECTED]
* Archive of messages:
http://www.rational.com/products/rose/usergroups/rose_forum.jtmpl
* Other Requests: [EMAIL PROTECTED]
*
* To unsubscribe from the list, please send email
*
* To: [EMAIL PROTECTED]
* Subject:<BLANK>
* Body: unsubscribe rose_forum
*
*************************************************************************
