Can't Borrow license

[dgschaefer]

We have two laptops, one XP 32 and one Win7 64, where license borrowing
won't launch on both WF3 & WF4.  We get these errors on both:











I seem to recall seeing this before and it was a permissions issue
somewhere.  The Pro/E install folders are full permissions for all
users, however, so I'm stumped as to what the problem might be.



Anyone?



Doug Schaefer

[mkelley]

Looks to me like you are getting a path error... The proe "bin" folder must be in the path in order for thelicense borrowing script to run. In the past, Itypically did this by opening a cmd shell in the "bin" folder and running the "proe_borrow.bat" script. Seems that this is what you are doing, too?

Also it looks like you are running Windows 7 here - andmy comments are based on WinXP... I am just beginning to test Win7; and so far my observation is that Microsoft has made my life harder, not easier! 🙂 In XP, the current directory was assumed to be in the path. Perhaps this behavior is changed in Windows 7???

Try typing "path" in your command prompt & see what it looks like.

[MikeBrattoli]

Good point Mark. I'm running Win 7 64 bit and I just checked my path -
the Pro/E install directory/bin folder are in the path on my laptop.
We've also found that the user must have full permissions to that same
Pro/E install directory in order to borrow licenses

[dgschaefer]

The bin folders are in my path.



Someone suggested that c:\temp needs full permissions as well, but I do
not have a c:\temp folder on my Win7 machine.



This is not a Win7 issue, it occurs on an XP Pro machine as well.  Not
only a laptop issue, it occurs on my desktop as well.



Another XP pro laptop is able to run the borrow script just fine.



Doug Schaefer

[dgschaefer]

OK, I've been doing some digging and have some more info on this issue.
I'm hoping that it might prompt someone's thinking.



The 32 bit XP machine was a permissions issue.  I set the permissions on
the install folders to full control for all and it works fine. It's not
related to the other issue.



Borrowing works fine on the new 32 bit Windows 7 machines, so it's a 64
bit Win7 issue.



Here's the situation.  We are running the 32 bit versions of WF3 and WF4
on our 64 bit machines (installing 64 bit is not an option right now)
however they are installed in 'program files' rather than 'program files
(9x86)'.  We copied the install directory to 'program files (x86)' but
borrowing still did not run.



So, what would prevent the 32 bit proe_borrow batch file from running on
a 64 bit system?



Doug Schaefer

[dgschaefer]

A solution!



So, in digging into this it turns out that the proe_borrow.bat is trying
to call an executable in the bin folder which in turn creates the
ptc_setvars.bat file.  In my case, the file it's trying to call is
'x86e_win64_ptc_setvars.exe', but it does not exist in that folder, the
only executable file there is named 'i486_nt_ptc_setvars.exe'. 



That led me to believe that perhaps this was a copy install from a 32
bit machine and perhaps running setup to properly set variables etc.
would correct it.  It did for the WF4 install, but not for WF3. In fact,
ptcsetup for WF3 wouldn't even run, giving me the same error.



So, that led to plan B for WF3.   So, for WF3 I simply created a copy of
the executable and named it 'x86e_win64_ptc_setvars.exe' and it now
works.  Not the 'right' solution I'm sure, but good enough.



Doug Schaefer

[A.DelNegro]

A customer sent me an assembly that he exported in Pro/E format from
SolidWorks.



I can open each part file and see the parts, but when I open the main
assembly, I see nothing. When I move my mouse over the screen, it
highlights the parts in the model tree, but not on the screen.



Anyone seen this? Any idea how to fix it?