Prev
Next
Forums Infor / Lawson Platforms S3 Security

Application Event ID 32770

 6 Replies
 0 Subscribed to this topic
 15 Subscribed to this forum
Sort:
Author
Messages
RogerThomas
New Member
Posts: 3
New Member
10/10/2008 6:04 PM
    We have lsf9.0.0 running and ready for our conversion fron 8.0.3.  We keep getting the following error messages in the Application log on the windows server:

    WIN32Error: controller.c(100): NT AUTHORITY\SYSTEM: java.exe: NetGetAnyDCName(WREC) - There are currently no logon servers available to service the logon request.

    And

    WIN32Error: controller.c(100): NT AUTHORITY\SYSTEM: jobrun.exe: NetGetAnyDCName(WREC) - There are currently no logon servers available to service the logon request.

    And

    WIN32Error: controller.c(100): NT AUTHORITY\SYSTEM: bldxffiles.exe: NetGetAnyDCName(WREC) - There are currently no logon servers available to service the logon request.

    Eveything works fine we are just want to know if this is something that needs to be corrected?

    Thanks for any help.
    John Henley
    Posts: 3353
    10/14/2008 12:09 AM
      What version of Windows are your running? That error usually indicates an issue contacting the domain controller. Do you have multiple domain controllers, and perhaps firewall between your Lawson server and any of the domain controllers? You should also check your Lawson server to make sure that DNS is set up correctly and that its not trying to use WINS.

      How is your local Lawson group defined? Does it include AD (or perhaps nested AD) groups, or are all users defined as local users on that server, etc.? How "far" is the Lawson server from the AD controller(s)?

      One issue I've come across recently is that Windows 2003 SP2 does something with Kerberos which causes lengthy discussions with the AD controllers when looking up job related records that require AD authentication, and tries to drop down into NTLM authentication instead of AD/Kerberos. For some reason the same issue doesn't occur in Portal (I'm assuming Portal does a better job of caching it than LID). Look in the event logs on your Lawson server and see if you have any other errors ... The "solution" was to define an 'SPN' in order to force Kerberos over NTLM. As always, I'm a little out of my element on this, but hopefully someone who understands this more than I do will chime in...
      Thanks for using the LawsonGuru.com forums!
      John
      RogerThomas
      New Member
      Posts: 3
      New Member
      10/14/2008 1:15 PM
        John,
        Ms Server 2003 Enterprise SP2.  I have two DC's (one 2000 that is is virtual server and a 2008 on a blade server)  In the network properties there are no entries for WINS.  Have have the DNS pointing to the 08 DC server and then the 00 DC server.  Yes I run DNS intergrated with AD.

        The Lawson User group containes the user names and has no nesting of OU's.  Both DC's sit in the same room and the 08 shares the same switch.

        I will look into the Service Principal Name (SNP)

        Thanks
         Roger
        KEVIN POINDEXTER
        New Member
        Posts: 3
        New Member
        10/28/2008 7:59 PM
          John,
          I work with Roger. I thought you would be humored to know that we had also opened up a case with Lawson on this issue and Lawson said;  "I googled your error and came up with this:  https://www.lawsonguru.co...33/Default.aspx#5133
          Take a look at it and see if what the responder is saying makes sense in your case."
          We were happy to tell Lawson that that was us!  Lawson's next response was to recommend Lawson Professional Services.  Case closed. I think you need to bill them. On a side note, many of our cases end with a PT being submitted. We love being beta testers for Lawson.
          John Henley
          Posts: 3353
          10/28/2008 8:10 PM
            That is hilarious, especially given the grief I get from Lawson.

            BTW, did you get this resolved?
            Thanks for using the LawsonGuru.com forums!
            John
            etu
            Veteran Member
            Posts: 50
            Veteran Member
            10/28/2008 8:34 PM
              CheeseCloth!
              RogerThomas
              New Member
              Posts: 3
              New Member
              10/28/2008 8:49 PM
                John,

                Yes we solved it but why is still up in the air.  We allpied some PT's then had to back them out.  We then restarted the servers and what do you know the errors no longer show up in the application log.    Why they stopped still remains the great mistry of Lawson.