Error checking-in/creating module into new database

barry.marcus · Post by **barry.marcus** » Fri Jun 20, 2014 6:29 pm

This has actually turned out to be a MAJOR problem! Much in our code depends on the Default Database being set to a database other than the default set at installation. All of our sql statements (of which there hundreds, if not thousands) assume that the default database is something other than that. It would be a lot of work to change it. How do I create the SYSLIB table in our database????

barry.marcus · Post by **barry.marcus** » Sat Jun 21, 2014 11:25 am

Sorry... I just noticed the -libdb option for redirecting modules to another database. So I'm back again to feeling LESS anxious about this issue. Just the same, though, it'd be nice to find a resolution. Thanks.

Post by **Kai** » Mon Jun 23, 2014 10:16 am

This might be a file permission issue. Grant Everyone full control to your desired Default Database and everything in it, set it as the default in texis.ini, restart the monitor service, issue texis -wipelib, verify that SYSLIB.tbl and xslmr.btr exist in the (new) default database, and try to check in the module.

barry.marcus · Post by **barry.marcus** » Mon Jun 23, 2014 12:59 pm

That didn't seem to help. The error is still

000 ..\script\configuration: Index `xslmr' appears to be missing in D:\Crosshairs\database1

EVERYONE has FULL CONTROL in the directory where the database is located. There still is no table named SYSLIB in the catalog (i.e., in SYSTABLES) although there is a file named SYSLIB.tbl in the directory as before. I don't know if this is significant, but when I issue the command

monitor -d D:\Crosshairs\database1

or simply

monitor

I get the following:

Texis Monitor failed to start, exit code 37 (License violation or error)

I don't know if either of those are valid commands, since I always just let Texis restart the monitor after killing it.

Post by **Kai** » Mon Jun 23, 2014 1:45 pm

After [Texis] Default Database is set to D:\Crosshairs\database1, what happens and/or is printed when you issue texis -wipelib? Are there any errors in monitor.log?

barry.marcus · Post by **barry.marcus** » Mon Jun 23, 2014 3:42 pm

After monitor -k this is written to monitor.log

200 2014-06-23 15:36:40 (4108) Texis Monitor service status set to RUNNING
200 2014-06-23 15:36:40 (4108) Texis Monitor version 07.01.1393884148 starting as user SYSTEM
200 2014-06-23 15:36:40 (3720) Database Monitor on D:\Crosshairs\database1 starting as user SYSTEM
115 2014-06-23 15:36:40 (4108) Certificate `C:\MORPH3\conf\ssl\certs\licensemonitor.cert' for schedule/license server is a CA certificate (Basic Constraints: CA:TRUE): clients may expect a non-CA certificate in the function TXmonservSslUserPromptPrep
115 2014-06-23 15:36:40 (4108) License updates via applylicense may fail: [License Update] User `webinator' does not exist

After issuing texis -wipelib I see this message:

Library tables wiped in D:\Crosshairs\database1

After issuing monitor -d D:\Crosshairs\database1 this is written to monitor.log

200 2014-06-23 15:41:43 (2424) Texis Monitor version 07.01.1393884148 starting as user Barry
115 2014-06-23 15:41:43 (2424) Certificate `C:\MORPH3\conf\ssl\certs\licensemonitor.cert' for schedule/license server is a CA certificate (Basic Constraints: CA:TRUE): clients may expect a non-CA certificate in the function TXmonservSslUserPromptPrep
015 2014-06-23 15:41:43 (2424) Internal error: Client attempted re-init as server in the function TXlic_init
200 2014-06-23 15:41:43 (2424) Texis Monitor exiting with code 37 (License violation or error) due to error

Post by **Kai** » Mon Jun 23, 2014 5:02 pm

Don't run monitor -d; that may be implicitly starting the Texis monitor as an ordinary user, and it may not have certain perms it needs. Try restarting the Texis Monitor service (from Control Panel -> Services); that should run it with proper perms. Then re-issue texis -wipelib, and look at monitor.log, and for xslmr.btr in D:\Crosshairs\database1.

barry.marcus · Post by **barry.marcus** » Mon Jun 23, 2014 5:37 pm

OK. Did that. This was written to monitor.log when monitor was stopped:

200 2014-06-23 17:27:34 (4108) Received Windows service control message STOP, replied with status STOP_PENDING
200 2014-06-23 17:27:36 (4108) Texis Monitor service status set to STOPPED
200 2014-06-23 17:27:36 (4108) Texis Monitor exiting: Received Windows service control message STOP
200 2014-06-23 17:27:36 (3720) Database Monitor on D:\Crosshairs\database1 exiting: Monitor stop event signalled

This was written to monitor.log when monitor was started from the Services screen under Administrative Tools:

200 2014-06-23 17:28:36 (3808) Texis Monitor service status set to RUNNING
200 2014-06-23 17:28:36 (3808) Texis Monitor version 07.01.1393884148 starting as user SYSTEM
200 2014-06-23 17:28:36 (4364) Database Monitor on D:\Crosshairs\database1 starting as user SYSTEM
115 2014-06-23 17:28:36 (3808) Certificate `C:\MORPH3\conf\ssl\certs\licensemonitor.cert' for schedule/license server is a CA certificate (Basic Constraints: CA:TRUE): clients may expect a non-CA certificate in the function TXmonservSslUserPromptPrep
115 2014-06-23 17:28:36 (3808) License updates via applylicense may fail: [License Update] User `webinator' does not exist

Same message when texis -wipelib was issued and same message when texis -CI <filename> was issued. There is no xslmr.btr in the directory.

User SYSTEM seems to have full control permissions in D:\Crosshairs\database1.

barry.marcus · Post by **barry.marcus** » Mon Jun 23, 2014 5:41 pm

What is the implication that user 'webinator' does not exist? Should it exist? If so, can I just create it?

Post by **Kai** » Mon Jun 23, 2014 6:03 pm

The `webinator' user being referred to is a Texis user in the default database, not a system/OS/Windows user. In this case it would need to exist (and have a password) in order to authenticate license updates via the GUI; lack of it only prevents that, so don't worry about it.

What happens if you do texis -libdb D:\Crosshairs\database1 -wipelib?