We have developed a custom pipeline component that writes in context FTP properties, such as BeforePut, UserName, ...
When we are testing this component we received an unusual error: "Ran out of memory".
After discard memory problems, we realize that our problem was that...Password was not properly setted!!
We set Password FTP Context property ("http://schemas.microsoft.com/BizTalk/2003/ftp-properties") and our "Ran out of memory" error disappears.
Monday, November 26, 2007
Saturday, November 24, 2007
SOA Conference 2007 at Madrid
Next December 4 at Madrid, Microsoft announces SOA Conference 2007 in Spain. My friend Tomás Hernández will talk about "BizTalk Adapters for WCF".
Here is a complete agenda:
http://www.microsoft.com/spain/sunegocioconectado/agenda.aspx
Here is a complete agenda:
http://www.microsoft.com/spain/sunegocioconectado/agenda.aspx
Friday, November 23, 2007
MQSC Adapter error
We have installed MQSC adapter for BizTalk, with WebSphere MQ Client 6, with fixpack 6.0.2.2.
Our MQ Servers are MQ WebSphere 6, one in Z/OS Server and other in a Windows 2003 Server.
When we defined a Receive Location and try to get a message, we received this two errors:
"The adapter "MQSC" raised an error message. Details "Failure encountered while attempting to get message from queue. queue = <QueueName>, queueManager = <QueueManagerName>, reasonCode = 2354"."
"The MQCD structure was not valid. The value of 'Version' field has the value '0'. This value is invalid for the operation requested."
We was investigating in this issue, when we find this post:
http://biztalk.softwareheadlines.com/mqsc-adapter-mqseries-client-adapter-extended-transaction-t3299.html
We try this solution and it works!!
Our channel name (for example CHANN.NAMES.SVRCONN) had sufficient length to produces the error. We change the channel name with a shorter name (CHANN.NAMES) and works ok.
Solution is give a channel name one char less that maximum length.
Our MQ Servers are MQ WebSphere 6, one in Z/OS Server and other in a Windows 2003 Server.
When we defined a Receive Location and try to get a message, we received this two errors:
"The adapter "MQSC" raised an error message. Details "Failure encountered while attempting to get message from queue. queue = <QueueName>, queueManager = <QueueManagerName>, reasonCode = 2354"."
"The MQCD structure was not valid. The value of 'Version' field has the value '0'. This value is invalid for the operation requested."
We was investigating in this issue, when we find this post:
http://biztalk.softwareheadlines.com/mqsc-adapter-mqseries-client-adapter-extended-transaction-t3299.html
We try this solution and it works!!
Our channel name (for example CHANN.NAMES.SVRCONN) had sufficient length to produces the error. We change the channel name with a shorter name (CHANN.NAMES) and works ok.
Solution is give a channel name one char less that maximum length.
Wednesday, November 21, 2007
Download the Visual Studio 2008 Express Edition All-in-One DVD
Since few days ago is possible to download Visual Studio 2008 in an ISO image. Here is the link:
http://go.microsoft.com/fwlink/?LinkId=104679
Also for instructions on burning the Visual Studio Express Editions DVD there is this link:
http://www.microsoft.com/express/download/offline.aspx
http://go.microsoft.com/fwlink/?LinkId=104679
Also for instructions on burning the Visual Studio Express Editions DVD there is this link:
http://www.microsoft.com/express/download/offline.aspx
Thursday, November 15, 2007
Web Parts Personalization Providers
As I say in my previous post, today I found a lot of problems when I deploy my application in an integration environment.
Web Parts Personalization was a problem, because I can't use the default database to store the personalization values.
We found two posible solutions in this links:
http://msdn2.microsoft.com/en-us/library/aa479037.aspx
http://www.kowitz.net/files/source/XmlFilePersonalizationProvider.cs.txt
First of two, allow to store values in a txt file and second allow to store values in an XML files.
Both examples, build a class that derives from ProviderBase class. I use txt file provider, I customize the class, because I need more functionality. For example, I implemented this method that recognize when a user has personalization data:
public override int GetCountOfState(PersonalizationScope scope,
PersonalizationStateQuery query)
{
if (File.Exists(GetPath(query.UsernameToMatch, query.PathToMatch)))
return 1;
else
return 0;
}
It works ok and now, I don't need the default personalization database.
Web Parts Personalization was a problem, because I can't use the default database to store the personalization values.
We found two posible solutions in this links:
http://msdn2.microsoft.com/en-us/library/aa479037.aspx
http://www.kowitz.net/files/source/XmlFilePersonalizationProvider.cs.txt
First of two, allow to store values in a txt file and second allow to store values in an XML files.
Both examples, build a class that derives from ProviderBase class. I use txt file provider, I customize the class, because I need more functionality. For example, I implemented this method that recognize when a user has personalization data:
public override int GetCountOfState(PersonalizationScope scope,
PersonalizationStateQuery query)
{
if (File.Exists(GetPath(query.UsernameToMatch, query.PathToMatch)))
return 1;
else
return 0;
}
It works ok and now, I don't need the default personalization database.
SSO Error - The trust relationship between the primary domain and the trusted domain failed.
Today, when I was deploying my application in an integration environment, I found a lot of problems. First of all was this error message when I deploy my config files into SSO:
This error message confuse me, but finally I found the solution and was very simple. My error was that in my application configuration XML file for SSO, I set in appAdminAccount tag, my local account, instead of domain account.
SSO AUDIT
Function: CreateApplication
Tracking ID: caa4f99b-8053-4a8a-bfd0-67fcce18e978
Client Computer: server.domain.com (ssomanage.exe:4520)
Client User: DOMAIN\User
Application Name: MyApplication
Error Code: 0x800706FC, The trust relationship between the primary domain and the trusted domain failed.
This error message confuse me, but finally I found the solution and was very simple. My error was that in my application configuration XML file for SSO, I set in appAdminAccount tag, my local account, instead of domain account.
Monday, November 12, 2007
AddressAccessDeniedException - Windows Vista
Due to new security settings in Windows Vista, we get this error "HTTP could not register URL http://+:8081/Greeting. Your process does not have access rights to this namespace (see http://go.microsoft.com/fwlink/?LinkId=70353 for details)" when we try to run a ServiceHost in an HTTP address.
To resolve this, we have to give permissions to our user:
1º) Run Visual Studio 2005 Command Prompt as Administrator.
2º) Execute netsh http add urlacl url=http://+:8081/Greeting user=DOMAIN\user
3º) If we want remove permissions: netsh http delete urlacl url=http://+:8081/Greeting
To resolve this, we have to give permissions to our user:
1º) Run Visual Studio 2005 Command Prompt as Administrator.
2º) Execute netsh http add urlacl url=http://+:8081/Greeting user=DOMAIN\user
3º) If we want remove permissions: netsh http delete urlacl url=http://+:8081/Greeting
Subscribe to:
Posts (Atom)