Not a Problem

Error saving and loading files

I have downloaded BizAgi and it works wonderfully. I copied the downloaded executable to USB and gave to two of my managers. They installed the program and registered and can now open the program. They have a few problems though. First, neither person can save a file they create. When they try to save the file, they get the following error.

"Error saving Model:

There was an error reflecting type 'BizAgi.PM.BusinessEntities.XPDL22.PackageType'."

I've attached a screen shot of above.

The second problem is that they are unable to open files I have sent them. When they try to open the file, they get the following error.

"Error loading Model:

Exception oftype 'BizAgi.PM.BusinessEntities.Exceptions.EmptyDocumentException' was thrown."

I've attached a screen shot of above.

We get the same two errors on two different computers. Everything works perfectly on my computer. Your assistance getting you program working is much appreciated. We're just now in the evaluation phase and looking to implement work flow. BizAgi Modeler is VERY easy to use and I love the documentation creation, but it seems pretty buggy as it would not install when I downloaded (I had to copy downloaded file to USB and then install from USB to get installer to work). Also, these problems my Managers are having are a bit concerning. Hopefully we can work this out as I'm extremely impressed with usability.

PS - I tried exporting a model that we couldn't save and it exported to Word and to HTML just fine. Could save it, but could create documentation.

Best Answer
photo

Dear Jeff,

Thank you for your interest in Bizagi and sent feedback.

Regarding these 2 issues you are facing, they are both solved by ensuring that Microsoft .Net Framework 2.0 service pack 2 is installed in these machines.

View further links and related information about this framework 2.0 service pack 2 and your reported issue.

Best regards,

photo
0

Dear Jeff,

Thank you for your interest in Bizagi and sent feedback.

Regarding these 2 issues you are facing, they are both solved by ensuring that Microsoft .Net Framework 2.0 service pack 2 is installed in these machines.

View further links and related information about this framework 2.0 service pack 2 and your reported issue.

Best regards,