question

michel.torbey avatar image
0 Likes"
michel.torbey asked michel.torbey commented

Flexscript error messages Flexsim 2017 Update1

When I open my model, I get these two messages:

exception: FlexScript exception: VIEW:/nodefunctions/workspace/openworkspace
CreateFile failed with error code 22 while trying to connect to the registration pipe.	

I couldn't find any questions on the forum that are related to these two messages.

My software is up to date.

Is there any solution?

Best regards,

Michel

FlexSim 17.1.0
error messages
· 7
5 |100000

Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.

Abel van der Windt avatar image Abel van der Windt commented ·

I have the same problem when opening FlexSim 2017 Update 1. However, I only get the second message:

CreateFile failed with error code 22 while trying to connect to the registration pipe.

As @michel.torbey already asked: What could cause this error and how to fix it?

Cheers,

Abel

0 Likes 0 ·
Ben Wilson avatar image Ben Wilson ♦♦ commented ·

@michel.torbey, Do you get your error message only when opening your model, or do you get it when you open FlexSim itself (without opening a model)?

@Abel van der Windt, you mention getting the error message upon starting FlexSim, correct? Not when opening a model?

0 Likes 0 ·
Abel van der Windt avatar image Abel van der Windt Ben Wilson ♦♦ commented ·

@Ben Wilson Yes, you're right. If I open a model, then I get the error message.

0 Likes 0 ·
Ben Wilson avatar image Ben Wilson ♦♦ Abel van der Windt commented ·

@Abel van der Windt, thanks for the additional info. Do you see the errors with any model file, or just a specific model?

If it is just a specific model, can you post your model to this question? Or if not to this public question, could it be posted to a private question?

Also, if you have time to test some of the solutions I linked to in my answer below, I would love to hear if any of them helped.

0 Likes 0 ·
Steven Hamoen avatar image Steven Hamoen commented ·

@Ben Wilson Hi Ben, I now have almost the same error only the error code is different:

CreateFile failed with error code 00 while trying to connect to the registration pipe.

I'm already running the windows 10 creator update and have updated the graphics driver. I have also removed the prefs.t file but when I open the model it shows this message just after the dwg becomes visible. (that might be coincidence btw ) Shall I wait for 2017.1.1 or send you the model?

0 Likes 0 ·
Ben Wilson avatar image Ben Wilson ♦♦ Steven Hamoen commented ·

@steven.hamoen,

17.1.1 will be out later today, so let's try that first. Let us know if it clears up the errors. If not, and your model can be public, then go ahead and post it back, or attach it to a new private question.

Thanks!

0 Likes 0 ·
Steven Hamoen avatar image Steven Hamoen Ben Wilson ♦♦ commented ·

@Ben Wilson Seems the update fixed the problem!!. Thanks

0 Likes 0 ·
Ben Wilson avatar image
0 Likes"
Ben Wilson answered michel.torbey commented

The FlexSim 17.1.1 bugfix release is out now. Download it here:

https://www.flexsim.com/account/#/downloads

This release clears up the "CreateFile failed" errors mentioned in this question.

If you are seeing other errors after upgrading to 17.1.1, please post them to a new question.

Thanks!

· 1
5 |100000

Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.

michel.torbey avatar image michel.torbey commented ·

Hello Ben,

I just installed the update and seems that the errors' problem are solved.

Thank you.

As for the exception, i will try to find a solution as soon as I have time and will give you an update.

Best regards,

1 Like 1 ·
Ben Wilson avatar image
0 Likes"
Ben Wilson answered Ben Wilson commented

@Abel van der Windt, @michel.torbey,

We will ask the dev team to check into the source of that specific error message. Hopefully we can get you specific guidance for that particular error message later today.

In the mean time, here are some general tips which may or may not help with this error. If you have a chance, please check the following resources and let us know if any suggestions linked below cleared up the issue:

  1. We've seen some errors come as a result of Windows not including all available Microsoft updates. Please completely update your Windows installation, as well checking on the other items suggested in this post regarding startup/installation problems.
  2. You should always use the latest graphics driver, as well as trying the other tips found in this graphics compatibility post.

@michel.torbey, with your first error message regarding opening a workspace, assuming that you see this error when opening a specific model file, please try the following:

  1. open a new instance of FlexSim 17.1.0
  2. open your model - you will probably see those errors
  3. go to the main menu > View > Open Default Workspace
  4. save your model, preferably using a new file name so as to not overwrite your previous version of the model
  5. close FlexSim
  6. open FlexSim
  7. open the newly saved model
  8. does is still display an error regarding the workspace?
· 8
5 |100000

Up to 12 attachments (including images) can be used with a maximum of 23.8 MiB each and 47.7 MiB total.

Abel van der Windt avatar image Abel van der Windt commented ·

@Ben Wilson, @michel.torbey I tested some of the solutions. When I deleted the prefs.t file I don't get the error message anymore! Thanks for the quick reply.

0 Likes 0 ·
Ben Wilson avatar image Ben Wilson ♦♦ Abel van der Windt commented ·

@Abel van der Windt, that is great news! Thanks for the update!

@michel.torbey, you'll have to try that prefs.t solution that worked for Abel (as outlined at this post regarding startup/installation problems). Perhaps it would clear up your errors as well.

If not, there are also other suggestions at that link that you can try. Let us know if anything works.

Finally, if the problem is model specific (as in, you see the errors for just a particular model, but opening another model doesn't give you the errors), then it would be very helpful for us to see the model. If possible, post it to this public question. If it contains sensitive info, you could ask a new question, mark it as private, and post it there where only FlexSim's US-based support staff can see it.

0 Likes 0 ·
michel.torbey avatar image michel.torbey Ben Wilson ♦♦ commented ·
@Ben Wilson

Ok thank you Ben, I will try that on Thuesday and will give you a feedback as soon as possible.

Best regards,

Michel

0 Likes 0 ·
michel.torbey avatar image michel.torbey commented ·

@Abel van der Windt Thank you for you response. When i try and open the "Open Default Workspace", flexsim stops responding and i have to kill the process.

I will try again on Thursday and will give you an update.

0 Likes 0 ·
michel.torbey avatar image michel.torbey commented ·
@Ben Wilson

Thank you for your answer Ben.

Actually when i try openning the "Open Default Workspace", flexsim stops responding.

Do you have any idea what is hapenning?

0 Likes 0 ·
Ben Wilson avatar image Ben Wilson ♦♦ michel.torbey commented ·

@michel.torbey, no, I don't really have any good ideas why Open Default Workspace hangs. If it is a model-specific problem, then we'd need to look at your model to see what is in your view that causes the crash (infinite-loop?).

Or, if you have no model open at all, and then you select "Open Default Workspace", if that is crashing FlexSim, then it is not a model-specific problem, but rather an issue with your FlexSim installation or a system incompatibility. In that case, the suggestions outlined at this post regarding startup/installation problems would be your best bet, including the prefs.t solution that worked for Abel.

0 Likes 0 ·
michel.torbey avatar image michel.torbey Ben Wilson ♦♦ commented ·
@Ben Wilson

I have those errors when i open a specific model that i started in flexsim 2017 and updated it to flexsim 2017 update 1. Unfortunately i cannot send my model. I have tried to delete the pref file and didn't change anything. I will try all other solutions next week and will give you a feedback as soon as I can.

In the meantime, if you have discovered any solution, please keep me up to date.

0 Likes 0 ·
Show more comments