Tips & Tricks from Linda

I have been received the error "HTTP 400, bad request" when calling Azure Push Notification initialised function for few days. It was working fine previously and I didn't change any configuration on it. I checked the "diagnostics logs" in Azure Mobile App service and found the issue related to below error message. Could not load file or assembly 'Newtonsoft.Json, Version=8.0.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040) I researched above issue in Google and then updated the latest version of "Newtonsoft.Json" in my Azure Mobile App .NET back-end application. The issue was gone and I can calling Azure Push Notification service in my mobile App successfully!

 I had been received an error when  try to add a new record to Azure SQL table via Mobile App service in a mobile app as below: StatusCode: 400, ReasonPhrase: 'Bad Request', Version: 1.1, Content: System.Net.Http.StreamContent, Headers:  400 Bad request" I verified the SQL table and even can manually insert a record on there. Suddenly, I realized that an error " System.Data.SqlClient.SqlException (0x80131904): Cannot create more than one clustered index on table" was showing when created this table in Azure Mobile .Net back-end. Generally, this error message is caused that Entity Framework does not have an annotation for creating a clustered index that is not a primary key, so the mobile server SDK manually creates the right SQL statements to set CreatedAt as a non-primary key clustered index. To resolve this, In the Migrations\Configuration.cs file, include the following lines: public Configuration() {    AutomaticMigrationsEnabled = false; ...

I have been worked on a CMS Portal project in SharePoint 2013 platform and needed to create a lots of forms and landing pages. The stake holder needed to review and change frequently of the heading, messages, and column headers on the application pages, and so I am thinking to separate the labeling / contents from the code which the similar approach as Sitecore to save and retrieve word values in model's fields and then loading them to front-end pages. SharePoint provides some features to achieve showing dynamic contents as below methods: 1. Using SharePoint List I used a SharePoint list to save Label and message text values and then loading them dynamically in SharePoint WebParts. The benefit of this approach is giving user to update label/contents more easier without updating the source code. It increases the work efficiency. In some case, there will be multiple site collection needs to share data from the same SharePoint list. This causes cross domain call issue in jQu...

I met the issue "String was not recognised as a valid DateTime" when I executed the code which using " DateTime.Parse(strdate)" to convert the string value with date format "01/03/2016" (Australian date format) in a SharePoint 2013 site.  The code is executed successfully in another SharePoint environment, and so I verify the "Regional settings" in this SharePoint site, and found out the "Time zone" settings is correct which set to "Sydney" time zone and the "Locale" settings was set to "English (United States)" which is incorrect, and so I change the "Locale" settings to "English (Australia)". I refresh the WebPart Page again, and the issue was gone!

I had been received a error message " Application error when access /_vti_bin/client.svc, Error=Path '/_vti_bin/client.svc/ProcessQuery' is forbidden " when try to add user account to a user group in SharePoint 2013 Portal . I searched the issue in google and found out it may related to security issue in local folder  "C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\ISAPI" of " /_vti_bin/client.svc ". I verified the user permission on this folder and found out that "IUSR" for IIS is not there, and so I granted user account "IUSR" read and execute permission in this folder. I went back to try add user account in SharePoint again, and it worked successfully this time! This issue is related to error "The server was unable to save the form at this time. Please try again." which can be resolved using above configuration. In addition, if this error still occur, check the windows features in con...

I try to import a Excel 2013 spreadsheet to SQL Server 2012 Database and received above error message. I installed below component "2007 Office System Driver: Data Connectivity Components" (https://www.microsoft.com/en-us/download/details.aspx?id=23734) and then try the import again. Works fine!