Prev
Next
Forums User Experience Lawson Add-Ins for Microsoft Office

Webuser or Profile error

 7 Replies
 0 Subscribed to this topic
 1 Subscribed to this forum
Sort:
Author
Messages


J.Connelly











Basic Member



Posts: 5




Basic Member



12/3/2012 9:00 PM
    I've got a user in my office who is getting this error when trying to login to lawson addins in Excel:

    "WEBUSER OR PROFILE ERROR. Web User has been inactivated, please contact your administrator"

    The PC is using Windows XP and Office 2007

    This only occurs on ONE workstation, with ANY user account. When the same users try to login on another workstation, everything functions just fine. I'm currently working on getting a Fiddler log for the error, and will post it when I can.

    We've been running around with support for a couple weeks now, and haven't really made much progress. I was wondering if anyone has experienced this before, or might know a work around. Thanks in advance!


    John Henley














    Posts: 3353







    12/3/2012 9:50 PM
      My guess would be a browser configuration issue or missing MSXML patch.
      Try running servername.com/servlet/Profile on that workstation, and see what happens.
      Thanks for using the LawsonGuru.com forums!
      John


      J.Connelly











      Basic Member



      Posts: 5




      Basic Member



      12/7/2012 8:07 PM
        Sorry it took me so long to reply, my work email decided to filter my notifications.

        I ran through the Profile with Lawson support, who couldn't find anything out of place.
        I also had him take a look at the fiddler setup, and was unable to get it to monitor any traffic from the addin.

        I'm not super familiar with lawson, as it's mostly our finance and HR department who use it. Could you please elaborate a little on the browser config/MSXML patch? Is there a specific patch I'm looking for, or just a missed one in general?


        Aiz Javierto











        New Member



        Posts: 1




        New Member



        12/10/2012 6:32 AM
          newest version of Add-ins for Microsoft Office (10.0.2.0) limits the system support to Office 2010 and XP SP3.



          J.Connelly











          Basic Member



          Posts: 5




          Basic Member



          12/10/2012 5:09 PM
            We're currently running Ver. 9.0.3.1364 on XP SP3, if that makes a difference. Also, the issue occurs on both an XP machine and a Win7 machine


            JonA











            Veteran Member



            Posts: 1163




            Veteran Member



            12/24/2012 11:58 AM
              Just a thought... Since Addins recalls the server and user id when launched, have you verified that this user has the exact same information entered on both machines? Could they have had their id changed due to a name change and have that old id entered or perhaps the test server address entered on one machine? Sometimes we think technical and overlook the simple.
              Jon Athey - Sr. Supply Chain Analyst - Materials Management - MyMichigan Health


              J.Connelly











              Basic Member



              Posts: 5




              Basic Member



              1/14/2013 5:21 PM
                It's a little late, but holidays shut the office down for a bit.

                All the server information and login information is correct. The problem is that I recieve this error when ANYONE using ANY login tries to access addons via this computer.

                I have also since then installed 3 fresh win7 workstations that are now receiving the exact same error "WEBUSER or PROFILE error".

                I have done every bit of minor troubleshooting you can think of, and have noticed that Lawson isn't creating any registry entries for the addins. It is being installed from an admin account with full permissions.


                J.Connelly











                Basic Member



                Posts: 5




                Basic Member



                1/16/2013 8:58 PM
                  Update! Problem has been solved! We were experiencing issues with another one of our apps, which just happened to share the cause of this one.

                  Winhttp was causing the add-ins and other lawson apps to not connect to our server. Something to do with them being 32 bit apps running on a 64 bit OS, winhttp hadn't been configured to allow them through or something like that.

                  running a couple commands at a cmd prompt solved the issue.

                  Win7 machine:

                  Open cmd as administrator

                  cd c:\windows\syswow64
                  netsh
                  winhttp import proxy source=ie

                  That should solve the problem if anyone else experiences it!