Durron's Blog

Server is not configured for RPC

2010-05-05T12:38:00Z

Problem: Backup maintenance job for BizTalk 2006 R2 On a Microsoft SQL Server 2005 installation with a linked server configured to another sql server instance fails with error:

Msg 7411, Level 16, State 1, Procedure sp_BackupAllFull, Line 70
Server 'sql01\other' is not configured for RPC.

Solution: Problem is most likely that RPC is not configured for your linked server. That is not a default option, after all. You can see what settings are configured with exec sp_helpserver.

If 'rpc,rpc out' is not in your results, then the the linked server isn't configured for RPC.To do so:

exec sp_serveroption @server='myserver', @optname='rpc', @optvalue='true' exec sp_serveroption @server='myserver', @optname='rpc out', @optvalue='true'

Another way to see what the settings are is to go to the management stuio console open in the left panel the "server objects" -> "linked servers" and right click on the server and click on properties.

If you want to change the RPC settings you can set the 'rpc' and rpc-out' property true.

Installing BizTalk server 2004

2008-09-05T09:58:00Z

When you are planning to install a new BizTalk server 2004. These two URL's are very useful.

http://geekswithblogs.net/evega/articles/12865.aspx

http://geekswithblogs.net/evega/articles/12870.aspx

Regards,
Harmjan

BizTalk Tools and guidelines

2008-04-10T08:48:00Z

Yesterday I was reading about guidelines for biztalk so I thought let’s look on the internet wath other BizTalk developers or designers has made. So I found a blog of Kishore Dharanikota. Kishore has created a nice list of tools and guidelines BizTalk Tools and guidelines.

Regards,
Harmjan

A failure occurred while attempting to start the compilation

2008-03-18T17:31:00Z

I received the following error: "A failure occurred while attempting to start the compilation" When I searched msdn for an answer I got this:

http://msdn2.microsoft.com/en-us/library/zz9wwbfa(VS.80).aspx?topic=306132

An unknown error has been encountered while issuing the Start Build request to the Visual Basic or Visual C# compiler.

To correct this error

Restart Visual Studio.

But the real problem was because the compiler can't delete the previous output (read-only files) I received this error. Just so simple.

Regards,

Harmjan

Check out files when a newer version is already available

2007-11-02T15:09:00Z

Today I received the question how you can receive a pop up messege when you try to check out some files when a newer version is already on the server.
When you work with VS2003 and TFS it is possible to perform an get latest version when you try to check it out. I try to explain it:

Jan check out file 1
Jan changes the file and check in
Harm has the old version of file 1
Harm checks out file 1

Under 2003 this may (only when you set the options to do this) would have brought the latest version of the file from the server to Harm's machine and checked it out to him. But microsoft used there brains and deleted this option in TFS. Because you’re workspace is not a correct building solution anymore when you get only one latest file and not the whole solution.Doug Neumann from microsoft explains the reason behind it:

It turns out that this is by design, so let me explain the reasoning behind it. When you perform a get operation to populate your workspace with a set of files, you are setting yourself up with a consistent snapshot from source control. Typically, the configuration of source on your system represents a point in time snapshot of files from the repository that are known to work together, and therefore is buildable and testable.

As a developer working in a workspace, you are isolated from the changes being made by other developers. You control when you want to accept changes from other developers by performing a get operation as appropriate. Ideally when you do this, you'll update the entire configuration of source, and not just one or two files. Why? Because changes in one file typically depend on corresponding changes to other files, and you need to ensure that you've still got a consistent snapshot of source that is buildable and testable.

This is why the checkout operation doesn't perform a get latest on the files being checked out. Updating that one file being checked out would violate the consistent snapshot philosophy and could result in a configuration of source that isn't buildable and testable. As an alternative, Team Foundation forces users to perform the get latest operation at some point before they checkin their changes. That's why if you attempt to checkin your changes, and you don't have the latest copy, you'll be prompted with the resolve conflicts dialog.
source: http://forums.microsoft.com/msdn/showpost.aspx?postid=70231&siteid=1

There is a workaround for this issue: http://frozenorange.wordpress.com/2007/01/18/tfs-check-out-get-latest-version/ But the question is: DO YOU REALY WANT THIS?

But when you only needed a pop up message, sorry it isn't yet in TFS. We wait......

Regards,
Harmjan

Positional Flat File with Early Termination

2007-06-21T11:16:00Z

For our customer we needed a optional fault description at the end of each line. Normaly BizTalk expect each line completely filled with characters. BizTalk expects the file to look like this:

Volgnr. (3 characters) || Datum (8 characters) || relatienummer 7 characters || FaultDescription (49 characters)

001200705061154879Error message: wrong number of description lengthß \r\n
001200705061154879Error message: wrong number ß \r\n

So even the FaultDescription field of the second line only has 27 characters, the remaining 22 need to be filled with spaces. Suppose your file has the end of line directly after the contents of the FaultDescription field ends:

001200705061154879Error message: wrong number of description lengthß \r\n
001200705061154879Error message: wrong numberß \r\n

But I received an exception:
There was a failure executing the receive pipeline
Source: "Flat file disassembler"
Reason: Unexpected end of stream while looking for: '\r\n'

David Downing (MSFT) has the solution: you can add the following annotation to the schemaInfo node: allow_early_termination="true" Be sure that you will add these annotation in the xsd where you put the recordinfo: child_delimiter="0x0D 0x0A"

Information from: topxml and Jan Tielens' Blog

Regards,
Harmjan

Removing diacritics (accents) from strings

2007-05-30T07:15:00Z

It's often useful to remove diacritic marks (often called accent marks) from characters. You know: tilde, cédille, umlaut and friends. This means 'é' becomes 'e', 'ü' becomes 'u' or 'à' becomes 'a'. This could be used for indexing or to build simple URLs, for example.
Doing so is not so easy if you don't know the trick. You can play with String.Replace or regular expressions... But do you know .NET 2 has all that is required to make this easier?

You should use this kind of code for example: (this example is only possible for .NET 2.0 or higher)

public static String RemoveDiacritics(String s)
{
String normalizedString = s.Normalize(NormalizationForm.FormD);
StringBuilder stringBuilder = new StringBuilder();

for (int i = 0; i < normalizedString.Length; i++)
{
    Char c = normalizedString[i];
    if (CharUnicodeInfo.GetUnicodeCategory(c) != UnicodeCategory.NonSpacingMark)
      stringBuilder.Append(c);
}

return stringBuilder.ToString();
}

Copied from Fabrice blog.

Using Configuration in BizTalk Map

2007-05-30T07:04:00Z

During BizTalk map definition, sometime you might require to read some configuration value. For example, during use of database related functoids, you have to make connection string configurable. You can use BizTalk config file and scripting functoid to handle such scenario.

Here is what you need to do -

Open "BTSNTSvc.exe.config" file from "drive:\Program Files\Microsoft BizTalk Server 2006 ".
Add configuration setting there such as -<appSettings> <add key="CONNSTR" value="Data Source=SQL-SERVER;Initial Catalog=SAMPLE_DB;Integrated Security=SSPI"/> </appSettings>
In map file, drag and drop script functoid and write following inline c# script.                                              public string GetConnectionString()
{
       string connString=System.Configuration.ConfigurationSettings.AppSettings.Get("CONNSTR").ToString();
       return connString;
}
While using any database related functoid, drag output of script functoid as input in database functoid. And do not forget to put it in correct parameter sequence. That’s it.

One more last thing, you cannot test config value in map at design time because configuration values are read BTS host at runtime.

source: http://blogs.msdn.com/brajens/archive/2007/01/16/using-configuration-in-biztalk-map.aspx

My First post

2007-03-26T23:41:00Z

Hi everybody,

my First post on this blog and I hope much more will follow. Soon you'll see more here. But on this moment I have no time to post more! First some bugfixing :D

Regards,

Harmjan