| Fair enough Tim.
The wired thing is that at times when I can connect I cannot open active links and filters. I can open forms.
No issues with other severs on same client, same ds and same ar server configuration.
Thomas
I don’t know. You didn’t mention that there was a 2nd server involved where it loaded successfully. If you have 2 identical servers and are using DS on the SAME client machine to access them and one server loads properly and the other does not, then I probably would have eliminated a client side issue and not mentioned this. I’m just spit balling based on the scenario provided. :-) The only other thing I can think where this DS memory issue still might apply is if you are trying to log in to/load up both servers at the same time in your DS session. If you are trying to log in to both at the same time, try logging in to the unsuccessful one independently. /tp Thanks Tim, I'll check but why does it work with other server of the same version then?
I’ve seen this before when the dev studio did not have enough memory to load a large list of workflow objects. The default is 512mb. Go to the DS config and try increasing the memory it uses from 512 to 2048. That’s what worked for us. C:\Program Files\Java\jre1.8.0_161\bin\javaw.exe we have successfully upgraded our archive stand alone server from 8.1.00.002 to 9.1.03.001 Hotfix from Oct 2017. We can login and work using the Mid Tier. Dev Studio takes ages to log in. At other times the login works smoothly, we can load the form list but we cannot open the Active Link, Filter, Guides Lists as we get a time one saying that the server is busy. Any ideas where to start looking? The support has no idea so far.
|