Calyx Software Message Board / Calyx Point / Installation / Network Setup

Upgrade from 5.3a to 6.2

Shane — Sun, 05 Oct 2008 17:03:32 GMT

Hi Everyone!

I have a very interesting problem when upgrading my Point 5.3a to Point 6.2. The server side installation to the netsetup folder runs fine. However, when I run Point Admin the users listed are completely incorrect, even though the security password from 5.3a allows me to manage and access. The users listed are the original users that setup the very first installation of Point about 7 years ago. None of these users have been setup in Point for over 5 years now. Also when I run Point Network Configuration Server the only folder listed is the main folder. Oh, please read on before you reply…. It gets even more interesting.

Since I’m doing this in a test environment, I figured what the heck, let’s go ahead and launch Point from one of the test workstations to see what happens.

I launch Point from the workstation, I get the prompt that Point must 1st uninstall LoanBridge 5.3 prior to installing Point 6.2. So, I allow it to remove LoanBridge 5.3. The installation proceeds and successfully completes.

Now I launch Point from the workstation. At the login prompt, I enter the user and password for a user that has FULL control of all of the folders. Note, this user is NOT one of the users listed when you run Point Administrator on the server!

To my amaze, I can login and run Point under this name. Interesting, I thought… So, I exit out of Point and decide to run Point Administrator from the workstation.

Point Admin launches successfully; all of my users and data folders are correctly list that were in version 5.3a; however, this is completely the opposite of what launching Point Admin from the server produces.

Now, my questions are……………. What the heck? How is this possible? Even better yet, WHY?

Anyone care to elaborate? Take a guess?

Thanks!

Shane

Windows Vista Update

mwm50 — Thu, 04 Sep 2008 06:58:43 GMT

A client just purchased a new laptop, installed Point 6.1a, then downloaded and installed Vista updates. Point worked before the updates but now it terminates with the message:

Point application has stopped working. A problem caused the program to stop working correctly.

He has tried uninstalling and reinstalling Point but gets the same error. (He also tried to repair with same result.)

Newbie

iggles — Thu, 25 Sep 2008 13:19:15 GMT

I just installed Calyx on a brand new PC for the first time. Everything seemed to be ok but there is an issue with transfering closing docs to FAND. When it is done it states that it was successfully sent but when we check the FAND site the doc is not there....any ideas?

Template Directory not recognized after 6.2 upgrade

sb1920alk — Wed, 01 Oct 2008 15:08:50 GMT

We've been holding the template directory on a mapped drive. 6.2 doesn't recognize it, but it does recognize the long path (\\servername\...). The mapped drive is working correctly for other purposes. Any idea what changed?

Custom Settings and Roaming Profiles

FeralCat47 — Wed, 01 Oct 2008 13:55:17 GMT

(Also posted to the Citrix/Terminal Server Forum)

We recently installed Point 6.2 on one of our Windows Terminal servers.

Customizations are being saved to the "C:\Documents and Settings\username\Local Settings\Application Data\Calyx Software" folder (userprofile.ini, fannie.ini, fnma.ini, brwforms.ini, etc.) However, we use roaming profiles and as a result, none of these files are being saved back to the user profile on the file server as the "Local Settings" folder does not roam. Hence, all preference changes and options must be reset every time a user logs out and back into the network.

Is there any way to specify where these files are created instead of simply using the default location listed above?

Thank you in advance for any insight you may have.

David Aardema

Mortgage Works

.msi Installer for Point 6.2?

PCM — Mon, 08 Sep 2008 16:16:25 GMT

Has the .msi installer package been fixed for Point 6.2? It failed validation in 6.1 and 6.1a. Naturally, this meant that I either supply all users with local admin rights to install the updates or (which is what we did), roll it out one-by-one, taking about 3 hours to roll out the latest updates.

6.2 Upgrade

DarrinMc — Wed, 01 Oct 2008 10:50:31 GMT

Curious how many other users are happy about this upgrade to 6.2? After calling tech support for the 5th or 6th time since the upgrade, the hold time just to talk with someone is over 30 minutes. Once you get a tech on the line, they state that it’s a known issue and are working on a patch to resolve. Should have known there was going to be issues when we received a hand written CD with zero documentation. Issues known so far:

1. On the Credit Score Information Disclosure it prints the city and state of the credit bureau not the borrower name on the signature line.
2. Custom forms when within exciting form groups now print PCL XL error Subsystem: Kernel Error:illegalOperatorService. But printing the forms by it’s self prints fine. 3 different HP printers multiple machines.
3. Even though tech support tells you it’s ok to run the rebuild on your PDS server during business hours, it’s really NOT ok. Your users will start complaining that files have disappeared until you can run the process again with no one in Point.
4. Error message that Point has encountered an error it could not recover from System.Runtime.InteropServices.SEHException; External component has thrown exception, during install. And it WILL NOT install. Gone through the normal uninstall anti-virus, .NET blah blah, still doesn’t install.
5. DocTypes had disappeared and yet to hear how to fix yet. Other then that info is in the FOLDER.INI. Well, it’s not. And only the user that created the doc types is able to view.
6. Symantec EndPoint Protection has to be uninstalled to get Point to install, then you can re-install it.
7. The FHA MIP is still broken from the 6.1 upgrade that was supposed to be fixed in the next update.

Knowing that we received this CD with zero time to test is also great. We are big fans of waiting until the last minute on upgrades for the above reasons. However with the FHA items that go into effect tomorrow, didn’t give us any choice but to upgrade.

It seems as though Calyx has little or zero QA of their products before releasing to the masses. We, the end users and support, are the QA awaiting the next patch to fix the issues from the release.

Best line used when calling Calyx prior to the upgrade – “You sent me a hand written CD, with zero documentation knowing that your last upgrade deleted files from the server. Would YOU upgrade if you were in my shoes?”

What is the new UserProfile.ini for 6.2?

Drummy — Tue, 30 Sep 2008 06:43:09 GMT

We sometimes had issues with bad UserProfiles.INI files where the UI was totally messed up because this file would get corupted.

I just had the same problem with 6.2, but the UserProfile.INI file seems to no longer have any bearing on reparing the UI.

Any ideas? I have a user that is dead in the water (or I have to completely uninstall / reinstall every time this happens).

Thanks!

EDIT : Scratch that... even uninstalling it doesn't work! The UI is still unusable.

Data Folder

keystone — Tue, 23 Sep 2008 12:53:53 GMT

Hello,

I'm running into an issue when installing Point 6.2

OS: Windows XP Prof. Service Pack 2

This is a brand new install of Calyx Point - no previous versions are installed. We are installing via NETSETUP. The NETSETUP folder sits on one of our servers. I have edited the Config.exe file to add a data folder call C:\PNTDATA\ & I have checked the Do Not Override and Install Point Admin check boxes.

I've tried to install via run.exe and Point.msi - doing it both ways results in the same issue - NO DATA FOLDER IS CREATED.

Can someone please help? I called Tech Support and the gentlemen told me that "Its software, sometimes it works sometimes it doesn't" he also told me that you can "only setup folders on a server with that function" These answer are unacceptable. I know in the past we have used the NETSETUP to create a local data folder prior to the install.

Point 6.2 Installation issues

fatjoeyc — Mon, 22 Sep 2008 11:52:36 GMT

When installing Point 6.2 on an existing 6.1a computer, the following error occurs: Error 2908 Could not register component {F6838B8E-3FB4-4E26-AB5D-2ABDC1A80D20}

Any suggestions?

Win 2K Computer, Point data server user.

Thanks,

Joe

Having issues installing point 6.2

PPS — Mon, 22 Sep 2008 09:11:13 GMT

I am trying to install Point 6.2, but everytime I load the program, i get an error stating that Adobe Flash Player 9.0 has stopped working. Then the program stops loading all together. I have Windows Vista, but i had no problem on updating before to Point 6.1...

any ideas?

WINPOINT/WORK/EMBDCredit.pdf

Jimmy — Tue, 13 Dec 2005 09:25:47 GMT

I'm experiencing intermittent problems in viewing credit reports and exporting to fannie mae format through terminal services. Is there some 'quick fix' that I can apply in order to eliminate the sporadic availability of viewing credit?

ERROR: SAXCOM32.dll

KenGray — Wed, 08 Aug 2007 22:12:56 GMT

Does anyone have a copy of SAXCOM32.dll I could copy to my local directory?

Ken

Big Data Folder issue!

Blizzardace — Wed, 16 Jul 2008 10:23:56 GMT

I recently updated to the 6.1a build on on the offices server and performed Netsetup Admin install to 10 client comps no problem..
my first order of business was to create two new data folders which was all so done with out issue. set to import user data, and applied security..and continued to make the data folders available in the Netsetup window..

i checked on the client machines and both new data folders appeared ALONG with duplicates if the Three existing data folders totaling 8 data folders.. the duplicate having the same contents of the originals except that the borrower files would not allow me access.. Note the two new data folders would not allow me access either..

Logically i go to check the users window and... horror.. there was nothing there! horror because i couldn't comprehend how without user data, i and the 20 other users had been logging...

so i return to the Data folder manager and the duplicate folders are visible same extensions and all but BIG NOTE... All three original data folders (six with duplicates) are not owned! so i log out of the Point administrator, re-login the data folders password and only the two new folders are owned the other give me this error

http://kb.calyxsupport.com/kb/article.php?id=546

the suggestion there is of no help because im IT tech whom set-up the system.. and i know the password.. and its not working!

Sigh.. even more puzzling is, if we don't own the data folders, why can my users (whom don't exist according to the users window) still access the files!

I've tired disconnecting and relinking the data folders.. same issues.. not owned.. Anyway Users i can recreate no problem but is there ANYWAY to relink those data folders? reapply ownership? im not going to try a reinstall right now because by some miracle the office is still operational! sorry for the large post its a BIG Problem!

New 6.1a install won't talk to PDS

go123 — Tue, 12 Aug 2008 12:15:59 GMT

We are a new user of Point 6.1a and PDS. We have PDS hosted remotely at FocusIT - Calyx's recommended vendor.

We have 9 machines (all XP SP2) with 6.1a installed but 4 won't run using PDS- When logging in to PDS an error shows on each machine:

Calyx Point has encountered an error it could not recover from.
The details are as follows:
System.Runtime.InteropServices.SEHException: External component has thrown an exception.
at CPointApp.SubInitInstance(CPointApp* , Int32 LibMode)
at CPointApp.InitInstance(CPointApp*)

When testing the PDS connection in Point Administrator, I get:

Point Administrator MFC Application has encountered an error and needs to close. We are sorry for the inconvenience.

All machines run 6.1a locally just fine w/ PDS turned off in Point Admin.

I've been through at least one level of escalation in the Dallas office w/ Brandon but have not heard anything - "we're beginning to hear of a few of these problems..." The only solution (that FocusIT figured out) is to downgrade those installations to Point 6.0.

Calyx support tried everything - removing .NET 1.1 and 2.0, removing WSE, snooping through the registry, every other setting they could think of, etc, etc. Nothing works to get 6.1a running. These 4 machines not working are 2 Dell (each different models and ages), an Acer, and one HP. In each case, the downgrade (remove 6.1a and install 6.0) worked and all are up and running as advertised.

It's been 2 weeks since I last heard from Brandon - who worked for 2 weeks on the problem. Good thing I still had Encompass to fall back on!

If anyone else has seen these problems, or got any resolution, I'd love to hear about it!

There's another post from 6/18 showing the removal of WSE solved a similar problem, but that's been tried 2 or 3x on my machines with no change in error messages...

Thanks!

PDS Using SQL Express vs SQL

tomob — Thu, 15 May 2008 04:40:50 GMT

We are considering upgrading to PDS With remote offices and remote LO many of the feature offered intrigue us.

We have a New DELL Server with MS SERVER 2007 VMWare and also have 12 licenses for Terminal Server and our team has struggled with errors, speed, and time consumption to get it working right.

With 2 of our off site offices in the neighboring state ( 4 to 6 LO in each office)

Our main office has 2 - 3 Processors and about 25 - 30 Loan Offices, Not all of them in the office at the same time accessing point.

Our server have plenty of RAM and we are about to add more disc space Our dilemma is the cost or SQL ($9000.00) at what point is SQL Express not going to work for us in the environment. Our Tech team which are sub Contractor are telling us SQL Express will not work for us. And want to sell us $9000 upgrade. at what point do you need more then Express

Thanks

Networking Point

keystone — Wed, 06 Aug 2008 13:26:45 GMT

Hi,

Currently all of our installs of Point are stand alone. We send out updates to our LO's in the form of .exe's. The .exe's manipulate the users computer. Mainly the PNTDATA and PNTTEMPL folders. This process was in place way before I even came on board here. So I've never questioned it.

Looking at the Knowledge Base I came across article 0207 under Installation that talks about Networking Point with Admin install for over 10 computers. I was told by the last guy here that networking Point was impossible unless you had PDS. Based off of this article it seems like he was incorrect. It looks like it can be done.

We would be trying to network 300 users. I understand we would need a centralized server that all workstations would be able to access. If I understand the article correctly you would take the new release of Point and pop it in ther server. Follow the directions by installing the Admin piece. Place the PNTDATA and PNTTEMPL folders on the server. Setup Config.exe to point to the networked PNTDATA and PNTTEMPL. From there each workstation would just need to access the server and run the file run.exe from netsetup. Does this sound about correct?

Also, I read where it says "Auto-update each workstation with the new version of Point, when release" what exactly does this mean. Lets say the workstations have 6.1 and the server has 6.1. Lets say we then update the server to 6.2 - does this mean that the next time the users log into Point it will also update their workstation to 6.2? To me thats what Auto-update means. But I could be wrong. Clarification on how this scenario would play out would be helpful.

Just looking to get some answers as it seems we are doing things the hard way.

Adding a CPU with Point to Share Files

mwood — Wed, 06 Aug 2008 08:56:55 GMT

I have 5 computers with point and adding a new one. However I am having issues trying to add this one to share the files. Does anyone know how I can get them to share with the othhr computers or how to set this up? Thank you very much.

Netsetup 6.1 and 6.2

keystone — Thu, 31 Jul 2008 06:01:46 GMT

Hello,

Wondering if anyone can help with this one. When netsetup completes it laucnhes Calyx Point. Is there a way to stop this? I want it to install Point but not launch it. I looked around the files inside of the netsetup folder but was unable to find the key to hault this.

Thanks in advance.

6.2

keystone — Fri, 25 Jul 2008 06:45:11 GMT

When can we expect version 6.2? Just curious!

Thanks!

Page4 of 1003 b/c of 6.1

sredding — Mon, 16 Jun 2008 13:20:42 GMT

With this new version....There will be a date printing on page 4 of the 1003. It is being pulled by Interfaces/Fannie Mae/Addedum.

There a date will appear. Today's date. Unless you are looking up one of your older but still open files. The date that appears is the date that the "Template was Made" ie: 5/27/2003....

So if I don't catch the old files when they go to closing the final 1003 is out of complainance b/c the date is so old....

Add DataFolder

keystone — Thu, 24 Jul 2008 13:41:35 GMT

Hi,

I have users who will be dowloading 6.1 via NETSETUP. How can I be sure that new users have a data folder setup at C:\PNTDATA - and that existing users do not have information in this located deleted? Would it be in the config file?

Thanks!

6.1 update and compliance

RLS — Thu, 22 May 2008 13:57:13 GMT

Does 6.1 have an update that is necessary for copliance issues? I know it is supposed to be a helpful update, but we are having a difficult time installing it and want to know if the updates are required. If they are not, we are going to wait until we can get some computer help in here before we install it. We are small and not comfortable with what we have to do on each computer in order to install 6.1.

Point 6.x not saving

Kewdah — Fri, 18 Jul 2008 05:34:09 GMT

Hi,

I am looking to see if anyone else has experienced this issue.

We migrated for point 5.4 to Point 6.x w/ PDS 6.x a while back.

Ever since my users are saying that thier data when updating a loan is not bieng saved intermittantly. Even if they click the save button explicitly.

I have not been able to recreate this issue myself nor find anything in any of the logs about it evt/IIS/sql log ect.

Anyone have any ideas or could point me in the right direction to find the source of this issue?

6.1A Template Path losing "L\"

todrescher — Thu, 26 Jun 2008 10:17:46 GMT

I know of the issue where if you don't put the trailing back-slash in the template directory path in the config for a netsetup install, the winpoint.ini on the local machine will get the wrong template directory path (instead of calyx\pnttempl you'll get calyx\pnttemp).
Since we upgraded to 6.1A (from 6.0A or B, whatever the last letter patch was for 6.0) client machines are dropping the "L". We -do- have calyx\pnttempl\ in the config in the netsetup folder, and I've even changed the winpoint.ini on the local machines to include the correct (with following slash) path, but they still seem to be losing that data, meaning every day we're having to change the winpoint.ini again.

And as long as I'm here....

m00se — Thu, 19 Jun 2008 15:49:31 GMT

What's REALLY wrong with 6.1? You claim the reason for 6.1a was to correct a flaw in the netsetup install that was affecting 1% of your users. Shipping a new CD to every customer had to be a huge expense; one that makes no economic sense to fix a problem that affects just 1% of your users. The enlcosed letter adds suspicion becuase it tells us to throw away the 6.1 CD.

So... What's REALLY wrong with 6.1?

Do we need an update to 6.1a?

m00se — Wed, 18 Jun 2008 10:43:25 GMT

Point 6.1a may have fixed some of the issues with netsetup installs in version 6.1, but it didn't address all of them. I would like to see another interim release, ASAP, that fixes all of the netsetup issues and provides a point.msi file that passes validation. Do you agree? Disagree? Why?

6.1a crashes after PDS login

m00se — Wed, 18 Jun 2008 14:44:28 GMT

I have two PCs where Point crashes after PDS credentials are submitted. This happens in both 6.1 and 6.1a. Both systems are CD Rom installs. In both cases, Point 6.0 worked with the PDS server with no problems. Both systems are Windows XP. The PDS server is version 6.1.

I have tried upgrading 6.1 to 6.1a and uninstalling 6.1a and re-installing from 6.1a media after deleting the Winpoint.ini file.

I get a similar failure when I run a PDS Test from Point Administrator. Here is the event log that was generated:

Event Type: Error
Event Source: Application Error
Event Category: None
Event ID: 1000
Date: 6/12/2008
Time: 2:33:31 PM
User: N/A
Computer: PWAKEFIELD06
Description:
Faulting application pdsconnect.exe, version 6.1.971.422, faulting module kernel32.dll, version 5.1.2600.3119, fault address 0x00012a5b.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 41 70 70 6c 69 63 61 74 Applicat
0008: 69 6f 6e 20 46 61 69 6c ion Fail
0010: 75 72 65 20 20 70 64 73 ure pds
0018: 63 6f 6e 6e 65 63 74 2e connect.
0020: 65 78 65 20 36 2e 31 2e exe 6.1.
0028: 39 37 31 2e 34 32 32 20 971.422
0030: 69 6e 20 6b 65 72 6e 65 in kerne
0038: 6c 33 32 2e 64 6c 6c 20 l32.dll
0040: 35 2e 31 2e 32 36 30 30 5.1.2600
0048: 2e 33 31 31 39 20 61 74 .3119 at
0050: 20 6f 66 66 73 65 74 20 offset
0058: 30 30 30 31 32 61 35 62 00012a5b
0060: 0d 0a ..

Frustration

m00se — Thu, 19 Jun 2008 15:44:41 GMT

I ran into an interesting problem today. My users that have 6.1 (not 6.1a) and tried to update to 6.1a using the full install set were rewarded with a message that it (6.1a) was already installed. It appears to me that 6.1 must be patched to 6.1a - that the 6.1a install set can only install new or upgrade from a previous install that is a full version older, like 6.0.

Calyx, your product isn't good enough for me (us, I hope) to put with this much frustration. 6.1 has confused and frustrated my users, frustrated an annoyed me, and made the IT Department as a whole look bad.

Workstation keeps trying to update to 6.1a

flynjets — Tue, 17 Jun 2008 13:37:31 GMT

I installed 6.1 to our server and then to 2 clients. I downloaded the 6.1a patch and followed the instructions to install it. One client (Windows Server 2003) updated with no problem. 1 client (Vista SP1) keeps wanting to install the update every time you start the program. I tried updating the winpoint.ini with the new count from the sever but that didn't work. I tried also updating the version and build in the winpoint.ini but that didn't help either. I tried deleting the winpoint.ini and running the run.exe file to replace it. I tried unistalling the program and re-installing using run.exe from the netsetup folder but that didn't solve the problem either. Any one know how to fix this issue? Thanks.

Preventing Loan Officers From Deleteing Thier Files

jparrill — Thu, 17 Apr 2008 16:07:43 GMT

I am trying to prevent my loan officers from being able to use the Delete feature. What I am seeing is that instead of doing their turn down paperwork they just delete the files and I need to stop this! Anyone know how?

Thanks in advance for your help!

Strange 6.1 error

m00se — Tue, 10 Jun 2008 16:31:03 GMT

One of my users upgraded to 6.1 from 6.0 today and now gets the following error:

"Calyx Point has encountered an error it could not recover from. The details are as follows:

System.Runtime.InteropServices.SEHException: External component has thrown an exception.

at CPointApp.SubInitInstance(CPointApp*,Int32 LibMode) in d:\foreman\source control\point\main\winpoint.cpp:line 1046

at CPointApp.InitInstance(CPointApp*) in d:\foreman\source control\point\main\winpoint.cpp:line 732"

I use a PDS server. This error occurrs after the user types his login and password to connect to PDS. I have completely uninstalled and re-installed Point 6.1.

NETSETUP 6.1 to 6.1a

m00se — Fri, 13 Jun 2008 12:32:44 GMT

When I receive the 6.1a CD, I assume I will build a 6.1a netsetup in the traditional way. Do I then place that in my shared NETSETUP folder? I have added the 6.1a patch to it. Will that cause any kind of version conflict? Will Point try to "upgrade" itself when a 6.1a native build replaces the 6.1 build w/6.1a patch?

Print Groups deleted

JohnCorey — Wed, 21 May 2008 12:16:51 GMT

Recently upgraded to 6.1. This promptly deleted my print groups, and removed some forms I use on a regular basis. Since I had a different print group for each investor, that creates problems. Where are these stored? I saw an older post around the time of the 6.0 upgrade (beginning of this year) that mentioned some .ini files to replace. Would the same rules apply to the new version? Could I simply take an .ini file from a computer that has not upgraded to 6.1, and put it on my 6.1 computer?

6.1: Error TITILE INSURANCE (LENDER’S) table button Closes Point

pmieszerski — Mon, 09 Jun 2008 09:46:40 GMT

Program problem has been identified with the new 6.1 Point Release.

If the application is a PURCHASE you can not click the TITILE INSURANCE (LENDER’S) table button, item #1108, on the Good Faith Estimate screen or Point will automatically shut down.

The work around for this error is:

1. On the BORROWER screen; change the application from a PURCHASE to a REFI

2. Go to the GFE screen; click the ‘table’ button and select the title company needed

3. Return to the BORROWER screen; correct the application back to a PURCHASE.

6.1a Patch in NetSetup Environment

twedlake — Tue, 10 Jun 2008 04:25:31 GMT

Can anyone tell me where the point6.1a-eu.exe file needs to reside in order for the patch to be updated on the clients when they launch point in a netsetup environment please?

thanks

Todd

6.1 NETSETUP Strangeness

m00se — Wed, 11 Jun 2008 14:52:21 GMT

I have configured a network installation of Point 6.1 for those of my users that it will work for. So far, all of them that have upgraded from 6.0 using "run" from the netsetup folder have lost thier Primary Data Folder.

Here are a couple of snippets from the Winpoint.ini file:

[PDS]
Folder0=C:\PNTDATA
Enable=1

[Directories]
Application=C:\WINPOINT\
Templates=C:\PNTTEMPL\
Folder0=C:\PNTDATA\|

No, the "|" on the end is not a typo here. All users who upgraded from 6.0 to 6.1 have two references to C:\PNTDATA and all of them have the "|" on the end of the second one. The fix is simple enough - remove the pipe character and the Primary Data Folder comes back.

I used config.exe in the NETSETUP folder to enable PDS and set the server and key name, and I checked "Do not overwrite existing Data Folder Settings".

What's going on here?

Uninstall from client after runing run.exe

brodiemac — Thu, 14 Feb 2008 11:41:30 GMT

I need to remove the client application from a workstation but there is no uninstall routine in add/remove programs. We installed initially from the Point Data Server using run.exe. I've searched the forums and haven't seen anyone with a similar problem so perhaps this is unique or I'm just not looking hard enough. Either way, any help would be appreciated.

Installing Point 6.1 using point.msi

MH — Wed, 14 May 2008 07:23:56 GMT

I am trying to utilize the .msi files that come with 6.1 to roll out Point using a group policy in Active Directory. There are 2 that come on the new disk, netsetup.msi and point.msi

When i use netsetup.msi all it does is create a netsetup folder on the users machine which is useless to me. When i try to import the point.msi package i keep getting an error stating that "Add operation failed. Unable to extract deployment information from the package. Run validation on the package to ensure that the package is correct" I have found some articles from Microsoft, but none of the situations or fixes offered apply to the problem i am having.

I have been back and forth with support for a few days now, and not getting much help. Also have not been able to find any documentation from Calyx on using these files.

Has anyone been able to use point.msi successfully to roll this out?

Disable fields for Specific Users

ma4man — Thu, 05 Jun 2008 13:47:50 GMT

I have gotten a request to disable a few fields on the General Tacking and Status screen for specific user groups. Is there a way to disallow users from entering a status date by posiiton? For example, only allow underwriters to enter a date in the Approved field. All other users would not be able to enter data in this field.

Thanks!

:rolleyes: