Solution For Tekla Has Stopped Working Error When Closing Software
Susanne Sima
I noticed via Subversion that I apparently changed the project build Platform target to x64. This was the only change I had made. After making that change, the code was working for a short while before it started showing the same error you experienced. I changed the platform target to x86 to test and suddenly my designer was working again. Subsequently, I changed it back to x64, and the problem has disappeared completely. I suspect that the designer builds some kind of cached code in x32 and changing the x64 build platform breaks it when you make code changes.
Solution For Tekla Has Stopped Working Error When Closing Software
Download https://lomogd.com/2yV7p4
In my case, I had been building/rebuilding/cleaning the entire solution, instead of just the project that I was working on within the solution. Once I clicked "Build [my project]," the error message went away.
The solution for me was to unblock the assembly DLLs. The error messages you get don't indicate this, but the XAML designer refuses to load what it calls "sandboxed" assemblies. You can see this in the output window when you build. DLLs are blocked if they are downloaded from the internet. To unblock your 3rd-party assembly DLLs:
Sorry, those steps did not solve the problem. But it's interesting that with one of the drivers I chose during add printer, I got an error, and after that, it seemed like all the others resulted in the process appearing as if it worked, but no pdf was created. After uninstalling and reinstalling, I created a test windows profile and tried it there. It was the first time I saw "Acrobat Distiller has stopped working". subsequent tests resulted in the behavior described originally.
Discussion:
This error indicates that the FLEXlm routines in the application are unable to make a TCP connection to the server and port specified in the license file. Possible causes/solutions for this behavior are listed below
1.) PROBLEM:
The wrong license file is being referenced by IDL.
SOLUTION:
Verify that the application is using the proper license file. Check the paths and spelling of the licenses listed in the "license path" indicated in the error message.
2.) PROBLEM:
The server machine specified in the license file is down;
SOLUTION:
Verify that specified server machine is up and reachable by executing another command that uses TCP, such as ping, from the client to the server. For example, if the IP address of the license server machine "myserver" is 123.456.789.0, open a DOS command prompt on the IDL client machine and issue the command:
ping 123.456.789.0
or
ping myserver
TCP must be available on both the client and the server machines in order to use a floating license. If network problems are suspected, contact your system administrator for assistance.
3.) PROBLEM:
The license manager service is running but the IDL vendor daemon specified in the
DAEMON line of the license file (IDL_LMGRD.exe) is not running;
SOLUTION:
Check the license manager debug log file and run the lmstat command to try to determine if the vendor daemon is down and to get clues about how to resolve the problem=:
a.) Verify that the vendor daemon is running. Check the license manager debug log file that was specified when configuring the license manager.
b.) Examine the license manager debug log file to see if any problems are reported, particularly messages indicating that the vendor daemon has quit.
c.) Run lmstat -a from the server machine to verify that the vendor daemon is alive.
For example, if your IDL 6.4 installation is located at C:\Program Files\ITT\ IDL64 and license manager was started using a license file with the following SERVER line: