Hello, good morining,
We have Sales Logix 7.5.2.2151 implemented for several years now, since this monday we started to get this error message every time we complete a task.
An unusual error has occurred when executing Schedule:CompAct. Contact your system administrator. 0x1 @0: Function
Schedule:CompAct Exception:
Exception EOleException:
Row cannot be located for updating. Some values may have been changed since it was last read
Exception location:
[00546651]{SalesLogix.exe}

do you have any ideas of what should I be looking at to correct this probelm?

Thanks in advance,
Gaby Ramos

Is this error ocurring for all users and all Activities?

I have ran onto a similar issue with Modify Dates that happened near  the Start or End of DST (within XX hours where XX = your GMT Bias) (The conversion was not being applied correctly, thus the values would not match when the update was sent in).

In that case, i had to "manually" alter those records.

If this is happening to all users, all record (or if you could easily reproduce this issue), I would suggest you use the SLX Profiler to capture the Statement that is failing, then compare to the Data and determine what is making it not find the row.

To give some additional light, whenever SLX reads a record, it stores the ModifyDate of the record, so when it sends an update, it includes the ModifyDate on the Where clause to make sure that the record hasn't been updated by someone else. If for some reason someone else did update the record, then you would get this error. Also, in a weird case like the one I outline above.

Also, triggers on the Tables may cause similar issues (if they modify the Row Count returned).

For example, if I modify the Account Type, the Update statement may look something like this:

UPDATE ACCOUNT SET TYPE = 'New Type' WHERE ACCOUNTID = 'XXXXXX' AND TYPE = 'Old Type' AND MODIFYDATE = 'The Previous Modify Date'

As you can see, if the data had been modified, and the Type value or Modify Date no longer match, then you would get the error.

Also, if for some reasons you have Triggers in place, and it causes the Statement to return anything other than "1" as the Record Affected Count it would cause the same problem.

Now, there may be other factors that come into play here (Outlook integration of some sorts: IntelliSync, ExchangeLink, etc.) but you need to first figure out if indeed the data is changing and then try to chase what is making it change.

Thanks Raul, i suspected DST might be the issue but this is the first year that is happening so i didn't really look into this.

Your explanation is perfect. We are gonna work with the SLX Profiler, and find out which records are generating this error.

About your question, Yes, its happening to every user and every Activities, on Monday started with some users and some contacts now is every user, every contact.

I'll keep you posted.

Thanks again,

Gaby

I have face just the same error.

I updated the field LASTHISTORYDATE from the table Account, just as Raul said and that works for me.

Checking with SLX Profiling, we realized that the problem was the field LASTHISTORYDATE at Account table, we updated the field with the same date but with an hour earlier and that was it. Start working again

Thanks for your help!

Gaby

So is there any way to proactively avoid this from happening again the next time DST changes?

So is there any way to proactively avoid this from happening again the next time DST changes?

hmmmm you've been on the same version of SalesLogix for years.....there have been dozens of updates, upgrades, and version releases.....
and it's March 2013....

This occurs when fields have directly connected to the database and tables in a 1:1 or 1: n no identifier or ID.

Greetings.

---

Esto ocurre cuando tienes campos conectados directamente a la base de datos y en alguna de las tablas 1:1 o 1:n no existe el identificador o ID.

Saludos.