Front End Server in pool not showing as possible registrar server

Hi All,
We have recently another server to our front end pool. At first we had only one server, and now we have added the second server to the pool.
However doing a get-csuserpoolinfo command we are getting these result
Get-CsUserPoolInfo sip:testuser2@domain
Identity                            :
testuser2@domain
PrimaryPoolFQDN                     : lyncpool.domain
BackupPoolFQDN                      :
UserServicesPoolFQDN                : lyncpool.domain
PrimaryPoolMachinesInPreferredOrder : {fe01.domain}
BackupPoolMachinesInPreferredOrder  : {}
PrimaryPoolPrimaryRegistrar         : fe01.domain
PrimaryPoolBackupRegistrars         : {}
PrimaryPoolPrimaryUserService       : fe01.domain
PrimaryPoolBackupUserServices       : {}
BackupPoolPrimaryRegistrar          :
BackupPoolBackupRegistrars          : {}
BackupPoolPrimaryUserService        :
BackupPoolReplicaUserServices       : {}
Now we have fe02 deployed as well however this is not displayed for this testuser or any other user in our deployment. This is also causing the problem that if fe01 is not available the client will not automatically try to connect to fe02.
Thank you for your support!
Joseph

The Replica Instances for Routing Service does not add the second server fe01.domain, however for the other replicas the other server is added.
 Get-CsPoolFabricState -PoolFqdn lyncpool.domain
Replica Instances for MCUFactory Service
    Address: fe01.domain - Primary: 6 Secondary: 0
    Address: fe02.domain - Primary: 0 Secondary: 6
Replica Instances for ConferenceDirectory Service
    Address: fe01.domain - Primary: 1 Secondary: 0
    Address: fe02.domain - Primary: 0 Secondary: 1
Replica Instances for Routing Service
    Address: fe01.domain - Primary: 7 Secondary: 0
        Local Groups: Primary: 7 Secondary: 0
        Remote Groups: Primary: 0 Secondary: 0
Replica Instances for LYSS Service
    Address: fe01.domain - Primary: 7 Secondary: 0
    Address: fe02.domain - Primary: 0 Secondary: 7
Global Service Count Summary:
Fqdn: fe01.domain - Primary: 21 Secondary: 0
Fqdn: fe02.domain - Primary: 0 Secondary: 14

Similar Messages

  • The Document Conversions Launcher Service status on a SharePoint Server 2013 Web front-end server displays "Starting" but does not start or stop

    I have this strange error showing up from my second Web Front End Server, "The Document Conversions Load Balancer service is stuck in starting, The status showing up "Error Starting". When I lunch the start, it runs then went back to
    the same status "Error Starting" for the "Document Conversions Load Balancer Service". How can I get of rid this issue?

    Hi Mannyabdon,
    Based on your description, I recommend to check the things below:
    1.  Run the PowerShell command below to check the status of the Secure Store Service:
    Get-SPServiceInstance |Where {$_.typename -like "Document Conversions Load Balancer Service"}
    If it is not showing online, please stop the service first and then start it to see if the issue still occurs (the
    <ServiceGUID> can be obtained obtained from the command above).
    Stop the service:
    Stop-SPServiceInstance -Identity <ServiceGUID>
    Start the service:
    Start-SPServiceInstance -Identity <ServiceGUID>
    2.  Check the ULS log for detailed error message.
    For SharePoint 2013, by default, ULS log is at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\LOGS.
    Thanks,
    Victoria
    TechNet Community Support
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
    [email protected]

  • Lync phone edition does not try to sign in after the front end server restarts

    A restart of the frontend server. None of our Lync Phone Edition CX600 and CX3000 phones will sign back in. If you hit the cancel button and click it will work. This was fixed in a previous CU update but seems to be back again. CX version 4.0.7577.4451.
    Any ideas to try. Cant always restart our switches.

    Hi,
    Please install the update KB3014910 in the link below:
    http://support.microsoft.com/en-hk/kb/3014910
    The Update resolves the issue: Lync Phone Edition cannot automatically sign in when the primary front-end server that you register is shut down.
    If the issue persists, please also try to reset the IP phone and test again.
    Best Regards,
    Eason Huang
    Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
    Eason Huang
    TechNet Community Support

  • Lync 2013 Enterprise load balancing on the front end and edge pool

    Hi,
    I am setting up a Lync 2013 Enterprise deployment consisting of a Front End pool (x2 FE servers) and an Edge pool (x2 Edge servers).  I'm seeing some conflicting advice regarding load balancing using hardware or DNS for the front end and the edge.
    On the front end I have 2 internal DNS records 'lyncfepool1.contoso.local' each of which map to one of the IPs of the FE servers.  I've used my details to populate the Detailed Design Planner excel spreadsheet and am told that I require a HLB to load
    balance my front end pool.  I'm aware of the need to load balance HTTPS traffic internally (which will be done by TMG) however other traffic to the front end (SIP, etc) can be balanced by DNS only, and not require a HLB?
    Can someone clarify the front end requirement?
    Also - looking now at the edge pool - this site again have two edge servers in a pool.  We are using a total of six private IP addresses, two per edge service (2 x av.contoso.com, 2 x sip.contoso.com and 2 x webcon.contoso.com).  These will be
    NAT'ed by the external firewall and directed to the respective external (DMZ) IP addresses on the Edge servers on port 443.  I know this isn't true roundrobin due to the intelligence of the Lync client when connecting (in that the Lync client will connect
    to one of the public IPs and if it can't connect, it will know to connect to the other service IP), however I want to clarify this set up, particularly the need to direct the external public IP traffic at the DMZ Edge IP specified in the topology builder.
    I've attached a basic diagram of the external/DMZ/Edge side which hopefully helps with this question
    Persevere, Persevere, Per..

    That is because you will always need HLB for a front-end server since it hosts the Lync webservices which use HTTP/HTTPS traffic.
    The description on the calculation tool also describes this correctly:
    Supports Standard and Enterprise pools (up to 12 nodes), with pure device-based load balancing or a combination of DNS load balancing and device-based load balancing (for
    Lync web services)
    You can use either Hardware or DNS loadbalancing for SIP traffic only, but you will always need a HLB for the webservices.  Both are applicable for the Front-End so you have either
    full HLB for both SIP and HTTP(S) traffic
    DNS LB for SIP traffic and HLB for HTTP(S) traffic
    Hope this is more clear :-)
    Lync Server MVP | MCITP Lync Server 2010 | If you think my post is the answer to your question, please mark it as answer so future visitors can easily find it.

  • 2 Front-end vs 3 Front-end server

    Hi everyone,
    Our front-end pool will consist of 2 front-end servers for high availability. One front-end server should support 10,000 users, but since the recommendation for a front-end pool is 3 servers, i want to know if deploying only 2 could be a real issue. What
    I understand from the Technet documentation is that the way user data is stored (1 primary copy and 2 backup copies) is one reason (but I would thing not enough reason for us as a company of 1200 users) and that you need to shutdown and bring them up again
    in a specific order. Am I missing something what would definitely make me deploy 3 front-end servers? 

    I'd say just never do two front end servers, it's not recommended at all.
    Check out these links to learn more and see some experiences:
    Check out Richard Brynteson's blog post
    http://masteringlync.com/2013/10/29/understanding-how-windows-fabric-works/ (thank you for writing this up, Richard!)
    http://ucnew.wordpress.com/2013/08/16/lync-server-2013-2fe-2be-high-availablity-issue/
    http://unifiedme.co.uk/2013/04/lync-server-2013-front-end-architecture-process-and-can-you-run-enterprise-edition-pool-with-one-two-front-end-servers/
    Per TechNet "If you do not want to deploy three Enterprise Edition Front End Servers and want high availability and disaster recovery, we recommend you use Lync Server Standard Edition and create two pools with a paired backup relationship. This
    will provide the best high availability and disaster recovery solution with only two servers."
    http://technet.microsoft.com/en-us/library/gg412996.aspx
    Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer".
    SWC Unified Communications

  • High availability for Web front END server

    Dear All
    I am unable to understand the high availability model for Web front end server
    I am currently working on MOSS 2007/IIS 7 but I think for all versions it will remain the same
    I am now running single WFE server and my installation mode allow for adding extra servers to the Farm
    now when I add Extra server what will happen next ? should I add extra web application and site collections ? will load balancing include lists, library items and workflows
    how this stuff will be stored on one database
    it's too vague to me so extra explanation will be appreciated
    Regards

    To get a fault tolerant environment you need to do two things.
    1) Add a second server that is running the the Microsoft SharePoint Foundation Web Service.  That's the service that responds to calls for the web site making the server a WFE.
    2) Implement some form of load balancing to distribute HTTP requests for SharePoint web sites to the two servers.  This can be done with something as simple as Windows Network Load Balancing or with dedicated hardware like an F5 Load balancer.  
    Once you've added a load balancer and a second server you don't need to do anything else.
    Paul Stork SharePoint Server MVP
    Principal Architect: Blue Chip Consulting Group
    Blog: http://dontpapanic.com/blog
    Twitter: Follow @pstork
    Please remember to mark your question as "answered" if this solves your problem.

  • Front End Server Certificate Renewal

    I would like to see if someone could offer simple clarification to a hopefully simple question.  My OAuth and Default Certificates are expiring soon.  
    Can I request a certificate, using the wizard (which has worked before so no issues there) and effectively "stage" it to later assign during my scheduled maintenance window so I can simply assign and reboot?
    It isn't exactly imperative that this works in exactly this way, it would just be nice to request the certificate and ease my workload later, sort of like staging system patches but with certs, ha ha.
    Thanks.

    That's exactly how you'd do it.  Request it and stage it, confirm that you can assign it but don't.  Then, during your maintenance window you'd assign it and restart.
    oAuth you'd only assign once to a primary Front End, that should replicate out on it's own.  The other certs you'd need to assign individually to each front end, reverse proxy, etc.
    Please remember, if you see a post that helped you please click "Vote As Helpful" and if it answered your question please click "Mark As Answer".
    SWC Unified Communications
    This forum post is based upon my personal experience and does not necessarily reflect the opinion or view of Microsoft, its employees, or other MVPs.

  • Site not accessible from the Load balanced web front end server - sharepoint 2010

    I have a production environment with 2 WFE's(sp-wfe1 & sp-wfe2), 2 APP's and 2 SQL clustered VM's.
    2 WFE's are load balanced using hardware load balancer.
    An A-Record(PORTAL) is created in DNS for the virtual IP of the load balancer which points to the 2 WFE's.
    A web application is created on the WFE's on port 80.
    alternative access mapping is configured and the load balanced record "http://PORTAL" is used under the default zone.
    Under IIS I have edited the bindings for the sharepoint site at port 80 and added the HOSTNAME as PORTAL.
    Result: The site is accessible from outside the server and works fine.
    ISSUE: The site is not accessible within the WFE's(sp-wfe1 & sp-wfe2).
    When I browse the site from the WFE's server it ask for the credentials and when I enter the credentials and click OK it ask the credentials again and again and in the end displays a blank page.
    Kindly help me in this issue because I am clueless and couldn't find anything helpful on the internet. 
    Regards,
    Mudassar
    MADDY-DEV Forum answers from Microsoft Forum

    Loop back check.
    http://www.harbar.net/archive/2009/07/02/disableloopbackcheck-amp-sharepoint-what-every-admin-and-developer-should-know.aspx

  • SharePoint Search is failed when request comes from one front end server

    Hello colleagues!
    I have a SharePoint 2013 farm with 3 server: batch, wfe 1, wfe 2
    Search topology includes batch and wfe 1 servers.
    So when search request comes from wfe 1 search service works fine. When search request comes from wfe 2 search service is failed.
    In logs there is an error:
    A failure was reported when trying to invoke a service application: EndpointFailure Process Name: w3wp Process ID: 16556 AppDomain Name: /LM/W3SVC/234569039/ROOT-4-130544984716198913 AppDomain ID: 6 Service Application Uri: urn:schemas-microsoft-com:sharepoint:service:9d3cd1b87fc848c0b7bbbfb95a7fd7a0#authority=urn:uuid:08a793bc71b54dfcb7f0cf2d6cc35c4f&authority=https://wfe2:32844/Topology/topology.svc
    Active Endpoints: 1 Failed Endpoints:1 Affected Endpoint:
    http://batch:32843/9d3cd1b87fc848c0b7bbbfb95a7fd7a0/SearchService.svc
    I have gone through the link
    http://batch:32843/9d3cd1b87fc848c0b7bbbfb95a7fd7a0/SearchService.svc It works from any server and any workstation except wf2
    When I open the link on server wfe2 I get:
    HTTP Error 503. The service is unavailable.
    Please help to understand what is wrong.
    Thank you for your help

    Hi Anna,
    Is this issue resolved?
    Is there anything update about this issue?
    Best regards.
    Thanks
    Victoria Xia
    TechNet Community Support

  • Toplink Expression - edit button not showing all possible field names

    Hi,
    i use Jdev 11g (11.1.1.0.1) with TopLink. I created a Toplink mapping and everything works well. I now want to create another named query with a selection criteria, but the Edit-Button in the Expression Builder for the selection criteria isn't working well. If i click the button nothing happens, but JDev freezes for about 15 sec. Anyone else with this problem ?
    Thanks,
    Friedrich

    You should put all your menus in the root menu.
    <?xml version="1.0" encoding="utf-8"?>
    <openbox_menu xmlns="http://openbox.org/3.4/menu">
    <menu id ="root-menu" label="Exit">
    <item label="Reboot">
    <action name="Execute">
    <execute> sudo /sbin/shutdown -r now </execute>
    </action>
    </item>
    <menu id="apps-accessories-menu" label="Accessories"/>
    <menu id="apps-editors-menu" label="Editors">
    <item label="Scite">
    <action name="Execute">
    <command> scite </command>
    <startupnotify>
    <enabled> yes </enabled>
    </startupnotify>
    </action>
    </item>
    </menu>
    </menu>
    </openbox_menu>

  • Lync Server 2013 Front End Pool Mediation Service only works on one node

    Hello, I'm currently experiencing an interesting issue with a Lync 2013 Front End Pool implementation on a customer, and I don't know if this is by design or am I missing something.
    We implemented 3 Enterprise Front End Servers in a Pool with a hardware load balancer and we have them configured also as a mediation Pool.
    We have a SIP trunk to an Avaya PBX which was perfectly working before on a Lync 2010 Implementation that we migrated to these new 2013 Front End Pools.
    Now the SIP traffic is only working when configured directly to one node of the pool. If we configure it to any other node the calls fail. We also tried configuring the HLB for port 5060 for the pool and pointed the PBX to that IP but the calls also fail.
    Searching around I read something about that the PBX has to be Lync certified in order to use DNS load balancing to send SIP traffic to the mediation pool, however, I don't think DNS load balancing will work because the other nodes doesn't connect the calls
    from the PBX, only one node appears to be listening for the SIP Trunk.
    I also restarted the mediation service on one  non-working mediation server node and the event viewer on the working mediation server node showed events that it restarted the service, Not the non-working one, it's like only one server from the pool
    is doing as mediation server. 
    So even if I get a Lync Certified PBX/Media Gateway, the mediation service doesn't appear to be load balanced, or how does it work in order to do that?
    Thanks.
    Eduardo Rojas

    Just a few things about what should be happening.  Each front-end server should be listening on the port configured in topology builder for the mediation service. So if that is port 5060, verify that you see that port listening on all front-end servers
    by running a netstat -ano.  From a local workstation, also make sure you can connect to that port via a telnet IPAddress 5060.  As you say, you should be able to send any of the three mediation servers an inbound call.
    Outbound calls will round robin out of the enterprise pool.  So you shouldn't see all of the calls coming out of a single server.
    A few other items I would look into:
    - Make sure your ports are right.  Ensure that you are matching ports on the Avaya and Lync.  It's not a hard requirement but makes life easier to troubleshoot.  So if the Avaya is 5060, just make sure TCP/5060 enabled in your mediation pools
    and that your gateways/trunks are also set to TCP/5060.
    - Look outside the Lync Event Viewer and see if anything strange (.net errors) are being tossed anywhere else during startup of the mediation service.  I once had to remove the mediation server installer (Program and Features | Remove) and rebootstrap
    the server because something went sideways during an install.
    Thanks,
    Richard
    Richard Brynteson, Lync MVP | http://masteringlync.com | http://lyncvalidator.com

  • Lync 2013 On Prem - Front End Pool - Second server in pool becomes unavailable when first server is offline

    We have one front end pool, that contains 2 front end servers running Lync Server 2013.
    When the first server, LFE01 goes offline (to be restarted for instance), the second front end server LFE02 in the same pool's Lync services will suddenly stop and will refuse to start until LFE01's Lync services have started again.
    During this time, the Lync client will go from full functioning mode whilst LFE01 is up and running, to reduced functionality (when LFE01 is restarting), to the user being signed out of Lync and not able to log back in. As soon as LFE01 comes back up, users
    can log back in to Lync.
    We'd ideally like LFE02 to take over the front end server role whilst LFE01 is restarting, and vice-versa.
    Checking the event logs on LFE02, I can see the following errors when LFE01 is offline:
    This process was not able to update its health status
    The Audio-Video Conferencing Server failed to send health notifications to the MCU factory at https://frontendpool.contoso.com:444/liveserver/mcufactory/. 
    Failure occurrences: 30, since 7/11/2013 3:40:38 PM.
    Cause: Either the Front End service is not running, or poor network connectivity.
    Resolution:
    Verify that the Front End Service is available, and its machine is visible over the network.
    This process was not able to update its health status
    The IM Conferencing Server failed to send health notifications to the MCU factory at https://frontendpool.contoso.com:444/liveserver/mcufactory/. 
    Failure occurrences: 30, since 7/11/2013 3:40:42 PM.
    Cause: Either the Front End service is not running, or poor network connectivity.
    Resolution:
    Verify that the Front End Service is available, and its machine is visible over the network.
    Server startup is being delayed because fabric pool manager is initializing.
    Cause: This is normal when Pool is bootstrapped and indicates that the Front-End is waiting for a quorum of other Front-Ends to be started.
    Resolution:
    If this event recurs persistently, ensure that 85% of the Front-Ends configured for this Pool are up and running. For 2 or 3 machine Pools, initial cold-start of the Pool requires all machines to be started. If multiple Front-Ends have been recently
    decommissioned, run Reset-CsPoolRegistrarState -ResetType QuorumLossRecovery to enable the Pool to recover from Quorum Loss and make progress.
    Does the first server in the pool need to be up at all times for the second server to be running? If so, I may need to re-plan my redundancy.

    I can't believe how inaccurate these statements are. 
    Yes as per Microsoft it is best practice to have 3 FE in a pool but that absolutely does not mean that if you have 2 FE server in a pool that your pool will stop working!!
    In case when you do have 2 FE servers in a pool your Back End primary database server will act as a vote to keep the quorum for single server still left in a pool and all your clients will keep operating in a pool with one FE still running. 
    The problem with having 2 FE in a pool as per Microsoft documentation is as follows:
    If one of the two Front End Servers goes down, you should try to bring the failed server back up as soon as you can. Similarly, if you need to upgrade one of the two servers, bring it back
    online as soon as the upgrade is finished.
    If for some reason you need to bring both servers down at the same time, do the following when the downtime for the pool is finished:
    The best practice is to restart both Front End Servers at the same time.
    If the two servers cannot be restarted at the same time, you should bring them back up in the reverse order of the order they went down.
    If you cannot bring them back up in that order, then use the following cmdlet before bringing the pool back up:.
    http://technet.microsoft.com/en-us/library/gg412996.aspx
    I tested this in my environment which I currently am running with 2 FE servers and I can categorically confirm that pool will continue operating. 
    However, with all this said I did notice that clients with connection to FE server that is shut down take anywhere from 2-9 min to reconnect. I was trying to figure out why such a long delay until clients reconnect. Possibly it might be because there are
    2 FE servers in a pool and Back End server is taking a while to vote in turn delaying auto reconnect process for clients. Second possibility that I'm looking into is that we deployed HLB for sip traffic internally as well and I'm curious if using DNS LB would
    fix this delay.
    I'm just so disappointed how inaccurate some of these accepted answers above are.

  • 2 Front End Servers with reporting enabled in topology but only one server shows reports

    Hi,
    We have 2 Front End Standard pool servers with resiliency enabled between them. The monitoring service is configured in the topology so that both Front End Servers point to the same monitoring database. We have half our users homed on 1 Front
    end and half the other users sitting on the other Front End. In the Reports we can only see information on Audio calls made from users that are sitting on our Primary Front End Pool Server however we cannot see call information from users that are sitting
    on the other front end server?
    Thanks, Kevin

    We have applied the backend updates and verified the config by running Test-CSDatabases cmd-let . I ran enable-cstopology and ran bootstrapper.exe and rebooted both Front End Servers, however we are still unable to see monitoring data of users
    homed on our second Lync Front End server.
    Any other suggestions? Thanks for responses so far, appreciate the assistance!
    DatabaseName               ExpectedVersion            InstalledVersion
    xds                        10.13.2                   
    10.13.2
    lis                        3.1.1                     
    3.1.1
    rtcxds                     15.13.1                    15.13.1
    rtcshared                  5.0.1                      5.0.1
    rtcab                      62.42.2                    62.42.2
    rgsconfig                  5.5.1                      5.5.1
    rgsdyn                     2.2.1                     
    2.2.1
    cpsdyn                     1.1.2                     
    1.1.2
    and ......
    DatabaseName               ExpectedVersion            InstalledVersion
    LcsCDR                     39.82.2                    39.82.2
    QoEMetrics                 62.90.1                    62.90.1

  • Lync Server Front End 2 Hardware Load Balancer IP

    I currently have the following Setup.
    I only have 1 Hardware Load Balanced IP for my Front End Pool. 
    After running the Lync Planning Tool it actually states that i need 2 Hardware Load Balanced IP, 1 for internal and 1 for external. 
    My question would be would i be able to configure for mobility and external access with just using 1 Hardware Load Balanced IP? 
    Because i seem to have problem with connecting to the front end server based on the following scenario.
    Without Reverse Proxy Mapping (port 80/443 internet to port 80/443 reverse proxy to port 80/443 lyncpool frontend) 
    Internal Access (No Issue)
    Lync Mobile 2013 App (Can Connect and chat but intermittent connection) *gets disconnected if i access video/audio
    Lync Client 2013 Externally (Cannot Connect to Server) 
    https://meet.domain.com (working)
    With Reverse Proxy Mapping (Port 80/443 internet to port 8080/4443 reverse proxy to port 8080/4443 lyncpool frontend)
    Internal Access (No Issue)
    Lync Mobile 2013 App (Cannot connect)
    Lync Client 2013 Externally (Cannot connect)
    https://meet.domain.com (Not working)
    Would i actually need to have a additional front end pool IP for external access? or can i maintain it as it is? 
    I do not understand why without the mapping it can work whereas if i do the mapping according to technet article it won't work.
    Everything is running windows server 2012 R2 and Lync 2013, Loadbalancer / Reverse Proxy is the same F5 Appliance
    Any assistance on this is greatly appreciated.

    Hi Greg,
    I have been making use of it (https://testconnectivity.microsoft.com/) to test my autodiscover and remote
    access.
    Like i mentioned it is weird that without doing port mapping from 80/443 to 8080/4443 i was able to pass
    the autodiscovery and all but once i changed to the proper steps to do port mapping it stopped working. 
    and im not using TMG but using a F5 Hardware Reverse Proxy which also happen to be my Load Balancing Appliance. 
    Is there anyone who can help give me more details if i need 2 VIP for the front end ? 

  • Workflows not shown in the front end but exists in LDAP

    Hi
    In my OAM application, Workflows are not shown in the front end but exists in LDAP. Any idea how the workflows are displayed on the front end.
    due to this not there in production, when i tried to create a user, it says i donot have access rights.
    When i try to create and add workflows in the LDAP, the server rejects with the following error:
    Error adding object 'dn: obname=R20030715T164905882142,obpolicyContainerId=WorkflowDB, obcontainerId=Policies, o=Oblix,ou=oblixconfigentries,. The error sent by the server was 'Already exists':
    the entry is : last line shows obwfstatus as deleted ...
    dn: obwfinstanceid=7e872056d0ce012f0000BD537dc00000,obcontainerId=workflowInstances,o=Oblix,ou=oblixconfigentries, dc=axa,dc=co,dc=uk
    modifyTimestamp;adcsn-5038aa2900000001000f;vucsn-5038aa2900000001000f: 20120825103356Z
    modifiersName;adcsn-5038aa2900000001000e;vucsn-5038aa2900000001000e: uid=oblixadmin,ou=admins,dc=uk
    obwfstatus;adcsn-5038aa2900000001000d;vucsn-5038aa2900000001000d: 8
    obwfstatus;vdcsn-5038aa2900000001000d;deleted:

    Hi
    In my OAM application, Workflows are not shown in the front end but exists in LDAP. Any idea how the workflows are displayed on the front end.
    due to this not there in production, when i tried to create a user, it says i donot have access rights.
    When i try to create and add workflows in the LDAP, the server rejects with the following error:
    Error adding object 'dn: obname=R20030715T164905882142,obpolicyContainerId=WorkflowDB, obcontainerId=Policies, o=Oblix,ou=oblixconfigentries,. The error sent by the server was 'Already exists':
    the entry is : last line shows obwfstatus as deleted ...
    dn: obwfinstanceid=7e872056d0ce012f0000BD537dc00000,obcontainerId=workflowInstances,o=Oblix,ou=oblixconfigentries, dc=axa,dc=co,dc=uk
    modifyTimestamp;adcsn-5038aa2900000001000f;vucsn-5038aa2900000001000f: 20120825103356Z
    modifiersName;adcsn-5038aa2900000001000e;vucsn-5038aa2900000001000e: uid=oblixadmin,ou=admins,dc=uk
    obwfstatus;adcsn-5038aa2900000001000d;vucsn-5038aa2900000001000d: 8
    obwfstatus;vdcsn-5038aa2900000001000d;deleted:

Maybe you are looking for