STAR-CCM+ Error

mnws · January 1, 2021, 02:32

Dear all,

I attached an image of an error report that was generated when I was running STAR-CCM+. By the way, am using a POD licence.

The STAR-CCM+ simulation was able to complete a 24 hour run just a few hours before this error popped up at the beginning of a restart simulation. I usually run these simulations consecutively with no problem.

I have encountered a similar start up error before, and was able to remedy it by simply deleting the hidden App folder containing the temporary STAR-CCM+ files unique to each run. Re-installing the same version also works.

However I tried these 2 methods but was unsuccessful in troubleshooting.

Please let me know if you have any advice.

Best regards

bluebase · January 2, 2021, 09:33

Exit code 8 indicates a license issue. Search the manual for "exit error codes"

However, the other error code in the line "Error in checking out ccmpower: ...." seems unusual to me.

Since the sim tried to reach those three different locations (flex.cd-adapco.com, and 2 internal ips) I would rhetorically ask which address is your license server? Do you use POD licenses in general (the cd-adapco server) or an internal server. Either way, can you make sure, the compute nodes can actually reach the respective servers. There is a section regarding POD licenses in the manual.
Since you also write you could perform an initial run, i think there is no issue with reaching the license server.

My department also uses POD licenses. I remember for a while we had to manually order cpu hours in contingents of 10k hours, though i wasn't responsible for the departments licenses. Maybe ask your account manager, or respective colleague whether you used up your accounts cpu hours. Maybe renewing cpu hours hasn't been done fast enough. 1 day with 768 cores are already 18k hours.
I am not sure though whether the latter can be the cause, since there would be a distinguished error code if all credits/cpu hours would be used up.

mnws · January 4, 2021, 21:36

Dear bluebase,

Thanks for the reply. It turns out to be a recently expired POD license key issue. The new license key works fine.

Best,
mnws

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
[swak4Foam] swak4foam openfoam 7 installation problem	Andrea23	OpenFOAM Community Contributions	1	February 17, 2020 18:11
Undeclared Identifier Errof UDF	SteveGoat	Fluent UDF and Scheme Programming	7	October 15, 2014 07:11
OpenFOAM without MPI	kokizzu	OpenFOAM Installation	4	May 26, 2014 09:17
[Commercial meshers] Trimmed cell and embedded refinement mesh conversion issues	michele	OpenFOAM Meshing & Mesh Conversion	2	July 15, 2005 04:15
error while compiling the USER Sub routine	CFD user	CFX	3	November 25, 2002 15:16

January 2, 2021, 09:33		#2
bluebase Senior Member Sebastian Engel Join Date: Jun 2011 Location: Germany Posts: 566 Rep Power: 20	Exit code 8 indicates a license issue. Search the manual for "exit error codes" However, the other error code in the line "Error in checking out ccmpower: ...." seems unusual to me. Since the sim tried to reach those three different locations (flex.cd-adapco.com, and 2 internal ips) I would rhetorically ask which address is your license server? Do you use POD licenses in general (the cd-adapco server) or an internal server. Either way, can you make sure, the compute nodes can actually reach the respective servers. There is a section regarding POD licenses in the manual. Since you also write you could perform an initial run, i think there is no issue with reaching the license server. My department also uses POD licenses. I remember for a while we had to manually order cpu hours in contingents of 10k hours, though i wasn't responsible for the departments licenses. Maybe ask your account manager, or respective colleague whether you used up your accounts cpu hours. Maybe renewing cpu hours hasn't been done fast enough. 1 day with 768 cores are already 18k hours. I am not sure though whether the latter can be the cause, since there would be a distinguished error code if all credits/cpu hours would be used up.

January 4, 2021, 21:36		#3
mnws New Member Join Date: Dec 2020 Posts: 20 Rep Power: 5	Dear bluebase, Thanks for the reply. It turns out to be a recently expired POD license key issue. The new license key works fine. Best, mnws