AS2 ID and URL in BizTalk Server 2009

Hi Everyone,
I am new to BizTalk and have some very basic understanding of what it does. My client wants to send and receive EDIFACT files over AS2 protocol and they have asked for our AS2 ID, AS2 URL and certificate(public if I am right). Please find my understanding below
about these and correct me if anything goes wrong
1. AS2 ID - Not sure where and how to create AS2 ID
2. AS2 URL - I have created a virtual directory[AS2] in IIS to receive files from client [Path mapped to C:\Program Files\Microsoft BizTalk Server 2009\HttpReceive] and the URL obtained is http:\\<ip_addr>\as2
3. Certificate - Certificate is generated with 1 year validity using Certificate authority services in windows server 2003 and exported with [Do not export private key] option
Is the above AS2 URL correct to share with the client?Is the certificate generated is valid to share?
And please tell me how to create AS2 ID
Platform details:
1. Windows Server 2003
2. BizTalk 2009 with SQL Server 2005 Standard Edition [SP2]
Any help on this is highly appreciated.
Thanks in advance
Jose

Jose,
For your Requirement, you need to provide the below to the customer to establish the AS2 communication.
1) Party - You need to create a Party in the console in your own and also you need to specify the thumbprint of your certificates..
Refer the
msdn for configuring which would help you in configuring.
2) You need to make sure your client allows your server (IP - Not white listed) to access their firewall when you are sending the message.
3) You need to make sure that your server is made accessible to your customer server to send the files.
4) You need to have the Partner ID of your customer and configure a Party with the Certificate Details for receiving the files from Customer.
5) you need to provide the your certificates (Public) to your customer and you need to have the customer's certificate in your store as well.
Hope this helps, also you can configure lot of details (MDN req or not) in the Parties that is created for your customer.
Regards - Rajasekhar.R ' Don't forget to mark the post as answer or vote as helpful if it does,

Similar Messages

How to send 999 from BizTalk Server 2009?

I am trying to send 999 from BizTalk server 2009. I downloaded 999 (Errata schema) from CU4 of BizTalk 2009.
I know we need to map 997 to 999 as there are no built in configuration avaialable. If you have any BizTalk mapper to do 997 - 999 transformation. Please share with me.
Also is there any other way to accomplish this, please let me know your thoughts.
Bit urgent !!!!!
Thanks,
Rajesh N

you can send 999 acknowledgement even without mapping.
refer- http://support.microsoft.com/kb/2669948/en-us
To generate 999 acknowledgements, you must create a custom receive pipeline and set the Use 999 Acknowledgment Instead
of 997 option to True.
you also need to configure EDI acknowledgement property
When the 997 acknowledgement is enabled, BizTalk EDI assumes that 997 Acknowledgement must be generated for the incoming message from
the party. With the Override997With999 property set to True, a 999 is returned instead of
a 997. If you don’t want a 997 or 999, uncheck the 997 Expected property in the agreement. A 997 and 999
acknowledgement cannot be generated simultaneously. If this is the goal, a custom pipeline component is needed.

AS2 Certificates and URL

Hi,
We are setting up a party and going to exchange via AS2.
As the messages would involve outbound and inbound, they had forwarded their certificates along with URL path.
Also, they were requesting GLN number. Please let me know what is it about.

Hi Krish,
>>As the messages would involve outbound and inbound, they had forwarded their certificates along with URL path.
Nwo you need to provide your certificates and url.. Generally there shoudl be a template for exchanging this information...
GLN number is an identification number, through which your messages are identified.. we call it as AS2ID
Regards
Suraj

BizTalk Server 2009 | most of my messages suspending

Hi,
I have a application to process the files and when we dropped the files
--most of the times it is occupying 100% CPU
--all messages are going to suspended state and generating a partial file
when this happens i can see the below error message in the event logs. could you please suggest what is causing the issue.
xlang/s engine event log entry: Failed while creating a xxxxx_Clms_837_Inbound.BizTalk_Orchestration1 service.
Exception type: ServiceCreationException
The following is a stack trace that identifies the location where the exception occured
   at Microsoft.BizTalk.XLANGs.BTXEngine.BTXSession._serviceCreator(Guid& instanceId, Object objCurrMsg)
   at Microsoft.XLANGs.Core.ResourceContainer._allocateResource(Guid& key, UInt32 hashKey, ResourceCreator resCreator, Object creationContext)
   at Microsoft.XLANGs.Core.ResourceContainer.Dispense(Guid& key, ResourceCreator resCreator, Object creationContext)
   at Microsoft.BizTalk.XLANGs.BTXEngine.BTXSession._dispenseService(Guid& instanceId, IBTMessage currMsg)
   at Microsoft.BizTalk.XLANGs.BTXEngine.BTXSession._tryReceiveOneMessage(Boolean& loggedError, Guid& instanceId, IBTMessage currMsg)
   at Microsoft.BizTalk.XLANGs.BTXEngine.BTXSession._receiveOneMessage(Guid& instanceId, Guid& serviceId, IBTMessage currentMsg)
   at Microsoft.BizTalk.XLANGs.BTXEngine.BTXSession.ReceiveMessages(IBTMessage[] messages, Int32 firstIdx, Int32 count)
   at Microsoft.BizTalk.XLANGs.BTXEngine.AppDomains.AppDomainRoot.Microsoft.XLANGs.BizTalk.ProcessInterface.IAppDomainStub.ReceiveMessages(Object objMsg)
   at Microsoft.XLANGs.BizTalk.CrossProcess.AppDomainStubProxy.Microsoft.XLANGs.BizTalk.ProcessInterface.IAppDomainStub.ReceiveMessages(Object msgs)
   at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
   at System.Runtime.Remoting.Messaging.StackBuilderSink.PrivateProcessMessage(RuntimeMethodHandle md, Object[] args, Object server, Int32 methodPtr, Boolean fExecuteInContext, Object[]& outArgs)
   at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg, Int32 methodPtr, Boolean fExecuteInContext)
   at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg)
   at System.Runtime.Remoting.Messaging.ServerObjectTerminatorSink.SyncProcessMessage(IMessage reqMsg)
   at System.Runtime.Remoting.Messaging.ServerContextTerminatorSink.SyncProcessMessage(IMessage reqMsg)
   at System.Runtime.Remoting.Channels.CrossContextChannel.SyncProcessMessageCallback(Object[] args)
   at System.Threading.Thread.CompleteCrossContextCallback(InternalCrossContextDelegate ftnToCall, Object[] args)
   at System.Threading.Thread.InternalCrossContextCallback(Context ctx, IntPtr ctxID, Int32 appDomainID, InternalCrossContextDelegate ftnToCall, Object[] args)
   at System.Threading.Thread.InternalCrossContextCallback(Context ctx, InternalCrossContextDelegate ftnToCall, Object[] args)
   at System.Runtime.Remoting.Channels.CrossContextChannel.SyncProcessMessage(IMessage reqMsg)
   at System.Runtime.Remoting.Channels.ChannelServices.SyncDispatchMessage(IMessage msg)
   at System.Runtime.Remoting.Channels.CrossAppDomainSink.DoDispatch(Byte[] reqStmBuff, SmuggledMethodCallMessage smuggledMcm, SmuggledMethodReturnMessage& smuggledMrm)
   at System.Runtime.Remoting.Channels.CrossAppDomainSink.DoTransitionDispatchCallback(Object[] args)
   at System.Threading.Thread.CompleteCrossContextCallback(InternalCrossContextDelegate ftnToCall, Object[] args)
Regards
Madhu

Hi Madhu,
This error could occur to deployment issue where you assemblies are not deployed property or also when the assemblies you have deployed have some build related issues like not built against the correct version of .NET framework (in your case .NET 3.5 for
BizTalk 2009)
When you say your CPU utilization goes to 100% also make us to doubt on throttling and not enough resource availability for message processing. But I have not seen a case where BizTalk would create all the suspended message as partial messages due to throttling.
Lets identify the root cause of issue as whether its a deployment issue or message-load/throttling issue.
Instead of dropping all the files at one go to BizTalk's receive location, drop just one or few messages and see the behaviours of the message transmission. If even after dropping one message (or few message) fails with the same pattern as creating
partial message(s) as the suspended instance, then its a deployment issue. Before I do this I would restart the host instances. If this issue occurs only when you drop more number of messages, then this could be due to throttling/resource shortage issue. In
this case of throttling use monitor the performance monitor using
PAL and also run
Messagebox view tool to identity the root cause of the issue.
If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

Some help needed regarding Files and URLs on a server

I don't get it - my applet works in a local directory, but not on a server. This has to do with the loading of files (I load an array of images to use, but when I attempt to use that array, it comes up with the error ArrayIndexOutOfBounds), but I can't understand what the problem is...
I have a code that loads files (using File objects) from the current directory (a .jar file) into the program. I do not simply type in the file names - I set it so that the program searches for them based on a prefix in the file name. This works fine on my computer, and I never navigate to files outside of the .jar file. Why might this have a problem on a server? Would URL objects be more appropriate?
Note: I alter the file base String in this way before loading it (this stands for the current directory)
fileBase = applet.codeBase.toString().replace('\\', '/');codeBase is simply the applet's codeBase() method put into a URL variable. The replace statement is there so that there are no backslashes. And this works perfectly on my computer. Any help? Would it work if I used a URL instead? If so, how do I perform a search function with a URL (so that all the filenames within a certain directory are returned as Strings)?

Thanks for the info, it helps a lot. You say there is no "practical" way to search for a file under a URL path. What I am trying to do is load a file that begins with a particular prefix. (eg. I wish to load a file called "funnyImage0011204924." However, the numbers after the prefix "funnyImage" are variable, and might require change in the future. Is it possible to load any file with the prefix "funnyImage," using URL methods? Would I need to create a new class? Is this impossible?)
Please remember that I do not plan to go outside the .jar file, so there is no point in trying to get around server permissions and all that if it is unnecessary.

Component Service microsoft.biztalk.adapter.sql for BizTalk Server 2009

Hello All,
We have a production server which has 2 hosts used for receiving data. When I use these hosts for SQL adapter I am getting an error that "the receive location is shutting down. Details: The error threshold has been exceeded. The receive location is
shutting down"
I did some analysis and can see that the component service "microsoft.biztalk.adapter.sql " is missing on my receive server. Can this be the reason for this?

Hi,
Please check DTC connectivity between the two servers using DTCPing and DTCTester. That at the very least should make things easier to diagnose.
http://www.microsoft.com/downloads/details.aspx?FamilyID=5e325025-4dcd-4658-a549-1d549ac17644&DisplayLang=en
http://support.microsoft.com/default.aspx?scid=kb;en-us;293799
http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q306843
Make sure that "Distributed Transaction Coordinator" service is running on both biztalk and SQL server.
Rachit

Biztalk server 2009- Orphaned instances

Hi ,
I have run the Biztalk MBV report and found the below
there are 19792 DTA Oraphaned instances
i have tired to use Biztalk terminator tool it says its expired can you send me the latest version of terminator tool?
is there nay other way to do?

Hi Sujith,
Yes, The installtion for this BizTalk tool is expired as on today (03-Sep-2014)
I did a quick (funny) thing to make it work.
This tool was updated on (04-Sep-2013) and today is 03-Sep-2014. This version work only until 31-Aug-2013 and expired on 01-Sep-2014. I hope Microsoft update this tool in early September every year which has not happened as of now.
But if you change your system date to anything earlier to 01-Sep-2014. i.e. if you set the system date to 31-Aug-2014, this tool would work :)
Wait for the latest version to be uploaded, meanwhile change your system date to make it work. Obviously you can't change your system dates in production servers. If tt’s for non-production server (or to server changing system date doesn't matter) change
it otherwise wait for the tool to be updated.
FYI: codePlex terminator tool is not a offical tool and its a different one.
If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

Migrating From BizTalk 2009 To Biztalk server 2013

Hi All,
My current solution is on BizTalk 2009 and my client is thinking of migrating to BizTalk 2013 . Please suggest me is it a good idea to migrate to BizTalk 2013.
Please provide me a difference between 2009 to 2013
Difference between 2009 to 2013 and main features.
Thanks and Regards
Dhanavel S

Hi Dhanavel,
Why don’t you think about migrating to BizTalk 2013 R2 which is available now. Anyway
First and foremost thing, BizTalk Server 2009’s mainstream support from Microsoft has ended on 08-July-2014. After mainstream support, customer will get extended support until
09-July-2019. So you're are in extended support phase now. Find out the following blogpost where you will know more about what you can get and what you’re going to miss from Microsoft support for BizTalk Server 2009. And also about what you have to do next.
Why you have to migrate to the latest version.
BizTalk Server 2009 mainstream support ends.What to do next?
Apart from losing the benefits of mainstream support against the extended support and apart from getting the benefits of latest offering/features of the newer version of the
product, BizTalk server 2009 is closely dependent on its underlying platforms like Windows Server 2008 (or Window server 2003/Windows XP-SP3/Windows Visa SP1), SQL Server 2008 (or SQL Server 2005 SP2) and Visual Studio 2008. So its high time to migrate.
BizTalk Server 2009 mainstream support ends. What to do next?
Some of the benefits of migrating from BizTalk 2009 to BizTalk 2013.
Platform upgrades:
BizTalk 2013 uses following, so when you upgrade from BizTalk 2009 to 2013, you will get the benefits by upgrading your platforms.
Windows Server 2012 (BizTalk 2009 uses Windows Server 2009)
Visual Studio 2012(BizTalk 2009 uses Visual Studio2008)
.NET Framework 4.5 (BizTalk 2009 uses .NET 3.5)
SQL Server 2012(BizTalk 2009 uses SQL 2008)
Virtualization support for Hyper-V (this feature is available from BizTalk 2010 onwards)
Some of the other benefits include
Better support to could
Azure Service Bus. And support for
BizTalk Server running on Azure IaaS
BizTalk Server 2013 Support for RESTful Services
More support towards WCF-based adpaters.
Secure FTP with new FTPS Adapter and an improved FTP Adapter
Out-of-box support to SFTP Adapter
Enhancements to the IBM Hosts Systems adapters
Update to BizTalk mapper
Updated Trading Partner Management (TPM) Capabilities.
Updates to industry schemas like HIPPA, HL7, SWIFT and SWIFTNet
Seamless ability to leverage BizTalk capabilities from SharePoint 2010 Business Connectivity Service to Line-of-Business systems
BizTalk Server setting dashboard for setting to
configuring the key performance, throttling, and tracking settings of your entire BizTalk group while offering fine grained control all the way down to the Host
Instance level.
ESB toolkit part of BizTalk installation.
If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

Issues with creating and sending BOM XML IDOC to SAP using 2010 WCF-SAP Adapter (without using Biztalk Server)

I'm trying to replace an existing Biztalk 2006 Send BOM IDOC process, and completely remove Biztalk server from the equation. The existing Bizatalk 2006 server receives an input BOM (Bill of Materials) flat file, and using a Biztalk Map (BM08),
and Orchestration, generates an Idoc and sends it to SAP.
In my replacement C# program, I'm using the 2010 WCF-SAP Adapter, and am trying to generate the BOMMAT03 XML IDOC it to SAP.
I generated the BOMMAT03 schema from SAP using the Add Adapter Service in VS 2010. I was able to generate a BM08 XSLT from the existing BMO8 map in the current Biztalk 2006 process. I am able to run a XSLT transform on the input BOM flat
file, and generate an XML file from that.
However, I've run into a few issues. First of which, is that the XML file that is generated from the XSLT transform is NOT the same schema as the BOMMAT03 schema expects. It's somewhat similar, but different enough that I have to manually
translate between the two in my code. I've verified that both the original Bitztalk 2006 process and my replacement program use BOMMAT V3 from SAP. Question--Is Biztalk 2006 server doing some other magic to turn that transormed XML into the BOMMAT03
schema?
I ended writing code which translates the transformed XML into the BOMMAT03 schema (which is a strong typed XML IDOC at this point).
However, when I try to send the BOMMAT03 XML IDOC, I get an exception "Object reference not set to an instance of an object."
idocClient.Send(idocData, ref sadapterTxGuid);
idocData is of type BOMMAT03, and I've verified that the various fields are populated.
Any help is appreciated.

Well, putting in a MSDN subscription support ticket for Biztalk server actually helped with the issue. They didn't find, or fix the issue directly. But one of the examples (https://randypaulo.wordpress.com/tag/idoc/) they sent over, jogged my
memory, and I realized in the code snippet below, I had accidentally deleted the 1st line. Such a simple mistake, yet was easy to overlook. The URL example is almost EXACTLY like my code, but without the transform and translation code to convert
from input XML file to IDOC XML. If someone is interested in that, let me know.
//Forgot the 1st line.
idocClient = new IdocBOMMAT03SIEIS_WED_BOMMAT03V3R700Client(binding, endpointAddress);
idocClient.Send(idocData, ref sadapterTxGuid);
For anyone else interested in knowing, you CAN send a strongly typed IDOC to SAP using C#.NET and the WCF SAP 2010 Adapter, using the IDOC Binding Client class you generated using the Add Adapter Service Reference in VS2010.
The one difference, which no one, not even the tech support from MS could tell me, was why the XSLT which I generated from the original map, did not transform the input BOM XML into the BOMMAT03 XML. Instead, it transformed it into an intermediate
XML, which resembled the BOMMAT03 IDOC XML, but still needed to be translated to the BOMMAT03 IDOC format.
The tech support person swore up and down that it should. But I believe that something happens in Biztalk server, after the Mapping occurs, maybe in the Pipeline, which converts that
intermediate XML into the final BOMMAT03 IDOC XML format.
I do think that the examples are severely lacking in showing how to send a strong typed IDOC using C# and the WCF-SAP Adapter. Even worse, the examples are completely lacking in how to actually generate a weakly typed IDOC. They show how to send
that weakly typed IDOC, but show me, or give me a class to be able to generate it.
I realize that this is not quite the "recommended way" to do it, but in reality, not everyone wants or even needs a full Biztalk installation. For some simple stuff like this, a C#.NET program and WCF-SAP adapter do the trick.

BAM APIs and TPE in BizTalk

Hi - i have been assigned work related to tracking data using BAM (its like Purchase Order, Sending/receiving Invoice, for Property related work)
I know TPE is used to track only at Ports level which is not always helpful and if there is looping involved it doesnt work.
BAM APIs is better way to approach as it can be customisable as per requirement.
Is there any real good detailed example of showing using BAM for tracking # of Received files, # of loop records, tracking within Orchestration, Sent delivery , and lot other stuff.
Please let me know.
MBH

There are few SDK samples available for learning about BAM
API:
From BizTalk SDK samples:
BAM
API(BizTalk
Server Sample)
Instrumenting a Solution: Step-by-Step
APIUsage
BAM
APIfrom
an Orchestration Expression (BizTalk Server Sample)
For looping records:
Capturing BizTalk 2006 BAM Data On Looping Process
I would also recommend this book,
Pro BAM in BizTalk Server 2009
If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

Biztalk server Deployment

when we were Deploying Package using MSI we got the following error
Failed to deploy map
Error saving map. Stored procedure returned non-zero result. Check if source and target schemas are present.
Error saving map. Stored procedure returned non-zero result. Check if source and target schemas are present.
I have read in one of the article that this is a bug with CU6 Update
Can anyone help me is there any way we can import this MSI?

One option you can try is delete the BizTalk application completely and reinstall this package again. This issue occurs when the update to the previous deployment schema and its namespace.
For BizTalk 2009, there is no release to fix this issue, yet some customer had raised this issue in 2009 environment. May be the time when the customer raised this issue (or when they/MS realised this as an issue) Microsoft's Mainstream Support for this
version is going to end (08/July/2014).
Based on this MSDN blog, you have to contact
Microsoft Support to find a fix for this issue.
MSDN
blog: "Error saving map. Stored procedure returned non-zero result." error message when you deploy the BizTalk Server 2009 applications in BizTalk Server 2009(with CU6 installed) Administration Console
If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful by clicking the upward arrow mark next to my reply.

Can I use BizTalk A4SWIFT without installing BizTalk server?

Can I use BizTalk A4SWIFT message pack to parse and validate ISO messages without installing BizTalk server?

No, You can't use BizTalk A4 SWIFT message pack without BizTalk:
Here is the Prerequisites for BizTalk Server Accelerator for SWIFT - Message Pack 2012.
BizTalk
Server Version
A4SWIFT Version and Service Pack
(if required)
Microsoft Visual C++ 2005 SP1 Redistributable Package
Microsoft .NET Framework
BizTalk Server 2009
A4SWIFT 2009
No
3.5
BizTalk Server 2010
A4SWIFT 2010
No
4.0
Reference:
Installation document for BizTalk Server Accelerator for SWIFT - Message Pack 2012
If this answers your question please mark it accordingly. If this post is helpful, please vote as helpful.

Looking for microsoft press book on C# programming for Biztalk server 2013 and also one for WWF 4.5

Is there any microsoft pressbook available for Biztalk server 2013?
Also is there one for WWF 4.5.
Please send me the URL where I can view the book contwnta nad buy.
Rajesh S Harwani

The dynamic ports use a pipeline including a custom pipeline component which I can confirm is available in the correct directory
C:\Program Files (x86)\Microsoft BizTalk Server 2013\Pipeline Components
I’m a bit stuck at what to try now, I have option where I could recreate the dynamic ports from scratch in the orchestrations and redeploy to dev in the hope it’s something
that VS2012 didn’t handle too gracefully when converting the project.
Two things.
1. That's what I would do first, recreate (really just change and reset the properties) the Orchestration Ports in Visual Studio.
2. Probably not related but, Custom Pipeline Components should not be placed in the Pipeline Components folder. All Custom Pipeline Components should be in the GAC only. The Pipeline Components folder
is a compatibility vestige from BizTalk Server 2004.

OpenReportingWebServiceConnection in the windowsupdate.log sometimes points to Microsoft URL and sometimes to WSUS server

OpenReportingWebServiceConnection in the windowsupdate.log sometimes points to Microsoft URL and sometimes to WSUS server.
Why is that? WSUS reports are never up-to-date. if this is by design it sucks
Also... it will take forever before clients are reporting to WSUS server..
Kind regards / Met vriendelijke groet, IS Group Rob Mulder Kantoorautomatiseerder Wielingenstraat 8 T 0299 476 185 1441 ZR Purmerend F 0299 476 288 www.is.nl / www.isenterprise.com KvK Hoorn 36049256

Hi Lawrence,
I installed a new server (2012R2 standard), fully patched and only the WSUS role. Uninstalled the old one, used same database and moved the downloads. Installed a new PC (win 8.1 update 1), not in the domain so no policies. Changed the local update
policy and point to the WSUS server.
Still no luck...... WSUS Last Status Report keeps saying 'Not yet reported'.
Could it be a network problem (VLAN, Firewall)??
The log:
2014-05-23 08:15:18:475 804 a08 IdleTmr Decremented idle timer priority operation counter to 0
2014-05-23 08:15:18:872 804 7e4 Shutdwn Checking to see whether install at shutdown is appropriate
2014-05-23 08:15:18:888 804 7e4 Shutdwn user declined update at shutdown
2014-05-23 08:15:18:888 804 7e4 AU AU initiates service shutdown
2014-05-23 08:15:18:888 804 7e4 AU ########### AU: Uninitializing Automatic Updates ###########
2014-05-23 08:15:18:903 804 7e4 WuTask Uninit WU Task Manager
2014-05-23 08:15:18:903 804 7e4 WuTask ScheduledInstallTaskHandler, setting scheduled install attempt time to 2014-05-25 06:09:51, using automatic maintenance:True.
2014-05-23 08:15:19:169 804 7e4 Report CWERReporter finished handling 1 events. (00000000)
2014-05-23 08:15:19:185 804 7e4 AU Earliest future timer found:
2014-05-23 08:15:19:185 804 7e4 AU     Timer: 117CAB2D-82B1-4B5A-A08C-4D62DBEE7782, Expires 2014-05-23 07:27:03, not idle-only, network-only
2014-05-23 08:15:19:278 804 7e4 AU Earliest future timer found:
2014-05-23 08:15:19:278 804 7e4 AU     Timer: 31DA7559-FE27-4810-8FF6-987195B1FD98, Expires 2014-05-24 02:26:02, not idle-only, not network-only
2014-05-23 08:15:19:560 804 7e4 Service *********
2014-05-23 08:15:19:560 804 7e4 Service ** END ** Service: Service exit [Exit code = 0x240001]
2014-05-23 08:15:19:560 804 7e4 Service *************
2014-05-23 08:15:51:285 760 5d8 Misc =========== Logging initialized (build: 7.9.9600.17093, tz: +0200) ===========
2014-05-23 08:15:51:301 760 5d8 Misc   = Process: C:\Windows\system32\svchost.exe
2014-05-23 08:15:51:301 760 5d8 Misc   = Module: c:\windows\system32\wuaueng.dll
2014-05-23 08:15:51:254 760 5d8 Service *************
2014-05-23 08:15:51:301 760 5d8 Service ** START ** Service: Service startup
2014-05-23 08:15:51:301 760 5d8 Service *********
2014-05-23 08:15:51:832 760 5d8 IdleTmr Non-AoAc machine. Aoac operations will be ignored.
2014-05-23 08:15:51:879 760 5d8 Agent   * WU client version 7.9.9600.17093
2014-05-23 08:15:51:910 760 5d8 Agent WARNING: SleepStudyTracker: Machine is non-AOAC. Sleep study tracker disabled.
2014-05-23 08:15:51:910 760 5d8 Agent   * Base directory: C:\Windows\SoftwareDistribution
2014-05-23 08:15:51:910 760 5d8 Agent   * Access type: No proxy
2014-05-23 08:15:51:910 760 5d8 Service UpdateNetworkState Ipv6, cNetworkInterfaces = 1.
2014-05-23 08:15:51:910 760 5d8 Service UpdateNetworkState Ipv4, cNetworkInterfaces = 1.
2014-05-23 08:15:51:910 760 5d8 Agent   * Network state: Connected
2014-05-23 08:15:52:035 760 5d8 Service UpdateNetworkState Ipv6, cNetworkInterfaces = 1.
2014-05-23 08:15:52:035 760 5d8 Service UpdateNetworkState Ipv4, cNetworkInterfaces = 1.
2014-05-23 08:15:53:207 760 5d8 Agent *********** Agent: Initializing global settings cache ***********
2014-05-23 08:15:53:207 760 5d8 Agent   * Endpoint Provider: 00000000-0000-0000-0000-000000000000
2014-05-23 08:15:53:207 760 5d8 Agent   * WSUS server:
http://is-wsus-001:8530
2014-05-23 08:15:53:207 760 5d8 Agent   * WSUS status server:
http://is-wsus-001:8530
2014-05-23 08:15:53:207 760 5d8 Agent   * Target group: TEST
2014-05-23 08:15:53:207 760 5d8 Agent   * Windows Update access disabled: No
2014-05-23 08:15:53:457 760 5d8 WuTask WuTaskManager delay initialize completed successfully..
2014-05-23 08:15:53:473 760 5d8 AU     Timer: 117CAB2D-82B1-4B5A-A08C-4D62DBEE7782, Expires 2014-05-23 07:27:03, not idle-only, network-only
2014-05-23 08:15:53:473 760 5d8 AU     Timer: 31DA7559-FE27-4810-8FF6-987195B1FD98, Expires 2014-05-24 02:26:02, not idle-only, not network-only
2014-05-23 08:15:53:473 760 5d8 AU     Timer: CF1ABEC6-7887-4964-BB93-B2E21B31CEC1, Expires 2014-05-24 06:06:34, not idle-only, not network-only
2014-05-23 08:15:53:473 760 5d8 AU     Timer: 29A863E7-8609-4D1E-B7CD-5668F857F1DB, Expires 2014-05-24 06:06:32, not idle-only, not network-only
2014-05-23 08:15:53:473 760 5d8 AU     Timer: E25CADF6-86A6-4569-BCDF-89BE66B0CA66, Expires 2014-05-26 06:08:09, not idle-only, not network-only
2014-05-23 08:15:54:160 760 5d8 Report CWERReporter::Init succeeded
2014-05-23 08:15:54:160 760 5d8 Agent *********** Agent: Initializing Windows Update Agent ***********
2014-05-23 08:15:54:207 760 5d8 Agent   * Found 11 persisted download calls to restore
2014-05-23 08:15:54:426 760 5d8 DnldMgr Download manager restoring 0 downloads
2014-05-23 08:15:54:426 760 5d8 Agent   * Successfully loaded 11 persisted download calls.
2014-05-23 08:15:54:457 760 5d8 AU ########### AU: Initializing Automatic Updates ###########
2014-05-23 08:15:54:457 760 5d8 AU Additional Service {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} with Approval type {Scheduled} added to AU services list
2014-05-23 08:15:54:457 760 5d8 AU AIR Mode is disabled
2014-05-23 08:15:54:457 760 5d8 AU   # Policy Driven Provider:
http://is-wsus-001:8530
2014-05-23 08:15:54:457 760 5d8 AU   # Detection frequency: 22
2014-05-23 08:15:54:457 760 5d8 AU   # Target group: TEST
2014-05-23 08:15:54:457 760 5d8 AU   # Approval type: Pre-install notify (Policy)
2014-05-23 08:15:54:457 760 5d8 AU   # Auto-install minor updates: No (User preference)
2014-05-23 08:15:54:457 760 5d8 AU   # ServiceTypeDefault: Service 117CAB2D-82B1-4B5A-A08C-4D62DBEE7782 Approval type: (Scheduled)
2014-05-23 08:15:54:457 760 5d8 AU   # Will interact with non-admins (Non-admins are elevated (User preference))
2014-05-23 08:15:54:770 760 5d8 AU WARNING: Failed to get Wu Exemption info from NLM, assuming not exempt, error = 0x80070032
2014-05-23 08:15:55:254 760 5d8 AU AU finished delayed initialization
2014-05-23 08:15:55:254 760 5d8 AU Processing post-reboot results now.
2014-05-23 08:15:55:270 760 5d8 AU Obtained Post reboot hr from Agent:8024000c
2014-05-23 08:15:55:348 760 5d8 AU Additional Service {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} with Approval type {Scheduled} added to AU services list
2014-05-23 08:15:55:348 760 5d8 AU Triggering Offline detection (non-interactive)
2014-05-23 08:15:55:348 760 5d8 AU Adding timer:
2014-05-23 08:15:55:348 760 5d8 AU     Timer: 31DA7559-FE27-4810-8FF6-987195B1FD98, Expires 2014-05-23 06:15:55, not idle-only, not network-only
2014-05-23 08:15:55:394 760 5d8 AU Adding timer:
2014-05-23 08:15:55:394 760 5d8 AU     Timer: 31DA7559-FE27-4810-8FF6-987195B1FD98, Expires 2014-05-23 06:15:55, not idle-only, not network-only
2014-05-23 08:15:55:394 760 5d8 AU #############
2014-05-23 08:15:55:394 760 5d8 AU ## START ## AU: Search for updates
2014-05-23 08:15:55:394 760 5d8 AU #########
2014-05-23 08:15:55:394 760 5d8 IdleTmr WU operation (CSearchCall::Init ID 12) started; operation # 73; does not use network; is at background priority
2014-05-23 08:15:55:394 760 780 DnldMgr Asking handlers to reconcile their sandboxes
2014-05-23 08:15:56:379 760 5d8 Report *********** Report: Initializing static reporting data ***********
2014-05-23 08:15:56:379 760 5d8 Report   * OS Version = 6.3.9600.0.0.65792
2014-05-23 08:15:56:379 760 5d8 Report   * OS Product Type = 0x00000004
2014-05-23 08:15:56:394 760 5d8 Report   * Computer Brand = Hewlett-Packard
2014-05-23 08:15:56:394 760 5d8 Report   * Computer Model = HP Compaq 8000 Elite SFF PC
2014-05-23 08:15:56:394 760 5d8 Report   * Platform Role = 1
2014-05-23 08:15:56:394 760 5d8 Report   * AlwaysOn/AlwaysConnected (AOAC) = 0
2014-05-23 08:15:56:394 760 5d8 Report   * Bios Revision = 786G7 v01.02
2014-05-23 08:15:56:394 760 5d8 Report   * Bios Name = Default System BIOS
2014-05-23 08:15:56:394 760 5d8 Report   * Bios Release Date = 2009-10-22T00:00:00
2014-05-23 08:15:56:394 760 5d8 Report   * Bios Sku Number = AU247AV
2014-05-23 08:15:56:394 760 5d8 Report   * Bios Vendor = Hewlett-Packard
2014-05-23 08:15:56:394 760 5d8 Report   * Bios Family = 103C_53307F
2014-05-23 08:15:56:394 760 5d8 Report   * Bios Major Release = 1
2014-05-23 08:15:56:394 760 5d8 Report   * Bios Minor Release = 2
2014-05-23 08:15:56:394 760 5d8 Report   * Locale ID = 1033
2014-05-23 08:15:56:754 760 5d8 Agent *** START *** Queueing Finding updates [CallerId = AutomaticUpdates Id = 12]
2014-05-23 08:15:56:769 760 5d8 AU <<## SUBMITTED ## AU: Search for updates [CallId = {0EA90D1A-5EFD-46BD-89A5-5BA637FD2BAB} ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}]
2014-05-23 08:15:56:769 760 5d8 Agent SkipSelfUpdateCheck search flag set for serverId: 117CAB2D-82B1-4B5A-A08C-4D62DBEE7782
2014-05-23 08:15:56:769 760 5d8 IdleTmr WU operation (CSearchCall::Init ID 13) started; operation # 75; does not use network; is at background priority
2014-05-23 08:15:56:769 760 5d8 Agent *** START *** Queueing Finding updates [CallerId = AutomaticUpdates Id = 13]
2014-05-23 08:15:56:769 760 5d8 AU <<## SUBMITTED ## AU: Search for updates [CallId = {4BA76BFE-3776-4A2A-8F8F-046C551FC154} ServiceId = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}]
2014-05-23 08:15:56:769 760 438 Agent *** END *** Queueing Finding updates [CallerId = AutomaticUpdates Id = 12]
2014-05-23 08:15:56:769 760 444 Agent *** END *** Queueing Finding updates [CallerId = AutomaticUpdates Id = 13]
2014-05-23 08:15:56:895 760 438 Agent *************
2014-05-23 08:15:56:895 760 444 Agent *************
2014-05-23 08:15:56:895 760 438 Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates Id = 12]
2014-05-23 08:15:56:895 760 444 Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates Id = 13]
2014-05-23 08:15:56:895 760 438 Agent *********
2014-05-23 08:15:56:895 760 444 Agent *********
2014-05-23 08:15:56:895 760 438 Agent   * Online = No; Ignore download priority = No
2014-05-23 08:15:56:895 760 444 Agent   * Online = No; Ignore download priority = No
2014-05-23 08:15:56:988 760 438 Agent   * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1
or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2014-05-23 08:15:56:988 760 444 Agent   * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1
or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2014-05-23 08:15:56:988 760 438 Agent   * ServiceID = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7} Managed
2014-05-23 08:15:56:988 760 444 Agent   * ServiceID = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} Third party service
2014-05-23 08:15:56:988 760 438 Agent   * Search Scope = {Machine & All Users}
2014-05-23 08:15:56:988 760 444 Agent   * Search Scope = {Machine & All Users}
2014-05-23 08:15:56:988 760 438 Agent   * Caller SID for Applicability: S-1-5-18
2014-05-23 08:15:57:066 760 444 Agent   * Caller SID for Applicability: S-1-5-18
2014-05-23 08:16:00:691 760 444 Agent   * Added update {B8041E56-C00A-45F8-81FB-D73AFA411347}.1 to search result
2014-05-23 08:16:00:754 760 444 Agent   * Added update {00563009-B9BF-43A4-8B4E-5ACE3172912B}.2 to search result
2014-05-23 08:16:00:754 760 444 Agent   * Added update {10ABC605-BFEB-4C77-86F6-3E4B128DB8CE}.1 to search result
2014-05-23 08:16:00:754 760 444 Agent   * Added update {5FFBBD0B-FE88-4891-A8AC-079773A2293C}.1 to search result
2014-05-23 08:16:00:770 760 444 Agent   * Added update {7808BE23-84F0-4A32-8733-E7C007F163F3}.1 to search result
2014-05-23 08:16:00:770 760 444 Agent   * Added update {5844AE0C-7736-4D29-A625-BE4C5B8F8913}.1 to search result
2014-05-23 08:16:00:770 760 444 Agent Update {EE38AC4D-7401-43C8-99E3-6A29B5D40125}.1 is pruned out due to potential supersedence
2014-05-23 08:16:00:770 760 444 Agent   * Added update {F9158DB5-472A-42E4-9011-8755FFD0E881}.1 to search result
2014-05-23 08:16:00:770 760 444 Agent   * Added update {B668ABF0-E6EA-4A46-8295-F0B3EA7A2280}.1 to search result
2014-05-23 08:16:00:770 760 444 Agent   * Added update {384F16CE-2C01-40C5-B4DF-77494AF5101B}.1 to search result
2014-05-23 08:16:00:770 760 444 Agent   * Added update {622DDF33-E2CC-4001-8F24-58CF7DCA850C}.1 to search result
2014-05-23 08:16:00:770 760 444 Agent   * Added update {27F89739-5050-4ED7-BB07-1B34FAD4A662}.1 to search result
2014-05-23 08:16:00:770 760 444 Agent   * Added update {9A0D7060-5FF4-4842-AAC2-6B7F3EC4FAC3}.1 to search result
2014-05-23 08:16:00:785 760 444 Agent   * Found 12 updates and 37 categories in search; evaluated appl. rules of 81 out of 122 deployed entities
2014-05-23 08:16:00:785 760 444 Agent *********
2014-05-23 08:16:00:785 760 444 Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates Id = 13]
2014-05-23 08:16:00:785 760 444 Agent *************
2014-05-23 08:16:00:820 760 444 IdleTmr WU operation (CSearchCall::Init ID 14) started; operation # 76; does not use network; is at background priority
2014-05-23 08:16:00:898 760 444 Agent *************
2014-05-23 08:16:00:898 760 444 Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates Id = 14]
2014-05-23 08:16:00:898 760 444 Agent *********
2014-05-23 08:16:00:898 760 444 Agent   * Online = No; Ignore download priority = No
2014-05-23 08:16:00:913 760 444 Agent   * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1
or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2014-05-23 08:16:00:913 760 444 Agent   * ServiceID = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} Third party service
2014-05-23 08:16:00:913 760 444 Agent   * Search Scope = {Current User}
2014-05-23 08:16:00:913 760 444 Agent   * Caller SID for Applicability: S-1-5-21-3625400098-2596169022-3213286213-1003
2014-05-23 08:16:01:429 760 444 Agent   * Added update {B8041E56-C00A-45F8-81FB-D73AFA411347}.1 to search result
2014-05-23 08:16:02:070 760 444 Agent   * Added update {00563009-B9BF-43A4-8B4E-5ACE3172912B}.2 to search result
2014-05-23 08:16:02:070 760 444 Agent   * Added update {10ABC605-BFEB-4C77-86F6-3E4B128DB8CE}.1 to search result
2014-05-23 08:16:02:070 760 444 Agent   * Added update {5FFBBD0B-FE88-4891-A8AC-079773A2293C}.1 to search result
2014-05-23 08:16:02:070 760 444 Agent   * Added update {7808BE23-84F0-4A32-8733-E7C007F163F3}.1 to search result
2014-05-23 08:16:02:070 760 444 Agent   * Added update {5844AE0C-7736-4D29-A625-BE4C5B8F8913}.1 to search result
2014-05-23 08:16:02:070 760 444 Agent Update {EE38AC4D-7401-43C8-99E3-6A29B5D40125}.1 is pruned out due to potential supersedence
2014-05-23 08:16:02:070 760 444 Agent   * Added update {F9158DB5-472A-42E4-9011-8755FFD0E881}.1 to search result
2014-05-23 08:16:02:070 760 444 Agent   * Added update {B668ABF0-E6EA-4A46-8295-F0B3EA7A2280}.1 to search result
2014-05-23 08:16:02:070 760 444 Agent   * Added update {384F16CE-2C01-40C5-B4DF-77494AF5101B}.1 to search result
2014-05-23 08:16:02:070 760 444 Agent   * Added update {622DDF33-E2CC-4001-8F24-58CF7DCA850C}.1 to search result
2014-05-23 08:16:02:070 760 444 Agent   * Added update {27F89739-5050-4ED7-BB07-1B34FAD4A662}.1 to search result
2014-05-23 08:16:02:070 760 444 Agent   * Added update {9A0D7060-5FF4-4842-AAC2-6B7F3EC4FAC3}.1 to search result
2014-05-23 08:16:02:070 760 444 Agent   * Found 12 updates and 37 categories in search; evaluated appl. rules of 81 out of 122 deployed entities
2014-05-23 08:16:02:070 760 444 Agent *********
2014-05-23 08:16:02:070 760 444 Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates Id = 14]
2014-05-23 08:16:02:070 760 444 Agent *************
2014-05-23 08:16:02:070 760 444 IdleTmr WU operation (CSearchCall::Init ID 14, operation # 76) stopped; does not use network; is at background priority
2014-05-23 08:16:02:085 760 444 IdleTmr WU operation (CSearchCall::Init ID 15) started; operation # 77; does not use network; is at background priority
2014-05-23 08:16:02:085 760 444 Agent *************
2014-05-23 08:16:02:085 760 444 Agent ** START ** Agent: Finding updates [CallerId = AutomaticUpdates Id = 15]
2014-05-23 08:16:02:085 760 444 Agent *********
2014-05-23 08:16:02:085 760 444 Agent   * Online = No; Ignore download priority = No
2014-05-23 08:16:02:085 760 444 Agent   * Criteria = "IsInstalled=0 and DeploymentAction='Installation' or IsPresent=1 and DeploymentAction='Uninstallation' or IsInstalled=1 and DeploymentAction='Installation' and RebootRequired=1
or IsInstalled=0 and DeploymentAction='Uninstallation' and RebootRequired=1"
2014-05-23 08:16:02:085 760 444 Agent   * ServiceID = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782} Third party service
2014-05-23 08:16:02:085 760 444 Agent   * Search Scope = {Current User}
2014-05-23 08:16:02:085 760 444 Agent   * Caller SID for Applicability: S-1-5-21-3625400098-2596169022-3213286213-1001
2014-05-23 08:16:03:054 760 444 Agent   * Added update {B8041E56-C00A-45F8-81FB-D73AFA411347}.1 to search result
2014-05-23 08:16:03:116 760 444 Agent   * Added update {10ABC605-BFEB-4C77-86F6-3E4B128DB8CE}.1 to search result
2014-05-23 08:16:03:116 760 444 Agent   * Added update {5FFBBD0B-FE88-4891-A8AC-079773A2293C}.1 to search result
2014-05-23 08:16:03:116 760 444 Agent   * Added update {7808BE23-84F0-4A32-8733-E7C007F163F3}.1 to search result
2014-05-23 08:16:03:116 760 444 Agent   * Added update {5844AE0C-7736-4D29-A625-BE4C5B8F8913}.1 to search result
2014-05-23 08:16:03:116 760 444 Agent Update {EE38AC4D-7401-43C8-99E3-6A29B5D40125}.1 is pruned out due to potential supersedence
2014-05-23 08:16:03:116 760 444 Agent   * Added update {F9158DB5-472A-42E4-9011-8755FFD0E881}.1 to search result
2014-05-23 08:16:03:132 760 444 Agent   * Added update {B668ABF0-E6EA-4A46-8295-F0B3EA7A2280}.1 to search result
2014-05-23 08:16:03:132 760 444 Agent   * Added update {384F16CE-2C01-40C5-B4DF-77494AF5101B}.1 to search result
2014-05-23 08:16:03:132 760 444 Agent   * Added update {622DDF33-E2CC-4001-8F24-58CF7DCA850C}.1 to search result
2014-05-23 08:16:03:132 760 444 Agent   * Added update {27F89739-5050-4ED7-BB07-1B34FAD4A662}.1 to search result
2014-05-23 08:16:03:132 760 444 Agent   * Added update {9A0D7060-5FF4-4842-AAC2-6B7F3EC4FAC3}.1 to search result
2014-05-23 08:16:03:132 760 444 Agent   * Found 11 updates and 37 categories in search; evaluated appl. rules of 81 out of 122 deployed entities
2014-05-23 08:16:03:132 760 444 Agent *********
2014-05-23 08:16:03:132 760 444 Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates Id = 15]
2014-05-23 08:16:03:132 760 444 Agent *************
2014-05-23 08:16:03:132 760 444 IdleTmr WU operation (CSearchCall::Init ID 15, operation # 77) stopped; does not use network; is at background priority
2014-05-23 08:16:03:132 760 444 IdleTmr WU operation (CSearchCall::Init ID 13, operation # 75) stopped; does not use network; is at background priority
2014-05-23 08:16:03:132 760 484 AU >>## RESUMED ## AU: Search for updates [CallId = {4BA76BFE-3776-4A2A-8F8F-046C551FC154} ServiceId = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}]
2014-05-23 08:16:03:148 760 484 AU   # 12 updates detected
2014-05-23 08:16:03:148 760 484 AU #########
2014-05-23 08:16:03:163 760 484 AU ## END ## AU: Search for updates [CallId = {4BA76BFE-3776-4A2A-8F8F-046C551FC154} ServiceId = {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}]
2014-05-23 08:16:03:163 760 484 AU #############
2014-05-23 08:16:08:679 760 438 Agent   * Added update {8427071A-DA80-48C3-97DE-C9C528F73A2D}.1 to search result
2014-05-23 08:16:08:742 760 438 Agent   * Found 1 updates and 74 categories in search; evaluated appl. rules of 1114 out of 1607 deployed entities
2014-05-23 08:16:08:742 760 438 Agent *********
2014-05-23 08:16:08:742 760 438 Agent ** END ** Agent: Finding updates [CallerId = AutomaticUpdates Id = 12]
2014-05-23 08:16:08:742 760 438 Agent *************
2014-05-23 08:16:08:742 760 438 IdleTmr WU operation (CSearchCall::Init ID 12, operation # 73) stopped; does not use network; is at background priority
2014-05-23 08:16:08:742 760 484 AU >>## RESUMED ## AU: Search for updates [CallId = {0EA90D1A-5EFD-46BD-89A5-5BA637FD2BAB} ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}]
2014-05-23 08:16:08:742 760 484 AU   # 1 updates detected
2014-05-23 08:16:08:742 760 484 AU WARNING: AU ignoring update during offline scan:
2014-05-23 08:16:08:742 760 484 AU #########
2014-05-23 08:16:08:742 760 484 AU ## END ## AU: Search for updates [CallId = {0EA90D1A-5EFD-46BD-89A5-5BA637FD2BAB} ServiceId = {3DA21691-E39D-4DA6-8A4B-B43877BCB1B7}]
2014-05-23 08:16:08:742 760 484 AU #############
2014-05-23 08:16:08:742 760 484 AU All AU searches complete.
2014-05-23 08:16:08:742 760 484 AU Adding timer:
2014-05-23 08:16:08:742 760 484 AU     Timer: 31DA7559-FE27-4810-8FF6-987195B1FD98, Expires 2014-05-24 02:26:02, not idle-only, not network-only
2014-05-23 08:16:08:742 760 484 AU   # Publishing WNF Per user update count event Count: 11 SID {S-1-5-21-3625400098-2596169022-3213286213-1003} Service {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}
2014-05-23 08:16:08:804 760 484 AU   # Publishing WNF Per user update count event Count: 11 SID {S-1-5-21-3625400098-2596169022-3213286213-1001} Service {117CAB2D-82B1-4B5A-A08C-4D62DBEE7782}
2014-05-23 08:24:06:607 760 5d8 AU ReAttemptDownloadsAsUserIfNecessary, No calls in download progress.
2014-05-23 08:24:06:623 760 5d8 AU IsPerUserUpdateInstallableForAnyLoggedOnUser, found at least 1 logged on user for which the update 10ABC605-BFEB-4C77-86F6-3E4B128DB8CE, revision 1 is applicable
2014-05-23 08:24:06:623 760 5d8 AU SchedulePerUserUpdateInstallOnUserLogonIfNeeded, per user update install scheduled for logged on user.
Kind regards / Met vriendelijke groet, IS Group Rob Mulder Kantoorautomatiseerder Wielingenstraat 8 T 0299 476 185 1441 ZR Purmerend F 0299 476 288 www.is.nl / www.isenterprise.com KvK Hoorn 36049256

BizTalk Server 2013 and deployment MSI with dynamic send ports

Hello community, wonder if any help out there for this odd problem.
Deployment of application msi fails into BizTalk 2013 prod environment, fails when deploying the project dll that contains all the orchestrations,
and reports a failure to apply early bindings. The only early bindings in this project are dynamic send ports. I cannot recreate the problem in in my QAS environment where deployments of the same msi works fine.
I can build an msi without any bindings at all except for the dynamically created ones, and this also display the same behaviour on import.
I have test deployed a 2nd unrelated app that also uses dynamic send ports, and this displays the problem.
Adding the assembly directly to BizTalk console displays the same behaviour.
Deployment of msi apps without dynamic send ports are ok.
The dynamic ports use a pipeline including a custom pipeline component which I can confirm is available in the correct directory
C:\Program Files (x86)\Microsoft BizTalk Server 2013\Pipeline Components
No specific further detail is available in the error except.
Import Wizard[09/05/2014 08:20:47]: Error in Importing Application
Import Wizard[09/05/2014 08:20:47]: Change requests failed for some resources.
BizTalkAssemblyResourceManager failed to complete end type change request.
Unable to deploy early bindings.
Failed to update binding information.
Error in the application.
Other information that may be relevant:
The main difference between QAS and PROD is that PROD is a two node cluster. Import behaviour is the same if attempted on either node. Assemblies are installed in both nodes currently.
The dynamic ports are set on handlers that are non-clustered hosts (all are for adapter type SMTP).
I have ensured that all the adapter handlers are identically setup in both environments.
The project files were migrated to BizTalk 2013 from BizTalk 2010, imported and then converted using VS 2012.
The msi has installed the assemblies as per usual and they do exist in the .net 4 gac
There is a reference to a shared resource in a different application, this application is installed and imported ok.
I’m a bit stuck at what to try now, I have option where I could recreate the dynamic ports from scratch in the orchestrations and redeploy to dev in the hope it’s something that VS2012 didn’t handle too gracefully
when converting the project. I could move the functionality into a helper class and forget about using dynamic sends, rather not go down that route. I'm still suspecting this is small difference in setup
of the group between QAS and PROD but I can't see anything jumping out.
Any comments are most welcome.

The dynamic ports use a pipeline including a custom pipeline component which I can confirm is available in the correct directory
C:\Program Files (x86)\Microsoft BizTalk Server 2013\Pipeline Components
I’m a bit stuck at what to try now, I have option where I could recreate the dynamic ports from scratch in the orchestrations and redeploy to dev in the hope it’s something
that VS2012 didn’t handle too gracefully when converting the project.
Two things.
1. That's what I would do first, recreate (really just change and reset the properties) the Orchestration Ports in Visual Studio.
2. Probably not related but, Custom Pipeline Components should not be placed in the Pipeline Components folder. All Custom Pipeline Components should be in the GAC only. The Pipeline Components folder
is a compatibility vestige from BizTalk Server 2004.

AS2 ID and URL in BizTalk Server 2009

Similar Messages

Maybe you are looking for