EDI error after installing BizTalk 2006

Software: BizTalk 2006

Soon after doing a fresh insallation of BizTalk 2006 I noticed the following error that kept appearing in the system event log:

---

Error encountered: ERROR (120) :
An error occurred in the File System connector. Check the details.Cant make a connection to \\SRV01\EDIDocsHome\Documents\PickupEDI. Errormessage: The operation cannot be performed because a network component is not started or because a specified name cannot be used.Foldername: \\SRV01\EDIDocsHome\Documents\PickupEDI, Errormessage: The operation cannot be performed because a network component is not started or because a specified name cannot be used.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

---

To get rid of this error, open Properties for the specified folder (by default \\SRV01\EDIDocsHome points to C:\Documents and Settings\All Users\Application Data\Microsoft\Biztalk Server 2006\EDI\SubSystem), switch to Security tab and give EDI Subsystem Users group full access to the folder.

Hash tools

Hash calculator: http://johnmaguire.us/tools/hashcalc/

Search millions of hashes (MD5, SHA1): http://md5.rednoize.com/

XSLT Tester

Nice XSLT tester:

http://www.perfectxml.com/xsltester.asp

Getting rid of the "An unexpected error has occurred" message

While trying to deploy a SharePoint web site to a server I've seen the following error a lot of times:

---

An unexpected error has occurred.

Troubleshoot issues with Windows SharePoint Services

---

With no error diagnostics given whatsoever, it makes hard to find what's causing the bugs and fix them. However I've been able to find out how to make SharePoint to become a little more wordy.

For your site find all available web.config files and make sure the following options are set in all of them:

<configuration>
  <SharePoint>
    <SafeMode MaxControls="200" CallStack="true" AllowPageLevelTrace="true">

...

  <system.web>
    <customErrors mode="Off" />

    <compilation batch="false" debug="true">

Once you do that, you'll start getting the complete ASP.Net diagnostics page instead of the generic error.

Also, when configuring WCF client, make sure to specify includeExceptionDetailInFaults option in the client's configuration file. For example:

<system.serviceModel>
  <behaviors>
    <serviceBehaviors>
      <behavior name="BlahBlah.Services.ServiceImplementation.Community_Behavior">
        <serviceDebug includeExceptionDetailInFaults="true"/>

Commenting HTML code with .Net server controls

Software: .Net Framework

Here's how to comment out sections of HTML code containing .Net server controls:

<%-− blah-blah −-%>

Regular comments (<!-− blah-blah −->) don't work (or work incorrectly) for sections containing server controls.

Changing Remote Desktop listening port

Remote Desktop (former Terminal Services) listening port is defined in registry:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\TerminalServer\WinStations\RDP-Tcp\PortNumber

Redirect using IIS, with query string

Suppose you want to redirect "http://raxxla.com" to "http://www.raxxla.com". In IIS create a new web site for the URL you want to be redirected ("http://raxxla.com"). On the Home Directory tab of the site's properties page, select A redirection to a URL radio button and specify destination URL ("http://www.raxxla.com"). At this point redirection will occur but query string will be lost (i.e. e.g. "http://raxxla.com/Journal.aspx?blogid=2" will be redirected to "http://www.raxxla.com". In order to enable redirection that keeps query string specify the following as destination URL:

<your URL>$V$Q

In our case,

http://www.raxxla.com$V$Q

Query string will be preserved while redirection.

Courtesy this.

More info on all suported parameters that can be used in redirection URL.

SharePoint: How to enable/disable content based on security context

<Sharepoint:SPSecurityTrimmedControl AuthenticationRestrictions="AuthenticatedUsersOnly" runat="server">

… Everything here will be displayed to authenticated users only. Other users won't see anything.…

</Sharepoint:SPSecurityTrimmedControl>

There are other handy uses of SPSecurityTrimmedControl. Refer to Microsoft documentation.

Good email regexp

^([\w\-\.]+)@((\[([0-9]{1,3}\.){3}[0-9]{1,3}\])|(([\w\-]+\.)+)([a-zA-Z]{2,4}))$

via Regexlib.com

Blocked Internet traffic while on VPN connection

When you connect to a remote network through VPN, sometimes it blocks other internet traffic. For example, Skype or ICQ may stop working. Other Internet aplications may still work but somewhat slow. The reason for that is that while on VPN, all of your Internet traffic goes through the remote network. That network's firewalls may have some ports closed for security reasons. To avoid streaming all the traffic through the remote network and still seeing the network's servers, do the following:

Open the properties for the VPN connection -> Networking tab -> Internet Protocol TCP/IP -> Properties -> Advanced -> General Tab -> uncheck the "Use default gateway on remote network". It will put all the things with local internet in order. Click OK for 3 times and reconnect the VPN.

Courtesy one of my collegues Anton.

CAML queries issues

Software: Microsoft SharePoint

Got this message when trying to access a SharePoint list in C# code using CAML query.

One or more field types are not installed properly. Go to the list settings page to delete these fields.

The problem was that names of fields that are to be used in CAML queries are SharePoint internal ones. Not what you see in any list configuration screens. Quite often internal names differ from displayed ones. For example, if displayed name contains a space (e.g. "Tab Order"), internal name will have "_x0020_" in place of the space character ("Tab_x0020_Order"). Another reason why internal and displayed names differ is that when you rename a field, its internal name doesn't change. Period.

To get to know what the internal name of a field is, go to its edit screen and do the View Source thing in browser. Somewhere in the code (usually close to the opening tag) there's internal name. Also internal name, though somewhat altered, can be found in the URL of the field edit screen. It's altered because "_"'s are replaced with their encoded version. For example, this part of the URL:

... Field=Key%5Fx0020%5FOrder

really means that internal name of the field is "Key_x0020_Order".