SetupBuilder and Windows Terminal Services
We have a few customers that have installed our newest release of our software and they cannot use their terminal server connections, using Windows Terminal Services 2000. The only difference in the current release is we installed build 2309 of SetupBuilder. Was their any changes in build 2309 that might cause these connections to have a pathing problem. They are getting error 45 (Invalid Filename)although the full path in the error message is valid on one of our Btreive tables. We have a log that shows the system trying to find the start in path (it goes through every hard drive and all of the folders looking for it but cannot find it). I don't think it is SetupBuilder but we are checking everything.
Reply With Quote
