Skip to main content
L
LisaA1-Visitor
1-Visitor
June 1, 2012
Question

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

  • June 1, 2012
  • 12 replies
  • 2520 views

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


    12 replies

    Show previous replies
    B
    bibach1-Visitor
    1-Visitor
    June 12, 2012
    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*
    >
    E
    ebenton1-Visitor
    1-Visitor
    June 12, 2012
    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...
    Terms & ConditionsAccessibility statement