Community
Showing results for 
Search instead for 
Do you mean 
Reply

Create a new opportunity problem

Accepted Solution Solved
Copper Super Contributor
Posts: 73
Country: USA
Accepted Solution

Create a new opportunity problem

Hi,

 

We are using ACT! Premium V16.2. Our system was working fine, but it just shows this message when all the users atempt to create a new Opportunity, and assign it to a contact. It is not possible to save any new opportunity.

 

Capture.PNG


Accepted Solutions
Solution
Accepted by topic author paymanzafar
‎09-25-2015 03:20 AM
Copper Super Contributor
Posts: 73
Country: USA

Re: Create a new opportunity problem

The problem is resolved.

 

We had a trigger on SQL database. We removed it, and there is no more proble.

View solution in original post


All Replies
Platinum Elite Contributor
Posts: 6,663
Country: USA

Re: Create a new opportunity problem

That isn't a friendly message. It could indicate a problem with the ACT! program but it's more likely a problem with the actual database. If you can, open the ACTdemo database and try the same operation. If it works then the problem is with your database. Try running database maintenance on the database in the ACT! program. You can also try the database repairs in ACTdiag. If those don't work, you'll need to contact a database repair service, either the one provided by Switpage or one of the ACCs, including Techbenders.

Roy Laudenslager
ACT! Certified Consultant
ACT! Report Expert
Durkin Impact Report Designer
www.techbenders.com
royel@techbenders.com
541-343-8129
Copper Super Contributor
Posts: 73
Country: USA

Re: Create a new opportunity problem

Thank you very much.

 

It works with other databases. I used the database repair, and re-index tools inside ACT!, and also checked database with ActDiag. But there was no success.

Solution
Accepted by topic author paymanzafar
‎09-25-2015 03:20 AM
Copper Super Contributor
Posts: 73
Country: USA

Re: Create a new opportunity problem

The problem is resolved.

 

We had a trigger on SQL database. We removed it, and there is no more proble.