Arbortext PE Interactive (6.0 m010) was not able to obtain a license [terminal services issue]

[naglists]

Hmmm. Did we talk about this already? I seem to have forgotten it if so or
discovered another wrinkle with the new licensing. I am unable to edit
e3config.xml using PE Interactive. I *think* it is because I am, of course,
accessing the server via Remote Desktop / Windows Terminal Services.

[A31679] Arbortext PE Interactive was not able to obtain a license
License problem: Cannot checkout an uncounted license within a Windows
Terminal Services guest session.

The server is properly licensed to do PE tasks according to
..e3/servlet/e3?f=license

--
Paul Nagai

[naglists]

FWIW: When I select the "Edit Configuration using PE Interactive" button on
the e3config.exe dialog, e3config.exe hangs. I had to kill it. I
eventually tried to open PI directly which displayed the error below.

[ClayHelberg]

I think we did cover this before, when 6.0 first came out. This is one
of the issues with the new Flex licensing. You can only use Remote
Desktop if you have a floating license. Won't work with a fixed license.
Very irritating for situations like yours where you are using RD to
manage a server located elsewhere.



You might be able to work around it by using a different remote access
technology like VNC or GotoMyPC, if that's an option for you.



--Clay



Clay Helberg

Senior Consultant

TerraXML

[AndyEsslinger]

You may need to convert to a "Registered User" license. Open a case and ask tech support.

\ / Andy Esslinger LM Aero - Tech Order Data
_____-/\-_____ (817) 279-0442 1 Lockheed Blvd, MZ 4285
\_\/_/ (817) 777 3047 Fort Worth, TX 76108-3916

[berard]

Yes VNC works. I've been trying a few scripts using something like psexec
or using the task scheduler to remote-run the process in, say, 3 seconds,
but I haven't had much luck. I'll keep trying, as this is an issue for us
as well. FLEX also has issues if you have your license bound to one NIC,
but then change (eg: from WiFi to ethernet)

[naglists]

Licensing support has confirmed what you have already said: A floating
license is required to use Publishing Engine Interactive to edit
e3config.xml via Remote Desktop/Terminal Services. What licensing could not
tell me was whether a single floating license would enable PE to handle
composition requests at the same time as Publishing Engine Interactive. I
assume it is one license request that "works" for both situations, but
would like confirmation. (Also, floating licenses are more expensive than
locked licenses. Yay.)

I will more easily install a different XML editor on my PE servers than
convince security/operations to allow me to use a different method of
remote access. Besides, the irony of configuring Publishing Engine using
XML Spy or oXygen is really too good to pass up.

[KarlJohanKleist]

> Besides, the irony of configuring Publishing Engine using XML Spy or oXygen is really too good to pass up.

Or "Liquid XML Studio", which doesn't suffer from having a Java based GUI. And its XSD editor rocks.

[GarethOakes]

Hi there,



PTC promised that for existing customers that use the software there would
be no loss of functionality between 5.4 and 6.0. You should be able to get
your locked license converted to floating so you can access PE Interactive
remotely. I'm pretty sure that you would not be able to run both PE
Interactive and PE as a server side by side though.



// Gareth Oakes

// Chief Architect

// GPSL (www.gpslsolutions.com)

[naglists]

All kidding aside (I wouldn't really install another XML editor ... I'd
just edit the file in notepad), technical (not license) support now
confirms that a single floating license should enable both composition
request and PE Interactive simultaneously.

Now I will have to decide whether or not to get my licenses converted and
install a license server. I hate moving parts. On the other hand, I know
NOT having access to the rich PE error reporting that is only available
through PE Interactive will bite me in the future if I do not convert them
/ install the license server. I know it.

Has error reporting improved in 6.0? Specifically, are all composition
failure / warnings available to an author using Editor? Or are there still
some errors that are only really explained in a PE Interactive session?