Object Invalid or No Longer Set : Terminal Server Issue

[boxeronboard]

I am using MS Access 2007. I have a distributed application (accde) that attaches to the data tables on a specified network drive. The application is distributed to client PCs and works fine. The server configuration also has a virtual server using terminal services, so that users can access applications from a remote location. There is one spot in the application where Object Invalid or No Longer Set occurs when executing the application from a terminal server, but not from the application installed on PCs connected to the network.

MS requires the purchase of several licences if executing from a server with terminal services which is expensive and the client does not have, so I can't debug the code when the failure occurs executing via terminal services.

It seems that the network connection is lost when the application runs via terminal services (virtual server) at this point in the application.

Any help would be appreciated. I thought that perhaps terminal services / virtual server has a data limit that the application is exceeding, but that is outside my area of expertise.

Thanks, in advance, for any feedback.

 

[lameid]

Terminal Services and Access 2007 aside, many developers only use UNC paths to files to overcome drive disconnection issues. Some also argue that it prevents problems of drive mappings changing and other network issues.

I say that if a network admin maps the drives in a script and the network works, use the mapped drive... The admin will likely move the share to a different server on you at some point.

UNC vs Mapped Drive all depends on your environment (others would say always use UNC period) but in your case I would definitely begin by switching to UNC paths.

 

[boxeronboard]

Thank you for the valuable information.

As I continue to research this issue, I am finding more information leading to the client's configuration. The backend database resides on Windows 2008 Server and the 2003 Terminal Services is running as a virtual server. And since the problem only occurs when the Application is executed from the Terminal Services, I suspect that this is either a configuration problem or a server problem.

I believe that at this point, I need to post this issue on another forum.

Thanks all, for reading and considering this post.