View Full Version: Tf80sqv.sql Errors

LawsonTalk > HR/Payroll > Tf80sqv.sql Errors



Title: Tf80sqv.sql Errors


trezaei - January 22, 2008 12:35 AM (GMT)
Following directions from BSI to insatll the TF80 database. I have created a separate databse called TF80 on the Lawson server.
When I run the tf80sqv.sql I get errors saying:


The specified schema name "TF80" either does not exist or you do not have permission to use it.

I have created a user called TF80 and have given it full permissions to that database.


any ideas? my brain is dead.

trezaei - January 22, 2008 12:36 AM (GMT)
I won't paste the whole script but this much will suffice, it produces the error show above,'

CODE
CREATE TABLE TF80.BTXDSET (
  DATASET          CHAR(25)          NOT NULL,
  PRIMARY KEY (
     DATASET
  ),
  DESCRIPT         VARCHAR(100)      NOT NULL,
  TFUSER           VARCHAR(50)       NOT NULL,
  TFPASS           CHAR(40)          NOT NULL
)
GO

trezaei - January 22, 2008 03:23 AM (GMT)
Okay, nevermind, I got it working. Turns out in SQL2005 you have to assign a schema explicitly to the user otherwise it doesn't what you're talking about when you name the schema on create statements. Whatever it'd done!

I am finally done with the Tax Factory 8 install.
It was tough only because we were:

1) Windows server with no maintenance since Aug 2004
2) Expired support from BSI which took 3 weeks to resolve
3) Had to upgrade env to ESP 7
4) No MSPs were applied to had to get that up to MSP 11
5) Had to apply about a dozen CTPs
6) Had the above issue with Database (minor compared to the rest)
7) Working on an extremely slow server.

All combined to make it one heck of an upgrade project that had to be done in 3 days. I am not even sure it's over yet. Could be a while longer if they discover something.

Thanks all for your help on this and other threads the past few weeks.

Cindy - January 24, 2008 04:44 PM (GMT)
Holy CRAP! And I thought mine was bad.

Congratulations...I know the sense of relief you must be feeling. :-) We had only a couple of aftershocks...nothing major though. Since we only applied what had been tested in our DEV/TEST system (which was back in Aug) we had to apply a couple of portal patches that had been issued since then. Good luck!




Hosted for free by InvisionFree