Tech Support > Microsoft Windows > Windows CRM > Publishing and subsequent iisresets changed database records...
Publishing and subsequent iisresets changed database records...
Posted by Paul on April 28th, 2005


Hi,

Just a quick question, can a subsequent iisresets and publishing of
customizations during office hours change/alter database records in CRM? To
be specific, below are the details:

1. The IT Admin did a customization on Case forms.
2. He then published it and did subsequent iisresets during office hours
when users are still logged on to CRM.
3. During this time, a CRM user reported a "General network error", but this
only happened ones.
3. After the publishing of the customization, 2 CRM users who previously
owns 800+ & 1000+ records, now owns only 13 records each.

Now, given this scenario, something must have happened in the background. No
trace in the logs either except for the MSCRMDeletionService error. I have
also checked the customization XML file and no inconsistencies there.

Here are some facts that could also be helpful:
1. A CRM user at that time is doing some record assignment (account
assigning) to a specific group of records.

Any insights on this? or any theories you can come up with that could cause
this error?

I would really appreciate if you could help me on this...

Thanks!

Cheers,


Posted by John O'Donnell on April 28th, 2005


1 - no problem here
2 - still no problem although you should try to do updates out of office
hours. However CRM does not maintain state so you can issreset without issue
3 - this occurred because the user was accessing crm in the middle of an
iisreset

1. A CRM user at that time is doing some record assignment (account
i think the above statement is the issue. Did this user have access to the
records that the other users say have disaapeared?

--
John O'Donnell
Microsoft CRM MVP
http://www.mscrmfaq.us


"Paul" <Paul@discussions.microsoft.com> wrote in message
news:B1921132-71DA-4534-A1D5-03F44857A1D5@microsoft.com...


Posted by Dave Carr (dave- no spam-@vscrm.com on April 28th, 2005


Paul,

The only way that users can "lose" records as you've described is if
either (a) somebody reassigned them, or (b) a change to a role (any
role) was made.

All access to all records (thankfully, this will go away in CRM v2.0)
is done using the securitydescriptor field. When you change a role,
CRM, behind the scenes, in a process that can take hours, and cause
performance problems, updates all security descriptors in any affected
tables.

These secruity descriptors determine who can see each record. And
unfortunately there is no way to manually tell if these descriptors are
correct. MS Support has a tool that they can run to re-set/re-create
all secruity descriptors. So if this continues to be a problem for no
apparent reason, I'd log a call.

HTH,

Dave
-------------------------------------------------
David L. Carr, President
Visionary Software Consulting, Inc.
Main #: 971-327-6944

Introducing our newest software product...
VAST - an auditing solution for Microsoft CRM 1.2
VAST shows you "Who Did What When" in Microsoft CRM
To download our free trial, get more info, or to order, visit
http://www.VSCRM.com