Hi Luis;
Yes & No ....
Yes .. but, you will need to make sure that the App deployment names are unique. For example OrderEntry1, OrderEntry2, etc.
No... if the App deployment names are the same, then the 2nd, third, etc App with the same name will not deploy as it sees the name there already as "deployed.
Multiple Instance App crashes ....
No... as long as instance #1 vs #2, #3, etc do not use any common resources - then they should run OK as Armeen mentioned.
Yes... If multiple instances use the same external file(s) especially for write access, then a conflict will occur and this could easily lead to an App crash (ie: using a "Control" file for example). I just tested this with my STD framework's OrderEntry PB App deployed as both a 32bit and 64bit PowerClient App. For two 32bit apps, the 2nd instance crashes, for two 64bit app instances the 2nd instance crashes, for one 32bit App instance & one 64bit app instance they run OK (separate deployment names). The reason that the 2nd instance of either bitness crashes is because the STD framework opens for write an App log. The 2nd instance then gets locked out of the log file. In order for this to work, I would have to allocate a unique log file instance per App instance in order to avoid this collision.
Note: the same considerations would be for multiple PowerServer App instances as well. As long as there are no resource clashes between instances, then multiple instances of any App should work OK.
PS: I had to override the STD framework behaviour in order to test the above as the framework always stops the 2nd instance from starting using the O/S Mutex feature and then informs the app user that the App is already running. This feature works not only for 2 32bit & 2 64bit Apps but one 32 and one 64bit App instance as well.
So in conclusion, it could be because your PC App is using a resource that the 2nd instance is then being locked out from. Food for thought.
Regards ... Chris