ADS Client Server (SAP)

[omni]

Roger,

Unsure on recommending how to set up for this. Moving a client to ADS.

Our client currently has a data server and a remote server. The exe and dll files are on the remote server for speed loading purposes with the current set up. All data files on the data server. All users are on the remote server, around 100.

Does the ADS still install on the data server and should the exe stay on the remote server, or should the ads be loaded on the remote serve?
Or, does the exe and dll files have to be moved back to the data server.

I would guess others have similar set up.

thanks

Fred
Omni

[rdonnay]

Does the ADS still install on the data server and should the exe stay on the remote server, or should the ads be loaded on the remote server?

YES. You should install Advantage Server on the same machine as your data files.

[omni]

How will our exe on the remote server be able to load ADS on the local drive when ADS is installed on the data server. Not sure how it will see it. They installed it today on the server c-drive (default settings) , which is not available from the remote server. Should it be installed on the shared drive? Just wondering if there is a specific method to load in this situation.

Thanks

[rdonnay]

The application code connects to the ADS server through a DacSession().

I already wrote that for you and we tested it.

What do you think is different than what we already tested?

[omni]

Just that our app is on one server and the ads on another server. I may be concerned about nothing. Suppose if its running as a service it does not have to be loaded in a certain path like normal programs.

Fred

[rdonnay]

Yes, you should not be concerned.

Feel free to call or Skype me if you have problems with the installation.

[omni]

dbesys will not start a session from the other drive. Finds everything, no errors, and I added alerts every few lines to watch it.

FUNCTION LoadAds( cExt, lCompatibleLocking )

LOCAL lAdsCompatible, cAdsServer, cSession, oAdsSession, cError

DEFAULT lCompatibleLocking TO .T.
DEFAULT cExt TO 'CDX'

IF !"ADSDBE" $ DbeList()
IF ! DbeLoad( "ADSDBE" )
Alert( "Unable to load ADSDBE", "ADS Server")
RETURN .f.
ENDIF
ENDIF

cAdsServer := "z:\oiswin\"

cSession := "DBE=ADSDBE;SERVER=" + cAdsServer
oAdsSession := DacSession():new(cSession)


IF !oAdsSession:isConnected()
cError := "Error Code: " + Alltrim(Str(oAdsSession:getLastError())) + ;
Chr(13) + oAdsSession:getLastMessage()
Alert( "Unable to establish connection to ADS Server" + Chr(13) + cError, 'ADS Server' )
RETURN .f.
ENDIF


Errors out on the alert line. So may be an issue on that line.
Wonder if there is a setting that allows the app to run from a different drive location than the dbf files.

We had to change curdrive() to z:, and that works when running from the server. But will not work when running from the remote server.

The ADS server cfg shows a connection, but will not start the session. Even after the fatal error the connection still shows active.

Is it possible that the ads needs to be installed in the shared folder on the data server so that the remote server has access to it? The remote server does not have access to any path on that server except our shared OMNI folder

Any thoughts?


Fred

[rdonnay]

Do you have Teamviewer?

I want to see what you are doing.

[omni]

Yes, the error is (7041) file not found on the session starting. I am leaving in 45 minutes, but I can show you quickly, or we can do it later. Up to your schedule.

I can send you connection info for teamviewer on an email.

[rdonnay]

I will be gone tomorrow and over the weekend.
I will be here all day today.

Call me at your convenience.