GoldMine is creating a new CONTACT2 record every time a contact record is accessed - Windows Event Log shows an Error: No value given for one or more required parameters
- When accessing any user defined fields of a contact record (CONTACT2 fields) the fields are empty although the user knows that values into the user-defined fields were added
- Upon further research a GoldMine Administrator or Microsoft SQL DBA recognizes that there are x duplicates of the CONTACT2 record for the specific ACCOUNTNO
- Upon further testing the GoldMine Administrator or Microsoft SQL DBA recognizes that every time accessing any CONTACT2 records (even when only scrolling through contact records (either when a user-defined field is on the primary screen or with the Fields tab or a custom screen is open) a new CONTACT2 record is generated for the contact record
- Verifying the local Windows Event log shows the error: No value given for one or more required parameters
- The CONTACT2 table contains an invalid column name for GoldMine. This can be either a column name with a ? like 'UTEST?' or column name with a special character like 'USTRAßE'
- The GoldMine front end will not allow such fields to be created, and a message appears 'Invalid characters used. You may use only Latin characters, digits and _ in field names' (Please keep in mind that the _ character should not be used at all either) if a user with master rights tries to create such a field, but Microsoft SQL allows such columns to be created in the back end (via MS SQL Designer on the CONTACT2 table)
- For any changes to the database (structure or content) which would be necessary in this case, it is absolutely recommended to make sure to have a full running backup of the database.
- This kind of data corruption needs to be corrected by the GoldMine Administrator (or MS SQL DBA) and also the duplicates need to be taken care of by the GoldMine (or MS SQL DBA)
- The affected field can be identified either by verifying the structure of the CONTACT2 table from within the SQL Server Management Studio or by applying the query from the local Windows Event Log directly in a SQL Query and identify the invalid character