Plex 2E

  • 1.  Negative Surrogates Error

    Posted Oct 01, 2010 02:13 AM
      |   view attached
    Good Day

    I hope somebody can assist me. On one of our group models when we extract from this model (The Update to the model is working 100%) we get a "negative Surrogates Error"

    I have tried a couple of things but I cannot get rid of this error. I tried to "Output Implementation names" and found a few objects that has negative surrogates. I fixed them, updated the model again. Extracted, same error.

    It is not causing any problems (That I know of) at the moment. I am just worried that there might be some underlying problem which can cause problems with the group model.

    Any ideas will be welcome!


  • 2.  RE: Negative Surrogates Error

    Posted Oct 01, 2010 02:52 AM
      |   view attached
    Title: NEGATIVE SURROGATE ERROR MESSAGE



    At Plex r5.1SP1 and below an error, displayed either in the message log or
    as a dialog is displayed during extraction if group model incorrectly has
    triples assigned with a negative surrogate. This error handling does not
    produce an error message in Plex 5.5SP1 and 6.0. The intended message is

    "16 negative surrogates were found in group model MYGROUP , please contact
    product support."


    RESOLUTION:

    Fixed at 5.5SP1 Bld 93.031, 6.0.47.011 and for 6.1.

    For more information about this error message search for "CPLEX 1523" and
    Knowledge Base document TEC468925.




    Great document attached also!
    Cheers
    George

    Attachment(s)



  • 3.  RE: Negative Surrogates Error

    Posted Oct 04, 2010 02:47 PM
    I know of one client that has had that issue for years without any apparent problems. Upgrading to 6.1 does not fix the problem, but I believe there is an INI setting to hide it.


  • 4.  RE: Negative Surrogates Error

    Posted Oct 05, 2010 08:55 AM
    I Tried the Plex INI file setting.. Bit it does not seem to do anything. Still getting the Negative Surrogate Error in the Error Log.


  • 5.  RE: Negative Surrogates Error

    Posted Oct 05, 2010 12:15 PM
    did you get to read the attached document in my first post which probably gives the most comprehensive descrition of negative surrogates you will find anywhere.

    Attachments: 258_Access_Manager_Client.pdf (28.5k)


  • 6.  Re: Negative Surrogates Error

    Posted May 18, 2017 03:22 PM

    Hi, we have the same problem.

    We want to find wich object has the negative surrogate to modify it, but we cannot find it.

    We export our model in XML, but it's difficult to find what we want. We also used the function "Output File for Implementation Names". I see 9 negatives surrogates, but there are SYSTEM objects and I think that it's normal. But I tought that I could find another object...

    Does someone know how to find wich object is the negative surrogate ?

     

    It is important to take the time to fix it ?

    Can we simply change our Plex.ini as it wrote in the George's document and we will never have this warning?

     

    Thanks

    Eric



  • 7.  Re: Negative Surrogates Error

    Posted May 18, 2017 03:25 PM

    We used Plex r7.2 (Build 22.000)



  • 8.  Re: Negative Surrogates Error

    Posted May 19, 2017 03:31 AM

    I suppose you have seen the discussion on the subject at Plex Help (User Guide/Model Management/File and Directory management/Group Model Integrity Checks), and the document added above by George. We have investigated last year this subject with CA Support, because we found several surrogates in a couple of models at 7.2 level. Support insisted in disregard such negative surrogates while they were a few. Only if surrogates were of high order it would require attention. In our case, it never passed from 15/20. In some of that cases negatives finally dissapeared. Anyway, we have the precaution of assuring such surrogates not pertain to critical objects. It was the case that no one was in use.



  • 9.  Re: Negative Surrogates Error

    Posted May 19, 2017 11:34 AM

    Ok, I will check if the number increases and if not, I will not investigate more than that.

    Thanks for your response.