PDA

View Full Version : PT can't detect INI file


mick2767
12-27-2004, 07:22 AM
We run PT Premium 2005 on a WIndows 200 server back. On the LAN the system is working fine. We have a Citrix server. When you connect to the Citrix server we receive "Peachtree could not detect the status of the Peachtree ini file." Again it is only though the Citrix connection. Any ideas? Mick mick2767@hotmail.com

M GO BLUE
12-27-2004, 11:17 AM
The data is on the Citrix server? You must be able to map a drive in order for the workstation to read the data from the server.

mlren777
12-27-2004, 02:31 PM
We have the same error coming up. Our situation is as follows:

We are running Peachtree Complete 2005 on a Windows 2003 Server pc. Remote Destop Connections are made to this pc. When a connection is made and the user tries to run Peachtree we get "Peachtree could not detect the status of the Peachtree ini file."

What file exactly is it looking for.

I do know that the 2002 version of peachtree required copying an ini named pcw90.ini to the local drive of the user that would be logging on remotely. This ini would be placed in c:\documents and settings\xuser\windows\ (xuser of course is the user name logged into windows).

mlren777
12-27-2004, 02:41 PM
Just figured out what needs to be done for this.

The file I previously mentioned is now called PPA120.ini.

This file should be copied from a PC that is successfully running Peachtree 2005. Copy it from C:\windows or c:\winnt depending on your operating system.

Now copy that file to the pc of the user that is trying to log on (whether that is via Remote Desktop Connection or Citrix or whatever method you are using). For me I had to copy the ini file to c:\documents and settings\xuser\windows\. I had to create the windows directory in this path. Xuser again is the name of the user logged in to Windows. This will have to be copied to all users logging in.

note that the about path in my case is "windows" because the users are logging onto a pc running Windows 2003. Windows 2003's "windows directory" is named windows rather than winnt. Windows 2000's "windows directory" will be called winnt. So the path would then be c:\documents and settings\xuser\winnt\

If you open up the ini file you will see that it is self explanatory as to what each section does. Pay close attention to the data path section.

davidk@lcdsolar
09-07-2005, 03:55 PM
I am coming up against a situation that I beleive may be sililiar to what has been described in previous posts.

I would appreciate some feedback from others that have done this or no about this process.

I am going to be connecting a remote user to our file server where the PeachTree Premium 2004 data files are located. If I load the PeachTree program onto the remote computer, I beleive the .ini file mentioned will be loaded onto that computer. Thus, all that will need to be done is mapping the remote computer data path to my file server.

It sounds so easy stated like this. Can I get a vote of approval for what I have dexcribed from someone who has been through this process before? Please? :)

Thank you in Advance for your time in reading this post.

David@lcdsolar

TheWolf
09-07-2005, 09:56 PM
If you are using terminal services just put a copy of it in the users directory on the server.