Well, an installation with no asyncservice running, though it is running(!)
Here in start December I am working on an installation made in February 2009. Created som entities, changed some attributes, adding relationshipsand modifying isv.config and sitemap. So far so good.
Then implemented some simple workflows including some CustomWorkflow Activities. Didn't run as intended. Just waiting statement in progress status.
Tried a simple workflow just updating an attribute when executed. Didn't run. Just waiting.
Looked at systemjobs and noticied that a duplicate job was paused since June.....
But no errors in eventlog.
Installed the rollup7 .....
And everything worked.
Well, i must say that 4.0 is becoming more and more stable. With rollup7 a lot of bugs are fixed and services runs more solid.
So if you haven't updated the server to rollup7 you might want to do that if you experience problems.
THEN AGAIN- Concider twice before doing this. There are someissues with the clients. In Citrix environments users may give that the reason, but I see it on windows 7 with Office2007. CRMClient stopsand you have to close down and open Outlook a couple of times to get all services and the add-in running again.
Monday, December 7, 2009
Monday, November 30, 2009
Can't publish entities in CRM 4.0?
I have been frustrated that from time to time the form, view and entity xml har caused some sort of inconsistency in an instance of an organization nin CRM 4.0.
A colleegue of mine followed this blog post and solved the issue. This will save us a lot of time in future trouble shootings. Post is found at http://blogs.salentica.com/direland/2009/04/16/a-hitchhikers-guide-to-transporting-schemas/
In our case the reasons to this issue were too many cook's. So at some point somebody changed the schema and somebody else (or the same person) imported a partial set of customizations. And schema did not match the form xml. A field on form had an emty string reffering to a non existing attribute on a related attribute.
The blog post was followed step by step and solved the issue.
As a result of this knowledge the future procedures in our company is to have a full backup of databases restored into a new database at the sql server hosting crm databases. Then creating a new organization by importing an organization instead of first creating and then make a full import of cust's will prevent this issue if we keep the newly created organization as the master organization and only deploy from master to live.....
Hope this post will make the issue and the resolution more visible to other fellow customizers in the future.
A colleegue of mine followed this blog post and solved the issue. This will save us a lot of time in future trouble shootings. Post is found at http://blogs.salentica.com/direland/2009/04/16/a-hitchhikers-guide-to-transporting-schemas/
In our case the reasons to this issue were too many cook's. So at some point somebody changed the schema and somebody else (or the same person) imported a partial set of customizations. And schema did not match the form xml. A field on form had an emty string reffering to a non existing attribute on a related attribute.
The blog post was followed step by step and solved the issue.
As a result of this knowledge the future procedures in our company is to have a full backup of databases restored into a new database at the sql server hosting crm databases. Then creating a new organization by importing an organization instead of first creating and then make a full import of cust's will prevent this issue if we keep the newly created organization as the master organization and only deploy from master to live.....
Hope this post will make the issue and the resolution more visible to other fellow customizers in the future.
Subscribe to:
Posts (Atom)