MOSS and Business Score Card Manager 2005

It is possible to use the Microsoft Office Business Score Card Manager with Microsoft Office SharePoint Server 2007... but you need the compatible version of BSCM 2005 and it works only on 32-Bit systems..

PDC Registration is online!

BizTalk FTP Adapter raises mystic error

"A failure occurred when parsing the remote folder listing"... just switch to passive mode.... :-)

HowTo use dynamic SAP Send Port with SAP Adapter 2.0

as described in the linked ms article above you can set the SAP URI dynamically. But the most problem you have is to install the SAP Adpter 2.0 on a Windows Vista Client... SAP Connector... VS.NET 2003... and all these stupid stuff....

Main problem is to set the username and password on runtime. You have to address the SAP Adapter properties in the header of the message send to the SAP system. You need to reference th Microsoft.BizTalk.SAPAdapterProperties.dll into your VS.NET Solution and you are now able to set the user credientials at runtime.

Uninitializes dynamic send port :-)

ok ok...

some kind of stupid stuff...
i was searching to resolve the error while compiling an orchestration... this error is normally thrown when you have no address registered for a dynamic send port...
BUT i had set this property... äääääähhhmmm... but not in the correct order...

this is the BAD expression in the shape:

Port_DynamicSAP(Microsoft.XLANGs.BaseTypes.TransportType) = "SAP";
Port_DynamicSAP(Microsoft.XLANGs.BaseTypes.Address) = SOMESTRING;

and this is the GOOD expression in the shape:

Port_DynamicSAP(Microsoft.XLANGs.BaseTypes.Address) = SOMESTRING;
Port_DynamicSAP(Microsoft.XLANGs.BaseTypes.TransportType) = "SAP";

*g*... errare humanum est....

MOSS Profile Import works only with one DC

If you want to import profiles in MOSS, you have to use only one domain controller for a LDAP query. this is by design... i have this situation:

three import sources and two domain controllers in "cluster mode". the first two import sources will work, but the third fails....

there is a workaround for this: just do an OR and use only two LDAP sources... or (of course) do an OR and use only ONE LDAP query... i will write some more lines about this tomorrow...

E-AI

in honor of my/our job.... all our cars have now the licence number schema E-AI XXX :-)