Prev
Next
Forums S3 Systems Administration

Schema Error

Sort:
You are not authorized to post a reply.
Author
Messages
Jay Riddle
Veteran Member
Posts: 191
Veteran Member
4/3/2009 4:29 PM

    I am making a copy of a product line in order to bring up an old test environment.  I am running into a schema error.  I have the schema=dbo in the MICROSOFT file however for some reason it is picking up a schema we no longer have.

    Jimmy Chiu
    Veteran Member
    Posts: 641
    Veteran Member
    4/3/2009 9:27 PM
      the login you specified in your MICROSOFT file. Is it set up as "dbo" schema on your db server?
      Jay Riddle
      Veteran Member
      Posts: 191
      Veteran Member
      4/3/2009 9:37 PM
        Yes dbo is set as the default scheme. I can log into the database with the login and query the tables without having to put any schema in.
        Jimmy Chiu
        Veteran Member
        Posts: 641
        Veteran Member
        4/3/2009 10:21 PM
          You copying 9.0.x productline?

          Did you remove the plda.cfg/editdafile in your productline folder and rerun pldbsetup and editdafile?

          check your plda.cfg and see if it's pointing to the right database with correct info.

          also do a dbdef and check the dataspace with the new productline you trying to create.
          Jay Riddle
          Veteran Member
          Posts: 191
          Veteran Member
          4/6/2009 2:13 PM
            It is a LSF9 app 8.1.esp5 system. The only plda.* file is a plda.xml file under /gen/install.
            Jimmy Chiu
            Veteran Member
            Posts: 641
            Veteran Member
            4/6/2009 4:57 PM
              Are you using SQL Server? Check the login that lawson uses in MICROSOFT on SQL and see if it's defined as dbo as schema.
              Jay Riddle
              Veteran Member
              Posts: 191
              Veteran Member
              4/6/2009 5:16 PM
                Yes we are using SQL Server. The login is set to use dbo as the default login on the database. There has to be one other place it is set that I don't know about.
                Jimmy Chiu
                Veteran Member
                Posts: 641
                Veteran Member
                4/6/2009 6:53 PM
                  I would delete and recreate the login on your SQL server end and try it. Perhaps it's orphan user that's not linked.
                  Jay Riddle
                  Veteran Member
                  Posts: 191
                  Veteran Member
                  4/6/2009 8:40 PM
                    I just tried deleting and recreating the user and still no luck.
                    Jay Riddle
                    Veteran Member
                    Posts: 191
                    Veteran Member
                    4/7/2009 1:34 PM
                      Solved: My guess is that Lawson really cares about line endings in the MICROSOFT file. Lawson recommended I recreate the MICROSOFT file using wordpad. I just copied are dev MICROSOFT file and edited that with wordpad and it looks like it is now working.
                      John Henley
                      Posts: 3352
                      4/7/2009 2:39 PM
                        <HTML dir=ltr><HEAD></HEAD>
                        <BODY>
                        <DIV id=idOWAReplyText58789 dir=ltr>
                        <DIV dir=ltr><FONT face=Arial color=#000000 size=2>Wow, I had forgotten about that--I ran into that several years ago, and it stumped Lawson support for days.  As a result, I've trained my brain to either use lx from a LID session or DOS Edit (gasp!)....</FONT></DIV></DIV></BODY></HTML>
                        Thanks for using the LawsonGuru.com forums!
                        John
                        You are not authorized to post a reply.