Community
Showing results for 
Search instead for 
Do you mean 
Reply

Error message in Act 10: This contact no longer exists in the database

Accepted Solution Solved
Copper Super Contributor
Posts: 87
Country: United Kingdom
Accepted Solution

Error message in Act 10: This contact no longer exists in the database

Hi,

Sorry for the length of this, but I feel it’s necessary to help narrow down the problem early on.

Our Act Setup
Me and a colleague have been using Act 10 (standard version) without any problems since October 2007. Our database was created in Act 5, migrated to Act 6 and then Act 10 and that process worked well. Recently, I upgraded both PCs (and our database) from Act 10.00 to Act 10.02. My colleague uses a remote database in a different office and we synchronise over VPN using Hamachi LogMeIn.

Errors on colleague’s PC
Recently, I noticed when my colleague tried to sync Act, the sync process did not complete. When she tried to sync the next day, the sync process did not complete again and she received an error message (on the previous day, it said sync completed on her screen, which is odd).


My colleague also said that she tried to record history against several contacts and Act said it was unable to record history.

Errors on My PC

Error: This contact no longer exists in the database
On the same day as this error on my colleague’s PC, I received an error message: “This contact no longer exists in the database <OK button> ”

Error: Not saving data all the time

1. I added and deleted data in some fields on a test/made up contact, then closed Act and the same error message displayed again. I clicked “OK” and Act closed.
2. Upon re-opening Act and viewing the test/made up contact, none of the field data changes I just made have saved.

Check & Repair
I carried out a ‘check and repair’ and that did not reveal any problems.

Re-installation of Act and SQL Server
I was unable to resolve this issue so I decided to uninstall and re-install Act and SQL Server, and restore a back-up copy of the database from a few days before.

We were able to work and synch Act without issues for several days.

Error Messages Have Re-Appeared
Today, as we were both working, we received the “This contact no longer exists in the database” message again. We are also unable to save data properly to records (sometimes the data saves to fields but most of the time it does not).

ActDiag / SQL Server
I have had a look at the ActDiag and the database instance is listed.

Services.MSC
I have checked services.msc on both PCs and here are the lines which I believe are relevant to Act/SQL Server. Both PCs display the same lines, as follows:
• SQL Server (ACT7): Status: Started, Startup Type: Automatic
• SQL Server Active Directory Helper: Status: <blank>, Startup Type: Disabled
• SQL Server Browser: Status: Started, Startup Type: Automatic
• SQL Server VSS Writer: Status: Started, Startup Type: Automatic

Testing in the Act Demo Database
Having just received the error message I tested the Act demo database today to see if we had the same issue and we did not. I tested all manner of actions e.g. changing data in fields (including the user and home fields etc), adding history, notes, opportunities, creating new contacts, deleting contacts, closing and re-opening Act (and so on). All changes saved without any problems and the error message did not appear.

Potential Solution?
The only joy I’ve had in narrowing this is from this post...

 

...which points to this article on the Act knowledge base:

 

However, I have just been through every single Contact, Company and Opportunity field and I can confirm that no fields have default text longer than their allowed number of characters.

Any Ideas?
Does anyone have any ideas on what this problem relates to and how we can resolve it?

Thanks in advance to anyone who offers help.


Accepted Solutions
Solution
Accepted by topic author drmiller
‎09-25-2015 03:20 AM
Copper Super Contributor
Posts: 87
Country: United Kingdom

Re: Error message in Act 10: This contact no longer exists in the database

[ Edited ]

I'm returning to this because I've just noticed this post and what I thought was the solution, wasn't..

 

In the end, I'm pretty sure I had a data corruption.  Before I found that out, I tried totally re-building the database again (i.e. new database, re-created fields, then imported the data) but that didnt work.

 

When I exported the data and looked at it in CSV format in Excel, there were some odd blank rows with characters in there that shouldnt be.  I can only assume this was a hang over from it being an old Act 6 database.

 

I spent a lot of time going through the CSV file and cleaning it up.  I also used Excel Remove but use this with caution and always save changes under a new file name so you can go back to previous version if you go wrong.

 

When I re-imported the cleaned up data into my new database, I only imported fields that I really had to, rather than importing fields which didnt contain any data (or not much data that I didnt mind losing).

 

I thought I had better post back because I lost weeks of business trying to sort this out and I hope one day, I save someone else the same bother.

Message Edited by drmiller on 09-25-2008 03:48 AM

View solution in original post


All Replies
Copper Super Contributor
Posts: 87
Country: United Kingdom

Re: Error message in Act 10: This contact no longer exists in the database

I have resolved this issue now. I followed the procedures on the Act Knowledge base. Click "Search".

 

Search Product: All

Search Text: 14349

Search by: Article ID

 

I carried out the steps up to and including "Rebuild Sync Objects:" but no further.

Copper Contributor
Posts: 156
Country: USA

Re: Error message in Act 10: This contact no longer exists in the database

Thanks for returning to let everyone know what solved your problem. Smiley Happy
Solution
Accepted by topic author drmiller
‎09-25-2015 03:20 AM
Copper Super Contributor
Posts: 87
Country: United Kingdom

Re: Error message in Act 10: This contact no longer exists in the database

[ Edited ]

I'm returning to this because I've just noticed this post and what I thought was the solution, wasn't..

 

In the end, I'm pretty sure I had a data corruption.  Before I found that out, I tried totally re-building the database again (i.e. new database, re-created fields, then imported the data) but that didnt work.

 

When I exported the data and looked at it in CSV format in Excel, there were some odd blank rows with characters in there that shouldnt be.  I can only assume this was a hang over from it being an old Act 6 database.

 

I spent a lot of time going through the CSV file and cleaning it up.  I also used Excel Remove but use this with caution and always save changes under a new file name so you can go back to previous version if you go wrong.

 

When I re-imported the cleaned up data into my new database, I only imported fields that I really had to, rather than importing fields which didnt contain any data (or not much data that I didnt mind losing).

 

I thought I had better post back because I lost weeks of business trying to sort this out and I hope one day, I save someone else the same bother.

Message Edited by drmiller on 09-25-2008 03:48 AM