KeyShot2 does not work on Mac Pro but works on MacBook Pro

Started by narendain, August 20, 2010, 11:01:09 AM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

narendain

I have a strange scenario.  I have a Mac Book Pro (2.4 GHz Intel Core 2 Duo, 2GB RAM, OS X 10.6.4) that can launch KeyShot2 without any issues.  I also have a Mac Pro (2x2.93 Quad-Core Intel Xeon, 6GB RAM, OS X 10.6.4) that keeps asking me for the License Server and to restart KeyShot 2 Floating.  When I look at the console on the Mac Pro I see this:

The process has forked and cannot use this CoreFoundation functionality safely.  You MUST exec ().
Break on __THE_PROCESS_HAS_FORKED_AND_YOU_CANNOT_USE_THIS_COREFOUNDATION_FUNCTIONALITY__YOU_MUST_EXEC() to debug.

Any idea why this application works on my laptop and not my workstation?  Both computers are on the same subnet and can access networked resources without issues.


guest84672

in your home directory, there is a file called .flexlmrc. Can you take a look at the content and tell me what it is?

How are you accessing the server? By name, or ip address?

narendain

Where exactly in my home directory should I look for .flexlmrc because when I do a global search on both computers, it cannot be found.

I specifically have looked at:

/home/Library/Application Support/Luxion/KeyShot/

/Library/Application Support/KeyShot/

/var/flexlm/

And I access the server via name not ip address on both computers.

narendain

Hi Thomas,

Funny thing is, it works on these macs:

Name: Mac Pro
Processor: 2 x 3.0 GHz Dual-Core Intel Xeon
RAM: 2 GB
Video Card: ATI X1900 512MB
Operating System: Leopard 10.5.8

Name: Mac Book Pro
Processor: 2.4 GHz Intel Core 2 Duo
RAM: 4 GB
Video Card: NVIDIA GeForce 8600M GT 256MB
Operating System: Snow Leopard 10.6.4

But it does not work on this mac:

Name: Mac Pro
Processor: 2 x 2.93 Quad-Core Intel Xeon
RAM: 6 GB
Video Card: ATI RADEON 4870 HD 512MB
Operating System: Snow Leopard 10.6.4

I heard you are on vacation.  So, my colleague and I are working with Claus Jensen to resolve this issue.