Problem connecting to db

[SimonW]

Hi Folks

Problems opening a database application through a Windows Terminal Services
window.

The application records its database path in an initialisation file normally
written to \windows (windir)

Traditionally (for remote users accessing the application on the TS through
their TS client window) this file is copied to each remote users' \windows
folders on the Terminal Server computer

The application starts but fails to connect to the database recorded in the
*.ini - An error message is displayed in the Terminal Services window as
follows

Error 75 (path)

This is clearly a result of the initialisation file not being detected. Or
I may be missing something - can any one help

TS
c
..progra~
...application
..windows
..*.ini
..documents and settings
...user1
....windows
.....*.ini
...user2
....windows
.....*.ini
etc

Thanks in advance

Simon

 

[SimonW]

RE: Problem connecting to db

In addition. I note the article immediately before mine that mentions
changing the location of documents and settings. On our TS server the local
profiles are held on a partitioned drive D:

Would this contribute to our problem?

Amended root folders

c:
..progra~
...application
..windows
..*.ini
d:
..users
...user1
....windows
.....*.ini
...user2
....windows
.....*.ini
etc


"SimonW" wrote:

> Hi Folks
>
> Problems opening a database application through a Windows Terminal Services
> window.
>
> The application records its database path in an initialisation file normally
> written to \windows (windir)
>
> Traditionally (for remote users accessing the application on the TS through
> their TS client window) this file is copied to each remote users' \windows
> folders on the Terminal Server computer
>
> The application starts but fails to connect to the database recorded in the
> *.ini - An error message is displayed in the Terminal Services window as
> follows
>
> Error 75 (path)
>
> This is clearly a result of the initialisation file not being detected. Or
> I may be missing something - can any one help
>
> TS
> c
> .progra~
> ..application
> .windows
> .*.ini
> .documents and settings
> ..user1
> ...windows
> ....*.ini
> ..user2
> ...windows
> ....*.ini
> etc
>
> Thanks in advance
>
> Simon

 

[Jeff Pitsch]

Re: Problem connecting to db

It's entirely possible with Access. Access on TS is a PITA. Where is your
home directory? or have you specified no TS home directory? What happens
if you do specify a home directory (user properties, GPO)?

Jeff Pitsch
Microsoft MVP - Terminal Services


"SimonW" <SimonW@discussions.microsoft.com> wrote in message
news:5E9B164B-7415-4788-8544-591C9EFCBBFC@microsoft.com...
> In addition. I note the article immediately before mine that mentions
> changing the location of documents and settings. On our TS server the
> local
> profiles are held on a partitioned drive D:
>
> Would this contribute to our problem?
>
> Amended root folders
>
> c:
> .progra~
> ..application
> .windows
> .*.ini
> d:
> .users
> ..user1
> ...windows
> ....*.ini
> ..user2
> ...windows
> ....*.ini
> etc
>
>
> "SimonW" wrote:
>
>> Hi Folks
>>
>> Problems opening a database application through a Windows Terminal
>> Services
>> window.
>>
>> The application records its database path in an initialisation file
>> normally
>> written to \windows (windir)
>>
>> Traditionally (for remote users accessing the application on the TS
>> through
>> their TS client window) this file is copied to each remote users'
>> \windows
>> folders on the Terminal Server computer
>>
>> The application starts but fails to connect to the database recorded in
>> the
>> *.ini - An error message is displayed in the Terminal Services window as
>> follows
>>
>> Error 75 (path)
>>
>> This is clearly a result of the initialisation file not being detected.
>> Or
>> I may be missing something - can any one help
>>
>> TS
>> c
>> .progra~
>> ..application
>> .windows
>> .*.ini
>> .documents and settings
>> ..user1
>> ...windows
>> ....*.ini
>> ..user2
>> ...windows
>> ....*.ini
>> etc
>>
>> Thanks in advance
>>
>> Simon

 

[SimonW]

Re: Problem connecting to db

Hi Jeff, thanks for you reply. I am not sure what you mean by home directory.
The application is in progra~ and user profiles are as illustrated below.
We have discovered some audit files in system32 that also need
read/write/execute permissions. We are making these changes and hope things
work. Will let you know.

Regards, Simn

"Jeff Pitsch" wrote:

> It's entirely possible with Access. Access on TS is a PITA. Where is your
> home directory? or have you specified no TS home directory? What happens
> if you do specify a home directory (user properties, GPO)?
>
> Jeff Pitsch
> Microsoft MVP - Terminal Services
>
>
> "SimonW" <SimonW@discussions.microsoft.com> wrote in message
> news:5E9B164B-7415-4788-8544-591C9EFCBBFC@microsoft.com...
> > In addition. I note the article immediately before mine that mentions
> > changing the location of documents and settings. On our TS server the
> > local
> > profiles are held on a partitioned drive D:
> >
> > Would this contribute to our problem?
> >
> > Amended root folders
> >
> > c:
> > .progra~
> > ..application
> > .windows
> > .*.ini
> > d:
> > .users
> > ..user1
> > ...windows
> > ....*.ini
> > ..user2
> > ...windows
> > ....*.ini
> > etc
> >
> >
> > "SimonW" wrote:
> >
> >> Hi Folks
> >>
> >> Problems opening a database application through a Windows Terminal
> >> Services
> >> window.
> >>
> >> The application records its database path in an initialisation file
> >> normally
> >> written to \windows (windir)
> >>
> >> Traditionally (for remote users accessing the application on the TS
> >> through
> >> their TS client window) this file is copied to each remote users'
> >> \windows
> >> folders on the Terminal Server computer
> >>
> >> The application starts but fails to connect to the database recorded in
> >> the
> >> *.ini - An error message is displayed in the Terminal Services window as
> >> follows
> >>
> >> Error 75 (path)
> >>
> >> This is clearly a result of the initialisation file not being detected.
> >> Or
> >> I may be missing something - can any one help
> >>
> >> TS
> >> c
> >> .progra~
> >> ..application
> >> .windows
> >> .*.ini
> >> .documents and settings
> >> ..user1
> >> ...windows
> >> ....*.ini
> >> ..user2
> >> ...windows
> >> ....*.ini
> >> etc
> >>
> >> Thanks in advance
> >>
> >> Simon
>
>
>