Anith Gopal

I’ve seen a few people get confused over what this error message in the Reporting Services log file indicates. This message is generated when the Reporting Services web server detects that an HTTP request has experienced a remote disconnect.  In practice, this means that we queried the property HttpResponse.IsClientConnected and it returned false. So how does this work exactly, and are all requests subject to this kind of check?

One of the biggest puzles of inconsistency is keeping a page that using Lookup column uptodate to all the changes that happened to underlying list. Image you have a web page in a Documents library.

This article outlines some of the features in the new version of Exchange.

With Dynamics AX 2009 it is getting more appropriate to have the AOS and .NET Business Connector installed on a 64bit version of Microsoft Windows Server as both components are shipped also as 64bit (x64) versions. The Dynamics AX 2009 Client is however still a 32bit (x86) application

And I’m back, yeeeee!!! It is really nice to see the sunlight again… oh wait, there is not much sun around Seattle J . Well anyhow, specifications for the features that I’m driving in our next milestone are done and I’ll finally had the chance to reconnect with the outside world he he, time for devs to go dark And to celebrate my return let me post something that I’m sure many CRM developers have wondered about. Why are plug-ins for the associate/disassociate   (N:N relationships) not supported

Durante o processo de criação de soluções utilizando o SharePoint, existem algumas situações nas quais precisamos de uma customização maior e criar nossos web parts.

By default, the WCF values for maxBufferSize and maxReceivedMessageSize are both 65536 (64K). If you send a request to a document service in Microsoft Dynamics AX and the message size exceeds this value, you’ll see a cryptic error that says something like: “The remote server returned an error: (400) Bad   Request.” You may also see an error message that references the maxReceivedMessageSize property.   To fix this problem, increase the binding properties maxBufferSize and maxReceivedMessageSize

Of all the types of spam that make use of deception (ie, all of them), the most damaging of all of them are phishing messages.  Phishing messages are when a spammer impersonates a legitimate entity — a form of reputation hijacking — in an attempt to trick the user into giving up personal information like banking information.  The phisher then uses the information in order to steal money from the victim. So how do you recognize a phish?  Microsoft has a good description on this.  Below is a screen shot of a sample message: A good phish (and even a bad one) takes the form: A bank or financial institution.  Phishes come from banks or online financial institutions like Paypal or eBay where money can change hands. Your account has been compromised or is about to expire

SPSite mySite = new SPSite(“<SiteURL>”); SPWeb myWeb = mySite.OpenWeb(); SPFolder myList = myWeb.Folders["<DocLibName>"]; SPFile myFile = myList.Files[0]; SPUser myUser = myWeb.Users["<User_Name>"]; CheckInFileByUser(myFile, “Checkin Comments”, SPCheckinType.MajorCheckIn, myUser); public static void CheckInFileByUser(SPFile file, string checkinComment,SPCheckinType checkinType,SPUser modifiedByUser) { MethodInfo mi = typeof(SPFile).GetMethod(“CheckIn”,BindingFlags.Instance | BindingFlags.NonPublic, null, new Type[] { typeof(string), typeof(SPCheckinType), typeof(bool), typeof(SPUser) }, null); try { mi.Invoke( file, new object[] { checkinComment, checkinType, false, modifiedByUser });   }   catch (Exception ex) { MessageBox.Show(ex.StackTrace); } } Before calling this code you will need to Check out the file, otherwise you will get an error.    

Here  I talked about a technique to convert SOAP faults into JSON objects for AJAX scenarios. The post was primarily around using WCF extensibility to send back exception details as JSON object with a particular HTTP status code . The code will only works with native XMLHttpRequest object or with a library which returns bare HTTP response (Ext JS, jQuery etc)

MSDTC is the important Transaction service on window system. COM+ system, or other OLE/XA resource managers (such as SQL, MS Oracle client) heavily depend on it.   If the MSDTC doesn’t start, when we open Component Service UI or try to create transaction, will get similar error messages as below:   a

Cela fait des années que j’utilise Outlook Thread Compressor. Jusqu’à récemment, cet outil n’était disponible qu’en interne, chez Microsoft