Model Reader Load Errors
Posted: Fri May 16, 2014 2:27 pm
Just looking for advice here, but was curious if anyone has ideas on what can cause the model reader to fail to load a model. (Assuming the path, model name and type are all correct)
Long story short, I've built a model for Syndromic Surveillance that uses excel as a dashboard/post processing application. Everything works fine on the development front (I.E., on machines that have VENSIM DSS installed) but I have run into issue distributing this to users who only have the model reader installed.
I've followed the instructions for creating a .VPA of the model that uses a .bat file to call the excel file. (this is necessary because the users want to be able to save their changes in the excel file rather than having the VPA overwrite the excel file every time its used) For the most part this works, but I've encountered intermittent failure to Load model errors, that I can't figure out the cause of.
Here are a couple of examples.
1) Model runs fine the first time, but then any subsequent runs the user gets the Load Model Error. If the user restarts the model reader, reloads the VPA they can then run the model again. But again after the first time they are unable to run it again.
2) Model runs fine on one computer but utilized on another computer (Using the same version of the Model reader) the model reader won't load the model. (Path and model name all correct)
3) This was a really weird one. At one point on a test machine neither a VPA (Like the one I described above), a VPA (With the excel sheet embedded so that it was overwritten each time) or even just a plain VPM would load into the model reader. I eventually shut the machine down and came back to it later, and suddenly everything was working again.
Overall I've been able to help users get the model going, but it's basically through a lot of flaying and blind luck. I would like to have a more structured process for addressing Model Reader load issues or ideally eliminate them altogether. However, given the seemingly infrequency at which they arrive I'm struggling to come up with an approach.
Has anybody experienced similar issues? How did you overcome them or what is the process you use? Is there something that can happen either before, during or after a model run that could cause the Model Reader to no longer accept the loading of a model through the .dll calls? Could an error in the excel file, not directly tied to the .dlls calls to the model, cause the model reader to no longer load a model?
Any help, advice or direction would be greatly appreciated.
Thanks.
-Chip
Long story short, I've built a model for Syndromic Surveillance that uses excel as a dashboard/post processing application. Everything works fine on the development front (I.E., on machines that have VENSIM DSS installed) but I have run into issue distributing this to users who only have the model reader installed.
I've followed the instructions for creating a .VPA of the model that uses a .bat file to call the excel file. (this is necessary because the users want to be able to save their changes in the excel file rather than having the VPA overwrite the excel file every time its used) For the most part this works, but I've encountered intermittent failure to Load model errors, that I can't figure out the cause of.
Here are a couple of examples.
1) Model runs fine the first time, but then any subsequent runs the user gets the Load Model Error. If the user restarts the model reader, reloads the VPA they can then run the model again. But again after the first time they are unable to run it again.
2) Model runs fine on one computer but utilized on another computer (Using the same version of the Model reader) the model reader won't load the model. (Path and model name all correct)
3) This was a really weird one. At one point on a test machine neither a VPA (Like the one I described above), a VPA (With the excel sheet embedded so that it was overwritten each time) or even just a plain VPM would load into the model reader. I eventually shut the machine down and came back to it later, and suddenly everything was working again.
Overall I've been able to help users get the model going, but it's basically through a lot of flaying and blind luck. I would like to have a more structured process for addressing Model Reader load issues or ideally eliminate them altogether. However, given the seemingly infrequency at which they arrive I'm struggling to come up with an approach.
Has anybody experienced similar issues? How did you overcome them or what is the process you use? Is there something that can happen either before, during or after a model run that could cause the Model Reader to no longer accept the loading of a model through the .dll calls? Could an error in the excel file, not directly tied to the .dlls calls to the model, cause the model reader to no longer load a model?
Any help, advice or direction would be greatly appreciated.
Thanks.
-Chip