Hi,
I try to go through the "Getting started Guide for new Developers".
I got stuck on page 63 with an attempt to start asbroker1.
I run this tutorial on Win7 with OpenEdge Developer Trial.
The error that pops up is:
com.openedge.pdt.explorer.model.ProgressExplorerException: Problem in OpendEdge Explorer: Broker resource.openedge.appserver.asbroker1 could not be started properly.
And the logs from console are:
Please let me know what might be the issue.
Thank you
The broker failed to start any agents, and gave up because the agents could not be connected to the database because the database isn't running.
Check the database .lg file and see why it could not be started.
This is the important bit:
** Error starting database server C:/Progress/OpenEdge/sports2000.db (-S 5555)
Thank you for a hint. Unfortunately, I can not find any .lg file in C:\OpenEdge or C:\Progress folders.
The message stats that "C:/Progress/OpenEdge/sports2000.db" could not be started. OpenEdge database puts its .lg file right next to the database so you're looking for C:/Progress/OpenEdge/sports2000.lg. Make sure you have that database created as well. I don't know what steps you are following so maybe you missed one, or there's a step missing?
If it isn't there, then you can create it using the following:
1. open a proenv shell. You can find the link in the windows start menu under the Progress group
2. cd to the correct directory. In this case c:\progrss\openedge
3. type: prodb sports2000
4. enter 'sports2000' when prompted to copy
5. then go back to PDSOE and restart the OpenEdge AVM (from project menu) and it should start the database for you.
Proenv helped me to solve the problem. Nonetheless, there seem to be some issues with sports2000.db in the default location (C:\progress\openedge). Short summary:
1. When I try to use C:\progress\openedge\sports2000.db from Developer Studio I get aforementioned exception. The DB file is present in C:\progress\openedge, but no *.lg is created.
2. When I cd C:\progress\openedge and run prodb sports2000, I get an exception, which seems what one would expect:
The procopy utility cannot copy the source database onto itself. (11024)
3. When I cd any other folder and run prodb sports2000 everything works fine, I get:
Database copied from C:\Progress\OpenEdge\sports2000. (1365)
Procopy session end. (334)
And also *.lg log file is being created.
Thank you
The copy of the sports2000.db in the OpenEdge Installation folder (aka DLC for historic reasons) is only meant to be used as a copy source (template) for new databases. You should always create a new DB using prodb, procopy or similar.
To say it stronger, never ever use one of the databases under DLC as an actual DB that you open. Copy it somewhere else.
I have OE v 11.3 installed in directory c:\oe (DLC=C:\oe).
I made few steps:
1. Create directory "db" on disc D:
d: <Enter>
md db <Enter>
2. Copy database soprts2000 from c:\oe to d:\db
copy c:\oe\sports2*.* d:\db
3. Create 2 batch files (start.bat and stop.bat) in directory d:\db (you may place it anywhere)
start.bat: - run server for sports2000 on port 1202 (or 5555)
----------------------------------------------------------------------
SET DLC=C:\oe
SET PATH=%DLC%;%DLC%\bin;%PATH%
call proserve d:\db\sports2000 -H localhost -S 1202
pause
----------------------------------------------------------------------
stop.bat: - run server for sports2000 on port 1202
----------------------------------------------------------------------
SET DLC=C:\oe
SET PATH=%DLC%;%DLC%\bin;%PATH%
call proshut d:\db\sports2000 -by
pause
----------------------------------------------------------------------
"pause" let you see messages form starting server.
Sorry for my English.
I would not recommend copying a DB using OS copy. In fact in most situations that creates a copy of the DB Header file (.db) that still referencse the other extends on the original Location.
Use procopy. Or prodb.
I would not recommend copying a DB using OS copy. In fact in most situations that creates a copy of the DB Header file (.db) that still referencse the other extends on the original Location.
Use procopy. Or prodb.