|
| | | Forum Newbie
Group: Forum Members
Last Login: 2/1/2006 5:46:21 AM
Posts: 4, Visits: 15 |
| | I have continually fought with Point for the past 4 years to get it to cooperate with our setup, which doesn't seem abnomral. We have workstations and we have a file server, which is Linux machine running Samba. All of our Point directories reside on this Linux machine, and are available through a mapped drive ( Z: ) [PS: I've given up hope for URI or UNC path support]. I've finally managed to get Point to play nice in a multi-user environment, through kicking, some duct tape, and a little voodoo. So this evening I decided to ruin my Sunday and upgrade to 5.1, in an effort to enjoy the fixes to some of the glaring problems with this LOS. I begin by wiping Point from all of the machines in the office and backing up the point data directories and template directory. I was hoping that I could use the admin installation route to make my life simpler in the long run. This, however, doesn't seem to be the case. If I let the installer install to c:\NetSetup, the installation goes fine and I can run Point Administrator; however, the workstations don't have shared drives, that would be counter-productive in a domain environment, killing my security, and making life more difficult than it needs to be. So installing to a local drive doesn't work for our setup. If I make the installer install to Z:\NetSetup (a drive on the server), the installation goes fine, but I<b>cannot</b> run Point Administrator or the Network Configuration Utility. The error generated is as shown: 
So it seems that I get to continue spending an hour or more updating the machines every time an update is released... I very much look forward to a fix. Chris Pearson Operations Manager American First Mortgage |
| |
| | | 
Sepal
Group: Moderators
Last Login: Yesterday @ 9:52:28 AM
Posts: 1,183, Visits: 9,258 |
| The network configuration utility config.exe should not give that type of error it has no .net common run time in it. as for Point Administrator you might check permissions on your system to allow .net exes to run off of a mapped drive ( it should not be a problem if this is a local drive) Point has supported unc since 4.4 just as an fyi.
If you already have datafolders set up there is no need to run Point administrator. You should be able to run config.exe and set up the client pathing.
Disclaimer: This post carries no explicit or implied warranty. Nor is there any guarantee that the information contained in this post is accurate. It is offered in the hopes of helping others, but you use it at your own risk. The author will not be liable for any damages that occur as a result of using this post.  |
| |
| | | Calyx Software
Group: Administrators
Last Login: 7/18/2008 1:42:09 PM
Posts: 94, Visits: 467 |
| Are you launching Point admin and the network config utility from the Calyx Software program group on the client or from the netsetup folder?
|
| |
| | | Forum Newbie
Group: Forum Members
Last Login: 2/7/2006 7:56:57 AM
Posts: 8, Visits: 9 |
| | I use Point in much the same way. File server runing Linux and SAMBA. What I do to create the NetSetup directory is pretty simple.... do the admin install on another pc and copy the created c:etsetup directory into a netsetup directory that is on the Samba server. Works like a charm. That error looks familiar to me on a different problem - have you looked at your Folder.ini file in the \\servername\pointshare\pntdata folder? open that file and press CTRL-A to select all and you will see all the text get highlighted. Make sure there is no "white space" after any of the lines by deleting it. My problem was after the Company name |
| |
|
|