Hi All,

I am trying to connect two application servers with one database server with two separate databases. I have moved existing BSE to new server and did necessory steps related to 3 tier structure. In fact, installation almost completed without problems. And I am able to run reports on new server.

During installation, I have choosen "User Interface and application logic" option and entered database node name after confirming BaaN Support. Now I am not able to open my scripts because it is pointing to database server instead of BaaN application server, also I am not able to copy menu, etc. screen-shot attached herewith. I think, I should enter application node name instead of database node name.

My queries are - How to change node name without reinstalling BaaN? or What node name should be there? or Is this different kind of problem rather than node name?

Regards,

-Suhas

Yeah,

After removing BSE_REM (BSE Remote) entry from registry, problem solved.

Regards,

-Suhas:cool:

HI! im doing .. i have the same problem. but i dont understand what is this variable BSE_REM, i only have BSE and BSE_temp (environment /Baan NT Manager) both servers.
the other problem is when im creating a new user .Maintain DB user tdba0115m000) .attached image..

Server a) SQL-Baan
Server b) Only Baan

Based on Tools reference Document TFH-006 i used Method 3 - ODBC.

Can you help me please.

Hi,

Probably it is problem of old master media. You have to open registery by regedit and remove that entry by finiding.

I think the second problem related to your DB MSSQL.

regards,

-Suhas

Vec
BSE_REM gets created in the Environment variables when you install "User Interface and application logic" from Baan Cd. It could be what Suhas as mentioned, old media CDs..

I used the same steps in that document you mentioned and i got through with the user creation and all. Just stuck with login issues with the users created. Did you carry out any extra steps than whats mentioned in the document? Is the user you are trying to create, exists in the OS level of ServerA?

sk

sukesh-suhas:
BSE_REM : according to doc. i removed this varibale from baan nt and i don't know what is the register (by regedit) i can't find

MSSQL: I dont have any problem with save-delete-etc. on DB, the system is looking in the right place (server 2 bd), but what is the difference with a creation of user?? the user is created in server 1 and server 2 (OS).

is necesary to modify anything in the session ttaad4100m000? maybe the name system (now is blank)

how can i know if the baan media is the same? server 1 and server 2(new app)


thanks!!!!
Vec

Hi,
First of all, its highly unlikely to find the BSE_REM variable in the System Registry(App Server) once you deleted it from the environment variable.
You can find the variable in the registry in the following path
HKEY_LOCAL_MACHINE=>Software=>Baan=><BSE>
or
HKEY_LOCAL_MACHINE=>Software=>Baan=><BSE>=>Environment
...where <BSE> is your baan environment name given at installation time.

As a further step, you can install SQL Client tools and try to connect to the database server from your APP server using the Query analyzer. If you are able to connect then the connection seems to be ok.
Did you by any chance create an entry in the session "Maintain Systems"?
Last but not least it would be better if you could post here the tabledef6.1 file of the APP server and how your Maintain Database Definition session looks like...


sk

Sukesh:
Hi,
1- The Sql Client is OK! i can connect with DB remote
2- Maintain Systems , i've tested with and without system name.
a) with system name , a message that is not possible to open the file. (when im creating a user).
message: (i cant open file '<REMOTE_SERVER!d:\baan/tmp', error 0 )
b) without system name, other message when i input the password for SA.
message :Connect Error 0 from 'Microsoft SQL-DMO(ODBC SQLstate:08001) as 'sa' to server '(local)' .....

here my tafledef6.1, that i had to change according other posts.. looks like:
-----------------------------------------------------------------------
tuxch001:*:msql7(MSQL_LEVEL1=1,MSQL_DSN:<ODBC_NAME>):Y
tuxch009:*:msql7(MSQL_LEVEL1=1,MSQL_DSN:<ODBC_NAME>:Y
.....
......
*:*:msql7(MSQL_LEVEL1=1,MSQL_DSN:<ODBC_NAME>):N (last Line)
--------------------------------------------------------------------------
if i convert DD, the system modify this file, like original (without MSQL_Level1, msql:...etc.) and i can not access. Then i have to restore this file from a copy.


Thanks
Vec

Hi Vec,
Reading through part of your post made me feel like reading my case on Infor support. The only exception is that you are a step behind me. I am able to create users without any problem. Logging them to baan is my problem. The Maintain System related error, even i am getting the same and so i did without the System defined. Convert to DD should be run only from the DB server as if you run from the APP you will mess tabledef6.1 as you have found out. After running the CRDD you should copy the tabledef6.1 from DB to App server. This is better than manually rectifying the tabledef6.1 on APP.

Another exception is your tabledef6.1. Mine goes like this
cpcpm000:*:msql7(MSQL_LEVEL1=1,MSQL_SERVERHOST:<DbServerName>):Y ---First Line
...
*:*:msql7(MSQL_LEVEL1=1,MSQL_SERVERHOST:.):N --- Last Line

Although i am using ODBC connection i have entered the DB servername in both my Database Definition and subsequently in my tabledef6.1

try it out and let me know if it changes your situation...

sk

Sukesh:
The same problem! can you send me a screenshot of your maintain system session ttaad0150m000 ?, i imagine that is a permission problem (i dont know). I 've tested with Baan user only and is working. with other users doesn't work. :-(
i need to solve this situation during this week.....and tell to my boss if its possible or not.


Tks!!!!!

Hi,
Although i havent maintained any system, it somehow works for the user Baan and not for the other users. You can find the screenshot of the Maintain Database Defintion with this post where the name "dtbserver" is the name of the database server. I might have got a fix from Baan support, just have to test it out and see if it really fixes this problem, as they say it would.

sk

it somehow works for the user Baan and not for the other users
Read this thread:

[URL=http://www.baanboard.com/baanboard/showthread.php?t=24626&highlight=administrator+group[/URL]

Thanks for the link. Unfortunately for me, even adding the user to the Administrator Group doesnt resolve the "Database Not On" error. The only difference between the user Baan and the test user is their name. All the permissions are identical. Both on and off Baan.
The link is based on a two-tier installation and so i doubt the effectiveness of the solution on a three-tier setup.

Wot say?
sk

It was down to a simple re-adjustment of a setting described in the TFH-006 document about the ODBC Driver setup that made it work. In the document, it shows that the ODBC driver to be created under the User DSN tab, but it should have been System DSN. Once this was done, other users were able to log in without problems. No more "Database Not On" errors.

sk