In this webinar, our experts showcase a variety of demo use cases of how different components of the...
Microsoft Dynamics CRM 2015 Update 0.1 has been released for on premise customers. This includes a number of small enhancements and minor fixes. For a complete list of what is included please go here:
https://support.microsoft.com/en-us/kb/3010990
Should you update?
At this time, there is a potential issue with importing backups of existing organizations. We recommend that you do not install the update if importing backups is a critical function of your organization.
Understanding the Issue
After the update, in Deployment Manager, when importing backups or copies of any CRM organization you may see this error: Could not find stored procedure 'p_CreateAuditEntry'
This error is contained in the log file:
16:28:30| Error| Error while updating organization information: System.Data.SqlClient.SqlException (0x80131904): Could not find stored procedure 'p_CreateAuditEntry'.
at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, Boolean callerHasConnectionLock, Boolean asyncClose)
Solution
We have a ticket open with Microsoft and are working on a workaround and will post here as soon as one is found. In the meantime, if importing backups of existing organizations is a critical function in your existing process we recommend delaying installation of Update 0.1 for Microsoft Dynamics CRM 2015.
Happy CRM'ing!
You can find a Workaround in this thread:
CRM 2015 - Error after update 0.1: https://community.dynamics.com/crm/f/117/p/158085/377185
Hi Patrick - Thanks for sharing. The above thread is a similar issue, but a different issue. Our issue appears to be a missing procedure [dbo].[p_CreateAuditEntry]
We have a fix appears to work from microsoft and are waiting confirmation this is the best fix before we update our blog with the fix.
Has Microsoft gotten back to you yet? We're having the same issue, but I haven't found any other information or posts.
Hi - we are still waiting for permission to post here. I'll send you an email with a bit more info.
I'd love to know the fix too. I just opened a case with Microsoft for the issue as well!
Still waiting for permission to share here, but i sent you an email with info.
can you send it to me too?
Hi - info on its way. Log a ticket and reference our ticket so this gets elevated in the priority list of fixes.
Hi Joe,
I encountered the similar issue, can you please send me the information as well?
I'll raise the ticket afterwards.
Hi Joe
would be great to receive the information. Can you please send it to me as well?
Thank you very much.
Urs
Joe - would you mind sending me the info for this? Same issue. Thanks!
Hi Joe- any chance you could share the solution?
Sorry to be a pain, but could I get this as well?
On its way.
Thank you, was very much appreciated! (Fixed our issues, very happy)
Could I get this fix too.. please
Hey Joe, mind sending me an email too, i'm kinda stuck.
Hi Joe, any chance I could get an email with the fix for this issue? Thank you!
So we have a potential work around and so far working great. We can import orgs again. We are waiting the OK to post it here.
Can you please let me knw the workaround?
Hi Joe, would you be able to send the workaround? Thanks!
It looks like as if I figured out a (nasty) workaround.
I had to create the two procedures below on the MSCRM_CONFIG(!) database.
I got them from CRM2015-Server-KB3010990-ENU-amd64.execonfigdb.cabconfig5.0StoredProceduresAuditHistory but I had to drop the procedure content because they are inserting/updating to a table AuditHistory which I don't have.
For me it looks like as if the procedures are called accidentally during the update.
if exists (select * from sys.objects where name = 'p_CreateAuditEntry' and type = 'P')
begin
drop procedure p_CreateAuditEntry
end
go
create procedure p_CreateAuditEntry (@AuditEntryId uniqueidentifier,
@ObjectId uniqueidentifier,
@ObjectType nvarchar(40),
@Operation nvarchar(40),
@Details nvarchar(max),
@UserName nvarchar(40)) as
begin
set nocount on
end
go
if exists (select * from sys.objects where name = 'p_CompleteAuditEntry' and type = 'P')
begin
drop procedure p_CompleteAuditEntry
end
go
create procedure p_CompleteAuditEntry( @AuditEntryId uniqueidentifier,
@Result int,
@Details nvarchar(max)) as
begin
set nocount on
end
go
Same problem here.
Harald's solution resolved the problem for me.
Bit nervous about some of the quality issues we're seeing with OnPremise. Seems every release/rollup has some major issue with solutions import and/or something else major. The inability to restore from a backup would I'd imagine be a showstopper for every organisation - this workaround means we can continue with the rollout.
Thanks.
Thank you Harald! This worked for me as well. Really looking forward to the official solution as well, although I guess we'll just have to wait for Update 2.
I actually don't think the procedures are called accidentally, but they're probably being called on the wrong database (CONFIG instead of actual Org DB).
Thank you Harald! This worked for me as well. Really looking forward to the official solution as well, although I guess we'll just have to wait for Update 2.
I actually don't think the procedures are called accidentally, but they're probably being called on the wrong database (CONFIG instead of actual Org DB).
You Rock Harald!
I'm also interested in the fix...when will it be shared publicly?
I also have the same Problem. Any chance of getting the work around info?
Happy to create a ticket with MS also but could do with some quick fix infromation
Is there any update on this?
It is now official that the update will be included in update 0.2 for crm on prem. No eta yet on a release date.
Any information about this error ?
Any information about this error ?