Progress 9.1B and Takestock

[drdanskin]

I’ve been commissioned to move a progress database of an old NT4.0 server and onto a SBS2003. I am having very little luck. I have the progress install ok (I think) and the data base copied over but when I try to start the applications startup batch file I get the following

E:\db>rem *****************************************************************

E:\db>rem * Windows NT Batch file for starting TakeStock servers. *

E:\db>rem *****************************************************************

E:\db>set DLC=D:\dlc91bdb

E:\db>set DATADIR=E:\db

E:\db>set SERVID=domdb

E:\db>set ODBCID=OIB

E:\db>set username=Administrator

E:\db>rem NOTE: -B startup parameter is in database blocksize (usually 8K on new
installs, so 6000 = 48 meg)

E:\db>rem NOTE: -n parameter is maximum connections, usually 2 times the number
of users

E:\db>rem NOTE: change -spin value to 8000 if multiple CPUs on the database serv
er

E:\db>rem NOTE: change -Mn (number of server processes) to value of -n divided b
y

E:\db>rem value of -Ma (number of users/server)

E:\db>D:\dlc91bdb\bin\_mprosrv.exe -db E:\db\domdata.db -S sqldb -N TCP -B 50000
-n 210 -Ma 8 -Mn 36 -bibufs 60 -aibufs 40 -L 20000 -spin 14000 -Mi 4 -Mpb 10
13:25:35 SERVER : Personal DB server cannot support more than 5 users. (9234)
13:25:35 SERVER : Number of users (-n) adjusted to 5. (5055)
13:25:35 SERVER : This version of PROGRESS does not support Spin Lock Retries
(-spin). (4965)
13:25:35 BROKER : This broker will terminate when session ends. (5405)
13:25:35 SERVER : Personal DB server cannot support more than 5 users. (9234)
13:25:35 SERVER : Number of users (-n) adjusted to 5. (5055)
13:25:35 SERVER : This version of PROGRESS does not support Spin Lock Retries
(-spin). (4965)
13:25:41 BROKER 0: Multi-user session begin. (333)
13:25:42 BROKER 0: Begin Physical Redo Phase at 640 . (5326)
13:25:47 BROKER 0: Physical Redo Phase Completed at blk 725 off 212 upd 0. (716
1)
13:25:48 BROKER 0: This server is licensed for local logins only. (4393)
13:25:48 BROKER 0: Unable to find server sqldb with protocol TCP in file SERVIC
ES or SERVICES file not found in expected location. (5192)
13:25:48 BROKER 0: Begin normal shutdown (2248)
13:25:50 BROKER : Multi-user session end. (334)
13:25:50 BROKER : ** This process terminated with exit code 1. (8619)

E:\db>D:\dlc91bdb\bin\_mprosrv.exe -db E:\db\domdata.db -S domdb -N TCP -m3 -Mpb
25 -Mi 4 -Ma 8
13:25:50 SERVER : This broker will terminate when session ends. (5405)
13:25:50 SERVER : There is no server for database E:\db\domdata. (1423)
13:25:50 SERVER : ** This process terminated with exit code 1. (8619)

E:\db>rem these lines start the page writers

E:\db>call D:\dlc91bdb\bin\proapw domdata
Starting background Async Page Writer for domdata
PROGRESS PATCH Version 9.1B25 as of July 09, 2001
13:25:50 APW There is no server for database domdata. (1423)
13:25:50 APW ** This process terminated with exit code 1. (8619)

Starting background Async Page Writer for domdata
PROGRESS PATCH Version 9.1B25 as of July 09, 2001
13:25:50 APW There is no server for database domdata. (1423)
13:25:50 APW ** This process terminated with exit code 1. (8619)

Starting background Before Image Writer for domdata
PROGRESS PATCH Version 9.1B25 as of July 09, 2001
13:25:50 BIW There is no server for database domdata. (1423)
13:25:50 BIW ** This process terminated with exit code 1. (8619)

Starting background After Image Writer for domdata
PROGRESS PATCH Version 9.1B25 as of July 09, 2001
13:25:51 AIW There is no server for database domdata. (1423)
13:25:51 AIW ** This process terminated with exit code 1. (8619)

Press any key to continue . . .

Can anyone assist? I think it maybe an ODBC issue but I am not sure
dtomkinson@verizon.net

 

[Casper]

I have the progress install ok (I think)

I guess not looking at the the startup command:

E:\db>D:\dlc91bdb\bin\_mprosrv.exe -db E:\db\domdata.db -S sqldb -N TCP -B 50000
-n 210 -Ma 8 -Mn 36 -bibufs 60 -aibufs 40 -L 20000 -spin 14000 -Mi 4 -Mpb 10

and this entry in the log file:

Personal DB server cannot support more than 5 users. (9234)

You got personal DB license installed. Not an enterprise license like you seem to expect.

What license type did you install?
Could it be there is an other Progress install on the same machine?

Casper

 

[drdanskin]

i'm sorry but i dont understand the question about license type. i used the license i read from the current server in the progress.cfg file. it came up as enterprise db. i do not have the orginal progress cd. i had to find one from a local software developer. i only asked him if he had progress 9.1b. so if there are different install type depending on the cd i can see that i might have some issues.
there was other install since i have tried differnt versions, but on this latest attempt, i have wiped out everything and reloaded a clean OS and started from scratch.
thanks for your assistance.

 

[Casper]

The log file says clearly personal DB and not Enterprise RDBMS.

You can see the license in your progress install:
Start > programs > Progress > Config

or cmd: /installdir/bin/showcfg

If this is correct (e.g. Enterprise RDBMS) then something else is wrong.
Since you made a clean OS install I can't imagine at the moment what this could be.
Otherwise it could have been there is still an OS environment variable (PROCFG) pointing to the wrong CFG.

Changing OS is also a good time to change Progress version. You should be at least on 9.1E04.

Casper

 

[drdanskin]

the config does not say anything about the DB (see below). but during the install it accepts the codes and lists enterprise db.

Configuration File: d:\dlc91bdb\PROGRESS.CFG
Company Name: Electrolab
Product Name: 4GL Development
Installation Date: Thu Sep 27 12:42:10 2001
User Limit: 499
Expiration Date: None
Serial Number: 00298XXXX
Control Numbers: XXXXX - XXXXX - XXXXX
Version Number: 9.1B
Machine Class: KB
Port Number: 31
Product Name: Client Networking
Installation Date: Thu Sep 27 12:42:10 2001
User Limit: 499
Expiration Date: None
Serial Number: 00298XXXX
Control Numbers: XXXXX - XXXXX - XXXXX
Version Number: 9.1B
Machine Class: KB
Port Number: 31
Product Name: Query/RESULTS
Installation Date: Thu Sep 27 12:42:10 2001
User Limit: 499
Expiration Date: None
Serial Number: 00298XXXX
Control Numbers: XXXXX - XXXXX - XXXXX
Version Number: 9.1B
Machine Class: KB
Port Number: 31

 

[Casper]

Well your config file does say something of the products installed namely:

Product Name: 4GL Development
Product Name: Client Networking
Product Name: Query/RESULTS

so no Enterprise RDBMS installed. This is development install.

4GL development only has personal DB to work with. So you need to find the registration number for Enterprise DB and if you don't develop on the machine (which you shouldn't if it is production) then you can skip at least the 4GL development license.

Casper.

 

[drdanskin]

i did all four and i am now reinstalling with just the enterprise.
during the reinstall i received the following error
updatemscfile waring
unable to update proexp.mcs for use with current MMC version
i selected ok and it continued

 

[drdanskin]

after the reinstall i do have the ent.db in the config. but i am still getting an error about unable to find the sqldb

 

[Casper]

could you post the logfile you are getting now?
Do you start the database with proserve?

Casper

 

[drdanskin]

i hope this is what you mean.
i start the services with this batch file

E:\db>rem *****************************************************************
E:\db>rem * Windows NT Batch file for starting TakeStock servers. *
E:\db>rem *****************************************************************
E:\db>set DLC=D:\dlc91bdb
E:\db>set DATADIR=E:\db
E:\db>set SERVID=domdb
E:\db>set ODBCID=OIB
E:\db>set username=Administrator
E:\db>rem NOTE: -B startup parameter is in database blocksize (usually 8K on new
installs, so 6000 = 48 meg)
E:\db>rem NOTE: -n parameter is maximum connections, usually 2 times the number
of users
E:\db>rem NOTE: change -spin value to 8000 if multiple CPUs on the database serv
er
E:\db>rem NOTE: change -Mn (number of server processes) to value of -n divided b
y
E:\db>rem value of -Ma (number of users/server)
E:\db>D:\dlc91bdb\bin\_mprosrv.exe -db E:\db\domdata.db -S sqldb -N TCP -B 50000
-n 210 -Ma 8 -Mn 36 -bibufs 60 -aibufs 40 -L 20000 -spin 14000 -Mi 4 -Mpb 10
16:38:33 BROKER : This broker will terminate when session ends. (5405)
16:38:38 BROKER 0: Multi-user session begin. (333)
16:38:38 BROKER 0: Begin Physical Redo Phase at 640 . (5326)
16:38:43 BROKER 0: Physical Redo Phase Completed at blk 725 off 212 upd 0. (716
1)
16:38:44 BROKER 0: Unable to find server sqldb with protocol TCP in file SERVIC
ES or SERVICES file not found in expected location. (5192)
16:38:44 BROKER 0: Begin normal shutdown (2248)
16:38:47 BROKER : Multi-user session end. (334)
16:38:47 BROKER : ** This process terminated with exit code 1. (8619)
E:\db>D:\dlc91bdb\bin\_mprosrv.exe -db E:\db\domdata.db -S domdb -N TCP -m3 -Mpb
25 -Mi 4 -Ma 8
16:38:47 SERVER : This broker will terminate when session ends. (5405)
16:38:48 SERVER : There is no server for database E:\db\domdata. (1423)
16:38:48 SERVER : ** This process terminated with exit code 1. (8619)
E:\db>rem these lines start the page writers
E:\db>call D:\dlc91bdb\bin\proapw domdata
Starting background Async Page Writer for domdata
PROGRESS PATCH Version 9.1B25 as of July 09, 2001
16:38:48 APW There is no server for database domdata. (1423)
16:38:48 APW ** This process terminated with exit code 1. (8619)
Starting background Async Page Writer for domdata
PROGRESS PATCH Version 9.1B25 as of July 09, 2001
16:38:48 APW There is no server for database domdata. (1423)
16:38:48 APW ** This process terminated with exit code 1. (8619)
Starting background Before Image Writer for domdata
PROGRESS PATCH Version 9.1B25 as of July 09, 2001
16:38:48 BIW There is no server for database domdata. (1423)
16:38:48 BIW ** This process terminated with exit code 1. (8619)
Starting background After Image Writer for domdata
PROGRESS PATCH Version 9.1B25 as of July 09, 2001
16:38:48 AIW There is no server for database domdata. (1423)
16:38:48 AIW ** This process terminated with exit code 1. (8619)
Press any key to continue . . .

 

[Casper]

Ok, we are getting somewhere.

The error is what it says. the services sqldb cannot be found in the services file with rptocol TCP.

So look in WINDOWSINSTALLDIR/system32/drivers/etc inhere there should be a file named services with the service sqldb in it with a portnumber. Something like:
sqldb 3500/tcp
sqldb 3500/udp

Casper

 

[drdanskin]

there is not sqldb reference in the services file on this machine, but there is on on the current production server. now that the current enterprise db is showing up. i am reinstalling the application to see if that has any effect. fyi, the progess.cfg on the current server also does not reference an enterprise db

 

[Casper]

Well, then it was on the old server also imposible to start without warnings because of the use of -spin and -n 210.
(you get warnings: 5055, 4965 and 4393).

you need to put all the servicenames in the services file or reference them directly with portnumber.

Considering the way you started the database I assumed we are dealing here with a production database.
But this proofs to be misleading sometimes
(I should have known that starting a database with -n 210 on a windows server isn't very realistic, though very optimistic).

Casper.

 

[drdanskin]

once again thank you so much for your assistance in this matter (i am a strong believer in show apprecation). we are using the commands from a production database but on a temp. server. i will conncat to the production server and add the commands to the services file as they are on that server and let you know the results.
thank you

 

[drdanskin]

rebooting now. i will let you know the results
thanks

 

[drdanskin]

thanks for your assistance. i have it almost complete because of your comment on the missing ent. db and the query module. i now have one error left that i am not sure how to address (see below). any assistance would be greatly appreciated
its the last line
E:\DB>D:\dlc91bdb\bin\_mprosrv.exe -db E:\db\domdata.db -S sqldb -N TCP -B 50000
-n 210 -Ma 8 -Mn 36 -bibufs 60 -aibufs 40 -L 20000 -spin 14000 -Mi 4 -Mpb 10
10:54:16 BROKER : This broker will terminate when session ends. (5405)
10:54:21 BROKER 0: Multi-user session begin. (333)
10:54:21 BROKER 0: Begin Physical Redo Phase at 640 . (5326)
10:54:26 BROKER 0: Physical Redo Phase Completed at blk 729 off 2167 upd 0. (71
61)
10:54:26 BROKER 0: Started for sqldb using TCP, pid 2540. (5644)
E:\DB>D:\dlc91bdb\bin\_mprosrv.exe -db E:\db\domdata.db -S domdb -N TCP -m3 -Mpb
25 -Mi 4 -Ma 8
10:54:27 SERVER : This broker will terminate when session ends. (5405)
10:54:27 BROKER 1: Started for domdb using TCP, pid 2740. (5644)
10:54:27 BROKER 1: This is an additional broker for this protocol. (5645)
10:54:27 BROKER 1: This broker supports both 4GL and SQL server groups. (8865)
E:\DB>rem these lines start the page writers
E:\DB>call D:\dlc91bdb\bin\proapw domdata
Starting background Async Page Writer for domdata
PROGRESS PATCH Version 9.1B25 as of July 09, 2001
Starting background Async Page Writer for domdata
PROGRESS PATCH Version 9.1B25 as of July 09, 2001
Starting background Before Image Writer for domdata
PROGRESS PATCH Version 9.1B25 as of July 09, 2001
Starting background After Image Writer for domdata
PROGRESS PATCH Version 9.1B25 as of July 09, 2001
10:54:27 AIW 40: After-imaging is not enabled. (2514)
10:54:27 AIW ** This process terminated with exit code 1. (8619)

 

[Casper]

Well, things changed a bit knowing that this is a development environment....
The error comes from the fact that you try to start an after image writer, but that isn't possible since you don't have after image enabled.
You can do 2 things to prevent this error:

1. since this a development environment and the data is easily recovered from the production environment: don't start the aiw and you wont have the error.
2. If you do want to start the aiw then you have to enable after image first. (after restore: rfutil /pathtodatabase/databasname -C aimage begin).

HTH,

Casper.

 

[drdanskin]

this is a test run to make sure we can have this application move to a new server running sbs2003 from nt4.0 so we want the server to act like a production environment. is the command you gave me for unix?

 

[Casper]

No, rfutil works on windows as well.

Casper.

BTW Did I already mention that this is a good time to upgrade to at least 9.1E :awink: (9.1b still has lots of issues compared to 9.1E..)

 

[drdanskin]

ok, so the big question is what is after image, do i need it to work?
there is a rfutil.bat file in the bin directory that has the following
@echo off
if "%DLC%"=="" set DLC=d:\dlc91bdb
type "%DLC%"\version
"%DLC%\bin\_rfutil" %1 %2 %3 %4 %5 %6 %7 %8 %9
pause
it comes back and tells me i must supply a database name

there is an ai direct that has a file called domdata.ai

i have tried the following commands in the db directory and come up with these results
E:\db>rfutil e:\db\domdata -C aiw
PROGRESS PATCH Version 9.1B25 as of July 09, 2001
Could not recognize: -C aiw. (348)
E:\db>rfutil e:\db\domdata -C h:\ai\domdata.ai
PROGRESS PATCH Version 9.1B25 as of July 09, 2001
Could not recognize: -C h:\ai\domdata.ai. (348)