Hi, I am new to DI and do not have enough knowledge about installation/administration. Currently I see all the repositories are configured to use port 3501. I guess my question is will I receive any benefit from creating multiple job servers and assigning repositories to each job server??
I bet you wont have issues when you do work from your local machine. The issue will come when you work through Terminal Servers. As soon as someone run the job from a Terminal Server, the person who have had the repository opened before the job run has to close and re-open the repository! I guess this is the issue you are facing.
You shouldn’t create multiple Job Servers for each user and in fact that isn’t going to solve your problem.
Ganesh you got it right !! As soon as someone run the job from a Terminal Server, the person who have had the repository opened is automatically kicked out. How can we resolve this issue when accesssing DI on terminal server. Can we open range of ports, will that solve the problem??
What login ID are the developers using? I had a client that had a problem where anyone using the administrator account would cause ETL job issues when logging out of a Remote Desktop session.
Look at the Windows service. There is a checkbox “Interact with desktop” or something like that. Be sure it is NOT checked on. If it is checked on then turn it off and restart the service.
That’s good. What is their security setting on that O/S? Are they in the administrators group? If so, change that. I think that was part of my client’s problem. Anyone in the administrator’s group would cause that problem.
I didn’t check with Administrators on the error. But I made my logins a Remote Desktop User and had to share (Install_Drive:.…\SAP BusinessObjects) to be shared to specifc id’s of mine and then yes, I had no issues executing job one after the other in alternate repositories!!!