In these days I worked on a strange issue: after migrating a CRM 2011 organization, English base Language with Italian Language pack, to CRM 2013, if you try to create a new appointment this error is raised:

the issue is still under investigation but it can be fixed resetting for every user the Formats setting: Navigate to the Personal Options->Formats->Choose italian -> Customize... -> push Reset button.

There is a shorter but UNSUPPORTED way to fix this issue : changing this setting manually modifying the organization database in which the issue appears by running a T-SQL script.

The script is not intended to be used into a production environment without a full test and a full backup of both the organization (ORGANIZATIONNAME_MSCRM) and configuration (MSCRM_CONFIG) databases: it's provided only as an example and here it is:

 

use ORGANIZATIONNAME_MSCRM

declare @ModifiedBy1 char(36)

declare @ModifiedOn1 char(19)

declare @SystemUserId1 uniqueidentifier

set @ModifiedBy1 = 'PUT_HERE_THE_GUID_OF_AN_ADMINISTRATOR'

set @ModifiedOn1=CURRENT_TIMESTAMP

declare CustList cursor for select SystemUserId from SystemUserBase where SystemUserId <> @ModifiedBy1

open CustList

fetch next from CustList into @SystemUserId1

while @@FETCH_STATUS = 0

begin

       exec sp_executesql N'update [UserSettingsBase] set
[DateFormatCode]=@DateFormatCode0, [NumberGroupFormat]=@NumberGroupFormat0,
[ModifiedOnBehalfBy]=NULL,

      
[NegativeCurrencyFormatCode]=@NegativeCurrencyFormatCode0,
[TimeFormatCode]=@TimeFormatCode0, [DateFormatString]=@DateFormatString0,
[TimeSeparator]=@TimeSeparator0,

      
[TimeFormatString]=@TimeFormatString0, [NumberSeparator]=@NumberSeparator0,
[CurrencyFormatCode]=@CurrencyFormatCode0, [CalendarType]=@CalendarType0,

      
[LongDateFormatCode]=@LongDateFormatCode0, [ShowWeekNumber]=@ShowWeekNumber0,
[ModifiedBy]=@ModifiedBy0, [DecimalSymbol]=@DecimalSymbol0,

      
[NegativeFormatCode]=@NegativeFormatCode0, [ModifiedOn]=@ModifiedOn0,
[DateSeparator]=@DateSeparator0 where ([SystemUserId] = @SystemUserId0)',N'@DateFormatCode0 int,

      
@NumberGroupFormat0 ntext,@NegativeCurrencyFormatCode0 int,@TimeFormatCode0
int,@DateFormatString0 ntext,@TimeSeparator0 ntext,@TimeFormatString0 ntext,

       @NumberSeparator0
ntext,@CurrencyFormatCode0 int,@CalendarType0 int,@LongDateFormatCode0
int,@ShowWeekNumber0 bit,@ModifiedBy0 uniqueidentifier,@DecimalSymbol0 ntext,

      
@NegativeFormatCode0 int,@ModifiedOn0 datetime,@DateSeparator0
ntext,@SystemUserId0 uniqueidentifier',@DateFormatCode0=3,@NumberGroupFormat0=N'3',

       @NegativeCurrencyFormatCode0=9,@TimeFormatCode0=0,@DateFormatString0=N'dd/MM/yyyy',@TimeSeparator0=N'.',@TimeFormatString0=N'HH.mm',@NumberSeparator0=N'.',

       @CurrencyFormatCode0=2,@CalendarType0=0,@LongDateFormatCode0=1,@ShowWeekNumber0=0,@ModifiedBy0=@ModifiedBy1,@DecimalSymbol0=N',',

       @NegativeFormatCode0=1,@ModifiedOn0=@ModifiedOn1,@DateSeparator0=N'/',@SystemUserId0=@SystemUserId1

 

       fetch next from CustList into @SystemUserId1

end

close CustList

deallocate CustList

 

To run this script you can start SQL Server Management Studio and open a new query window to be executed into the organization database (ORGANIZATIONNAME_MSCRM).

Please note also that we are working for providing a full supported fix.