Hi,
I have tried to migrate V8i project to CONNECT Edition (new try).
In the project, macro to define MS_GEOINITCMD variable is used:
In V8i it works fine, database is connected using UDL connection automatically when the project is opened. In BM CE U2, nothing happens.
When I removed the definition and enter the key-ins manually, the database is connected properly, so it seems the problem is in the variable functionality, not in the key-in.
With regards,
Jan
Hi Jan
I took a look at this in Map CE and I see MS_GEOINITCMD working. I set MS_GEOINITCMD as so:
mdl load dbconmgr; dbconmgr oledb $(MS_GEOWSHOME)/mytown_geosql14.udl
And then placed my UDL file in that directory, which on my machine is:
D:\Map Enterprise CONNECT\Configuration\WorkSpaces\mytown_sql_oledb\WorkSets\ws
I think maybe you have an extra $ in your MS_GEOINITCMD value?
Also, when you added the database to your schema, it should have added some connection variables including MS_GEOINITCMD to the Macros section. In my case, after adding this db to my schema, MS_GEOINITCMD was set by Map to:
db=D:\Map Enterprise CONNECT\Configuration\WorkSpaces\mytown_sql_oledb\WorkSets\ws\mytown_geosql14.udl
If the problem persists you could try setting MS_SESSION_DEBUG = 1. This will startup the db debugger and perhaps provide some insight into an unsuccessful 'auto connection'.
HTH
Mark
Hi Mark,
thanks for your comments, I will check $ in the key-in.
From my perspective it does now work simply because it worked in V8i and without any change in the project, it does not work in BM CE U2. I am aware a functionality can change between versions, but in such case it has to be documented or software has notify the user that "the old way does not work". Moreover, the key-in works fine when used after the project is opened and not as a part of the configuration variable.
I already created msdebug.txt to analyze how the variable is constructed and there are several issues, generated directly by GSA and BM config files (the same problem as in your example: a backslash after variable pointing to folder is useless and leads to multiple slashes, but Windows file system is tolerant to this mistake), but to use session debug is for sure good idea.
Bentley Accredited Developer: iTwin Platform - AssociateLabyrinth Technology | dev.notes() | cad.point
I understand that your main point here is that when you migrate from V8i to CONNECT the software should just work, notify the user, or be documented. But for the problem itself, I wonder if perhaps this connection issue is caused by our changes with workspaces and worksets?
The variable MS_GEOWSHOME points to a different directory in v8i versus CONNECT. So maybe the UDL is just not being found in CONNECT due to the software now looking in the Worksets directory?
Do you see any error when starting Map?
Unknown Keyin or Command would mean there is a problem with commands in MS_GEOINITCMD
Unsuccessful Connect Statement would mean that Map is not finding the UDL file or that the UDL itself is incorrect
Here are some informational links on the new CONNECT configuration changes. (more for the benefit of others reading this post, I know you are very familiar with MicroStation configurations)
What configuration changes have been made in MicroStation CONNECT Edition?
Considering Migrating to MicroStation CONNECT Edition?
Workspace location V8i compared to CONNECT Edition