Extremely slow connecting to database

[Maggied]

Hi,
We have TS 2012 r2 running sage 300. When you select your company to login it takes over 40 secs to connect. When you are finally in the database it runs fast. Then when you logout of the company it takes over 40 secs. We have 32 gigs of ram on ts and on the SQL Server. The sql is 2008. I hope anyone has any ideas of why it is slow just logging and out of the databases.
Thanks

 

[Jay Converse]

Assuming you have good speed from the TS to the SQL server, like 1 Gpbs or better, then check the PATH for a non-existent server.

 

[Maggied]

We have 1 Gpbs. When you say paths.... what paths am I looking for?

 

[DjangMan]

32GB of RAM on the SQL server doesn't guarantee instant access. You could also see what kind of memory usage is happening on that server.

For the paths - one place to look is to open a command prompt and then type PATH<enter> and examine what you're seeing there.

 

[Maggied]

Thanks for replying... I did the path and everything seems fine there. The SQL has 24 gigs dedicated to the databases. Its weird because it is super fast once you are logged into the company its just slow connecting and disconnecting from the company.

 

[ettienne]

Administrative Services, Customization Directories - check that all Directories are valid. Invalid paths here slow things down drastically.

Sage 300 ERP Certified Consultant

http://www.adssglobal.net

 

[Maggied]

Yes I checked there and nothing is there. Could the Org.isam file be corrupt?

 

[ettienne]

Run SCANISAM to check Orgs.ism

Sage 300 ERP Certified Consultant

http://www.adssglobal.net

 

[Maggied]

That is going to be my next step. I will do that tonight when everyone is off.
Thanks

 

[ramam1]

Time it. If it is consistently just a smidge over 30s then it's likely a TCP timeout and that's often a DNS issue.

 

[Maggied]

Yes its 35 secs to logout and 40 secs to login. Thanks I will get the I.t person to look at the DNS. Is there anything I should tell him to look at?

 

[ettienne]

You can run SCANISAM any time.... but if you really want to wait until tonight then that is ok.

Sage 300 ERP Certified Consultant

http://www.adssglobal.net

 

[Jay Converse]

Scanisam has absolutely nothing to do with this problem, don't bother.

 

[ramam1]

Your IT guy can do some basic tests like ping/telnet from/to the various hosts involved; given that log*out* is slow I don't believe this will be fruitful; this type of issue usually shows up at initial connection time (to the TS, to the DB, etc).

 

[Maggied]

O.k good to know. Could it be the odbc connection? I am at a loss.

 

[Maggied]

Our Sgl person upgraded sql from 2005 to 2008 could it be something on that end?

 

[Maggied]

The I.t checked the TCP and DNS and everything seems fine. We have no customized directories setup. The PATH is correct. Anything else we could try?

 

[DjangMan]

How are you connecting Sage to the DB? Are you using an ODBC DSN or are you entering a server name and letting Sage make the connection? It might be worth deleting and re-adding the setup in Database Setup.

 

[ettienne]

Which authentication method are you using for users in Sage 300? (Sage 300/Windows/Both)

Sage 300 ERP Certified Consultant

http://www.adssglobal.net

 

[Maggied]

Hi, We are using the server name and tried the IP address and letting accpac create it. For the login we are using windows authentication.