cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

New user access to servicemanual.pcf file on the Publishing Engine server

LisaA
Newbie

New user access to servicemanual.pcf file on the Publishing Engine server

Hello,


I have some publishing profiles set up in the servicemanual.pcf file in our custom directory on our Publishing Engine server. We just added another user to the system (for the first time), and her Arbortext editor does not "see" the .pcf file. She does have read access to the custom directory. She is using a floating license. Any ideas on what is preventing her access to theprofiles?


Arbortext 6.0, Windchill 10.0


Thanks,


Lisa Antell


Tempe AZ


Tags (2)
12 REPLIES 12

Running Arbortext 6.0 and a previous version simultaneously

I think that it is unlikely that anyone has this particular problem, but since we are having issues with our PTC contract and I am waiting for a return call from them so maybe I can talk to PTC technical support, I thought I would throw this out there.

We have a home-built program that launches Arbortext Editor from the Windows command line and uses Windows registry settings to launch the appropriate software for editing an XML file (in this case, Arbortext Editor version 5.2).

We have another program that uses a different version of Arbortext Editor and doesn't need to use the Windows registry. Previously, this used Epic Editor 4.3.1. Now this program has upgraded to Arbortext Editor 6.0.

On a PC with both versions installed, when running either Editor 5.2 or Editor 6.0 from the Windows Start button, they work fine.

Unfortunately, using Arbortext 6.0 *only one time* totally hijacks all of the registry settings and makes our home-grown application also try to use Editor 6.0 when launching from the Windows command line.

Anybody got any ideas?


Running Arbortext 6.0 and a previous version simultaneously

While we still keep an older copy of Arbortext 5.3 around on our server
(mainly due to launching problems over Terminal Services with the new
licensing), I do know I always did "epic.exe -regserver" call to line up
the DLLs.

I'm still not sure if that really did anything useful, but I thought I'd
throw it out there to try.

EXTERNAL: Running Arbortext 6.0 and a previous version simultaneously

I forgot to mention that we are launching Editor from COM which seems to be part of the problem. I will mention the epic.exe -regserver thing and see what happens. Thanks

EXTERNAL: Running Arbortext 6.0 and a previous version simultaneously

Well, adding that command to our batch file that launches our home-grown application seems to do the trick. Thanks for that!

EXTERNAL: Running Arbortext 6.0 and a previous version simultaneously

Glad it worked, and thank you as well... I was starting to feel like a bit
of an adepters lurker with nothing to contribute 🙂

EXTERNAL: Running Arbortext 6.0 and a previous version simultaneously

Been there. It's only a matter of time ... if you stick around long
enough, someone has a problem you've solved before ... and you get the joy
of paying it back or forward or whatever it is relative to your internal
tote-board.


New user access to servicemanual.pcf file on the Publishing Engine server

Is the new user's system set up to find the custom directory? This would
require APTCUSTOM to be pointing to it, set either in her environment or in
a batch file used to start Editor. You can check that the custom directory
is correctly configured by selecting "Session" from the "Help" menu and
looking at the "Custom directory path" value on the "Session" tab in the
resulting dialog.

Next, have her open or create a document of that type and check the
"Profiling configuration" value on the "Document" tab in the session
dialog, as above. It has been my experience that just having the PCF file
in the appropriate directory under "doctypes" in your custom directory
won't necessarily affect anything. Rather, I've had to put a copy of the
DCF there and have it point to my customized PCF file. Assuming you have
this set up, check that Editor is using that DCF file by checking the
"Doctype configuration" value on the "Document" tab.

-Brandon 🙂


RE: New user access to servicemanual.pcf file on the Publishing Engine server

Thank you for the info.


I compared my Session window to the new user's, and we see where her Profiling Configuration is not pointing to the profile configuration on the server. Her doctype configuration actually is pointing to the server correctly.


Might you have any idea how to get her Profile configuration to point correctly, like mine does?


Lisa Antell

New user access to servicemanual.pcf file on the Publishing Engine server

With the advent of pervasive technology in nearly every aspect of our
lives, it has been found that while the definition of insanity remains the
same, the leading cause is now using the (presumably) same configuration
over and over and somehow getting a different result. 😉

You're off to a good start with the troubleshooting, so now it's time to
question the assumptions.

So far as I'm aware, the only way to point to a different profiling
configuration is with a different setting in the doctype configuration.
Can you try making a change in the DCF and confirm that, after restarting
Editor, both machines reflect the change? What does the profiling section
of the DCF look like? Perhaps there's something odd going on with a
relative path?

What does the network path where these files reside look like? If a mapped
drive is being used, is it mapped identically on both machines?

-Brandon 🙂


EXT : New user access to servicemanual.pcf file on the Publishing Engine server

Brandon:
I listen in to adepters daily, though rairly contribute as my work is seldom common to the problems I read about. I do, however, particularly enjoy the level of thought that seems to run with this crowd.

I found your first statement one I'd like to quote; it appies so wel to situations I run into. I also try and correctly attribute what I borrow; are these your original words or from another source?

With the advent of pervasive technology in nearly every aspect of our lives, it has been found that while the definition of insanity remains the same, the leading cause is now using the (presumably) same configuration over and over and somehow getting a different result.


Robert Paisley, MSCS, MSSE
The price of anything is the amount of life you exchange for it."--Henry David Thoreau

EXT : New user access to servicemanual.pcf file on the Publishing Engine server

Thank you, Robert. The words are all mine, so feel free to borrow as you
like.

-Brandon Smiley Happy


On Tue, Jun 12, 2012 at 11:40 AM, Paisley, Robert G (AS) <
-> wrote:

> **
> Brandon:
> I listen in to adepters daily, though rairly contribute as my work is
> seldom common to the problems I read about. I do, however, particularly
> enjoy the level of thought that seems to run with this crowd.
>
> I found your first statement one I'd like to quote; it appies so wel to
> situations I run into. I also try and correctly attribute what I borrow;
> are these your original words or from another source?
>
> With the advent of pervasive technology in nearly every aspect of our
> lives, it has been found that while the definition of insanity remains the
> same, the leading cause is now using the (presumably) same configuration
> over and over and somehow getting a different result.
>
>
> Robert Paisley, MSCS, MSSE
> The price of anything is the amount of life you exchange for it."*--Henry
> David Thoreau*
>

EXTERNAL: EXT : New user access to servicemanual.pcf file on the Publishing Engine server

Brandon,
Are you sure that Single-Sourcing doesn't own those words now? Oh, wait...you're a consultant, not an employee, so maybe not...
Announcements