David

I ge a similar message saying cannot clean up activity table. I logged an
issue with great plains and was told they are aware of it but for now its
fine to ignore it


"DavidQ-DQ" <davidqdc@NOSPAM.lycos.com> wrote in message
news:00cf01c34d3e$858e4330$a101280a@phx.gbl...

"John O'Donnell" <csharpconsulting@hotmail.com> wrote in message
news:ewvhM8TTDHA.2676@TK2MSFTNGP10.phx.gbl...
There is a known issue (deleting activities) specifically deleting an
activity that has an attachment. CRM does not delete the attachment, but
wants to delete the activity, but there is a dependency on the attachment,
so the activity cannot be deleted. They do not list a specific work-around,
just a way to confirm this scenario exists

here is the response i got

I did a bit more digging and found that the errors you're seeing:

1. are an issue at the platform level and being looked at by our development
team to resolve the errors.

2. do not affect the operation of the Microsoft CRM application.


"Glen Cook" <g.cook@epicmail.ca> wrote in message
news:#VO0hEUTDHA.560@TK2MSFTNGP10.phx.gbl...

lastly

i was pointed at this tech article although i do not think it is relevant in
this case...

Issue

Error - "Select permission denied on MS Distributor_Access Database Temp DB
Owner DBO" occurs on the synchronization windows when trying to go offline
with the Microsoft CRM Sales for Outlook client.

I also see the following error has started showing in the event log every 2
hours:

Event Type: Error
Event Source: MSCRMDeletionService
Event Category: None
Event ID: 5895
Date: 3/13/2003
Time: 5:43:08 PM
User: N/A
Description:
Error: Can't clean up the following tables: Activity.

Resolution

Enable the Cross DB Ownership Chaining within SQL Server. You will only
have this option on SQL Server 2000 with SP3.

1. Open SQL Enterprise Manager by navigating to Start | Programs | Microsoft
SQL Server | Enterprise Manager.

2. Expand Microsoft SQL Servers | SQL Server Group.

3. Highlight your server, right click, and select properties.

4. Select the Security tab. Mark the checkbox to allow cross database
ownership chaining if it is not already marked.

5. Retry the offline synchronization.

Note - Use the Cross DB Ownership Chaining option to configure
cross-database ownership chaining for the instance of SQL Server. This
security enhancement was added in SQL Server 2000 SP3 to allow you to manage
cross-database security.

For more information on Cross DB Ownership Chaining refer to the section on
Cross DB Ownership Chaining within SQL Server Books Online (updated SP3).












"John O'Donnell" <csharpconsulting@hotmail.com> wrote in message
news:u#foUIUTDHA.1664@TK2MSFTNGP11.phx.gbl...