ravensoftware
IS-IT--Management
Thanks for reading this post.
I have a linux customer - I know little about Linux myself but there is an onsite IT guy helping me. They Refuse to change to a windows environment and unfortunately 10 years ago we managed to get everything working and it has been stable with an older version of accpac and PVSW for that long so there is no convincing them to migrate to a windows server etc....
On a windows XP box we have gone through a lengthy ordeal to get accpac and pervasive installed on the server and working. When we try to get the second workstation, a 64-bit workstation, to connect we get a 49153 error. There is no terminal services involved with this installation.
I have used the 32-bit ODBC to create the odbc's on the workstations in the 64-bit OS C:\Windows\SysWOW64 - and when I hit test they connection is successful...
What I noticed is that when I go to PCC and connect to the server engine and look at a specific database its path shows /usr/local/psql/data/lgcinc and I think it should show the unc path to the database: LGCINC is my database and the path to the data is \\10.0.1.97\accpac\psqldata\LGCINC - (for some reason only the IP address would work to browse to the data path). When I change the path i get the error message....
I have done literally hundreds of these accpac setups for MS-SQL and Pervasive (only once for linux 10 yrs ago) and am clearly out of my depth - I cannot determine if I have a linux problem, a security problem, or I am over complicating things unnecessarily and the answer is simple. Sage tech support will not help.
can you actually edit the WTS_restrictions registry on a linux box? I have been told we have 'god like' administrator rights to the server and our login is as administrator to do the installing on the server and workstations and again there is no T/S involved....
any help would be appreciated
thanks
M
I have a linux customer - I know little about Linux myself but there is an onsite IT guy helping me. They Refuse to change to a windows environment and unfortunately 10 years ago we managed to get everything working and it has been stable with an older version of accpac and PVSW for that long so there is no convincing them to migrate to a windows server etc....
On a windows XP box we have gone through a lengthy ordeal to get accpac and pervasive installed on the server and working. When we try to get the second workstation, a 64-bit workstation, to connect we get a 49153 error. There is no terminal services involved with this installation.
I have used the 32-bit ODBC to create the odbc's on the workstations in the 64-bit OS C:\Windows\SysWOW64 - and when I hit test they connection is successful...
What I noticed is that when I go to PCC and connect to the server engine and look at a specific database its path shows /usr/local/psql/data/lgcinc and I think it should show the unc path to the database: LGCINC is my database and the path to the data is \\10.0.1.97\accpac\psqldata\LGCINC - (for some reason only the IP address would work to browse to the data path). When I change the path i get the error message....
I have done literally hundreds of these accpac setups for MS-SQL and Pervasive (only once for linux 10 yrs ago) and am clearly out of my depth - I cannot determine if I have a linux problem, a security problem, or I am over complicating things unnecessarily and the answer is simple. Sage tech support will not help.
can you actually edit the WTS_restrictions registry on a linux box? I have been told we have 'god like' administrator rights to the server and our login is as administrator to do the installing on the server and workstations and again there is no T/S involved....
any help would be appreciated
thanks
M