I/o server 2009

Hello, I am trying to use the I/O server in Labview 2009 to do Modbus communication and I do not understand how it works. Does anyone have information on this and/or examples that I could use?
Thank you very much!
-Jeremy

Jeremy,
I/O Servers allow you to communicate with various external sources of data, such as OPC servers or Modbus devices, through shared variables.  Basically, once you create your I/O Server for a Modbus device, you'll create bound shared variables for the Modbus data items.  Here are a couple of items on how to configure and use Modbus I/O Servers:
Configure Modbus I/O Server Dialog Box
Using Modbus I/O Servers (DSC Module or RT Module
I hope that helps you get started with them. 
Jared S.
Applications Engineering
National Instruments

Similar Messages

  • 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,

  • 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. 

  • 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.

  • Server 2009 R2 Stuck Installing Updates and Unexpected Error Refreshing Server Manager

    I have a 2008 R2 server that is running but has issues when restarting or trying to install IE 10. I ran the System Readiness Tool and it fixed a number of issues but there are 5 remaining errors in the Component store that will not repair automatically. 
    They are:
    Checking Component Store
    (f) CSI Missing Identity 0x00000000 appid win7-micros..anguagepack_31bf3856ad364e35_7.1.7601.16492_eb5d85075a07f78b 
    (f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft-windows-directx-direct3d11_31bf3856ad364e35_7.1.7601.16492_none_3ef665796f74e084  
    (f) CSI Missing Winning Component Key 0x00000000 x86_microsoft-windows-directx-direct3d11_31bf3856ad364e35_7.1.7601.16492_none_e2d7c9f5b7176f4e  
    (f) CSI Missing Winning Component Key 0x00000000 x86_microsoft-windows-activexcompat_31bf3856ad364e35_8.0.7601.18126_none_13026217d8d91020  
    (f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft-windows-activexcompat_31bf3856ad364e35_8.0.7601.18126_none_6f20fd9b91368156  
    I tried to run a SFC but if failed because there is a repair operation that needs a reboot.  When rebooting, the server tries to install a number of updates but the update fail and the server backs them out and then comes up.  It goes through this
    loop every restart.  There is a pending.xml file that has much in it and I will copy at the end of this post.
    I moved the pending.xml out of the winsxs folder and tried to run the SFC again and now it fails with: "Windows Resource Protection could not perform the requested operation".
    Checking windows updates shows that the IE 10 upgrade for Server 2008 R2 failed a number of times.  I tried to manually install it and it fails.  I was going to go to the server manager and see if I could disable IE and then re-enable it (this
    has worked on W7 pcs in the past) but the Server manager aborts with "Unexpected Error refreshing Server Manager: Catastrophic failure (Exception from HResult: 0x8000FFFF (E_UNEXPECTED)).
    The details of the pending.xml is 32MB but here is an initial snipet:
    <?xml version='1.0' encoding='utf-8'?>
    <PendingTransaction Version="3.1" WcpVersion="6.1.7601.17592 (win7sp1_gdr.110408-1631)" Identifier="9afdc4c419d7ce01476300001c0cb817">
        <Transactions>
            <Transaction TransactionId="TI4.30332431_1303162608:4/Package_for_KB2884256~31bf3856ad364e35~amd64~~6.1.1.1">
                <Install Application="mdmnis2u.inf, Culture=neutral, Type=driverUpdate, Version=6.1.7601.18247, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_1_for_KB2884256~31bf3856ad364e35~amd64~~6.1.1.1.2884256-2_neutral_GDR" RefExtra="16"/>
                <Install Application="mdmnis1u.inf, Culture=neutral, Type=driverUpdate, Version=6.1.7601.18247, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_1_for_KB2884256~31bf3856ad364e35~amd64~~6.1.1.1.2884256-4_neutral_GDR" RefExtra="16"/>
                <Install Application="mdmgen.inf, Culture=neutral, Type=driverUpdate, Version=6.1.7601.18247, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_1_for_KB2884256~31bf3856ad364e35~amd64~~6.1.1.1.2884256-6_neutral_GDR" RefExtra="16"/>
                <Install Application="mdmcpq.inf, Culture=neutral, Type=driverUpdate, Version=6.1.7601.18247, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_1_for_KB2884256~31bf3856ad364e35~amd64~~6.1.1.1.2884256-8_neutral_GDR" RefExtra="2"/>
            </Transaction>
            <Transaction TransactionId="TI4.30332431_1357902608:4/Package_for_KB2853587~31bf3856ad364e35~amd64~~6.1.1.2">
                <Install Application="e30c96e70bb8831ddd580ec5531db3e7, Culture=neutral, Version=6.1.7601.18219, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_2_for_KB2853587~31bf3856ad364e35~amd64~~6.1.1.2.2853587-4_neutral_GDR" RefExtra="2"/>
            </Transaction>
            <Transaction TransactionId="TI4.30332431_1359952608:4/Package_for_KB2736422~31bf3856ad364e35~amd64~~6.1.1.0">
                <Install Application="838a6900433638745b282fd8a4ba817a, Culture=neutral, Version=6.1.7601.17933, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_1_for_KB2736422~31bf3856ad364e35~amd64~~6.1.1.0.2736422-3_neutral_GDR" RefExtra="2"/>
                <Install Application="50fab9749cbc66134f38ae1dc56c98dd, Culture=neutral, Version=6.1.7601.17933, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_1_for_KB2736422~31bf3856ad364e35~amd64~~6.1.1.0.2736422-6_neutral_GDR" RefExtra="2"/>
                <Install Application="ff3f54cca48812ca511cd304f4431436, Culture=neutral, Version=6.1.7601.17933, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_1_for_KB2736422~31bf3856ad364e35~amd64~~6.1.1.0.2736422-8_neutral_GDR" RefExtra="2"/>
                <Install Application="6ea506ab96b6a14822c1c2ab6846fc8f, Culture=neutral, Version=6.1.7601.17933, PublicKeyToken=b77a5c561934e089, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_2_for_KB2736422~31bf3856ad364e35~amd64~~6.1.1.0.2736422-10_neutral_GDR" RefExtra="2"/>
                <Install Application="87e192610d63f582a53ceb1723d390ab, Culture=neutral, Version=6.1.7601.17933, PublicKeyToken=b77a5c561934e089, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_2_for_KB2736422~31bf3856ad364e35~amd64~~6.1.1.0.2736422-12_neutral_GDR" RefExtra="2"/>
                <Install Application="4a1985f0141fae9c7cae493197a6b878, Culture=neutral, Version=6.1.7601.17933, PublicKeyToken=b77a5c561934e089, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_2_for_KB2736422~31bf3856ad364e35~amd64~~6.1.1.0.2736422-14_neutral_GDR" RefExtra="2"/>
                <Install Application="016dd2fdac3816d0990ef71a86b49ca5, Culture=neutral, Version=6.1.7601.17933, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_3_for_KB2736422~31bf3856ad364e35~amd64~~6.1.1.0.2736422-17_neutral_GDR" RefExtra="2"/>
                <Install Application="a37f333ec2c8fbbf96c5ecfffad21444, Culture=neutral, Version=6.1.7601.17933, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_3_for_KB2736422~31bf3856ad364e35~amd64~~6.1.1.0.2736422-20_neutral_GDR" RefExtra="2"/>
            </Transaction>
            <Transaction TransactionId="TI4.30332431_1370242608:4/Package_for_KB2726535~31bf3856ad364e35~amd64~~6.1.1.1">
                <Install Application="8e09fc8e70ef526fe271bb58df1b359b, Culture=neutral, Version=6.1.7601.18015, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_38_for_KB2726535~31bf3856ad364e35~amd64~~6.1.1.1.2726535-149_neutral_GDR" RefExtra="17"/>
                <Install Application="5e964ab696366f5925e35f48bce2e817, Culture=neutral, Version=6.1.7601.18015, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_39_for_KB2726535~31bf3856ad364e35~amd64~~6.1.1.1.2726535-152_neutral_GDR" RefExtra="16"/>
                <Install Application="e7ec7425bc5783cd10ed371bbb5001dd, Culture=neutral, Version=6.1.7601.18015, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_39_for_KB2726535~31bf3856ad364e35~amd64~~6.1.1.1.2726535-155_neutral_GDR" RefExtra="16"/>
                <Install Application="c4861d635189a7cabac3e380ad0cc01f, Culture=neutral, Version=6.1.7601.18015, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_59_for_KB2726535~31bf3856ad364e35~amd64~~6.1.1.1.2726535-272_neutral_GDR" RefExtra="17"/>
                <Install Application="36b758890f2cc03ad4c1f7b69ba4b785, Culture=neutral, Version=6.1.7601.18015, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_75_for_KB2726535~31bf3856ad364e35~amd64~~6.1.1.1.2726535-364_neutral_GDR" RefExtra="3"/>
                <Install Application="2e15e374d2e2b02519eb2bc107d92452, Culture=neutral, Version=6.1.7601.18015, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_75_for_KB2726535~31bf3856ad364e35~amd64~~6.1.1.1.2726535-367_neutral_GDR" RefExtra="3"/>
                <Install Application="79efe25214ed979d4739ffca9cef136f, Culture=neutral, Version=6.1.7601.18015, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_76_for_KB2726535~31bf3856ad364e35~amd64~~6.1.1.1.2726535-370_neutral_GDR" RefExtra="16"/>
                <Install Application="b8cda4a0fbf72009baf7a4d31ebb7e3f, Culture=neutral, Version=6.1.7601.18015, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_76_for_KB2726535~31bf3856ad364e35~amd64~~6.1.1.1.2726535-373_neutral_GDR" RefExtra="16"/>
            </Transaction>
            <Transaction TransactionId="TI4.30332431_1428402608:4/Package_for_KB2847311~31bf3856ad364e35~amd64~~6.1.1.2">
                <Install Application="65d33ad308914579e80ef4e979752b4e, Culture=neutral, Version=6.1.7601.18177, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_2_for_KB2847311~31bf3856ad364e35~amd64~~6.1.1.2.2847311-5_neutral_GDR" RefExtra="2"/>
                <Install Application="449dd8313096e8ea0b2798f052e79452, Culture=neutral, Version=6.1.7601.18177, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_3_for_KB2847311~31bf3856ad364e35~amd64~~6.1.1.2.2847311-8_neutral_GDR" RefExtra="2"/>
            </Transaction>
            <Transaction TransactionId="TI4.30332431_1441832608:4/Package_for_KB2832414~31bf3856ad364e35~amd64~~6.1.1.2">
                <Install Application="0f6c352b3b8ab87d68b593ef7f08823f, Culture=neutral, Version=6.1.7601.18140, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_1_for_KB2832414~31bf3856ad364e35~amd64~~6.1.1.2.2832414-2_neutral_GDR" RefExtra="3"/>
                <Install Application="8a9b3736ee0dfd9a2d51fe6ecb8262b9, Culture=neutral, Version=6.1.7601.18140, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_1_for_KB2832414~31bf3856ad364e35~amd64~~6.1.1.2.2832414-4_neutral_GDR" RefExtra="3"/>
                <Install Application="f03bb92dd4f91f6ca1fea9aa5f3d01f6, Culture=neutral, Version=6.1.7601.18140, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_1_for_KB2832414~31bf3856ad364e35~amd64~~6.1.1.2.2832414-6_neutral_GDR" RefExtra="3"/>
                <Install Application="d985d750c9b4e2d9ac9a71db0b5caeca, Culture=neutral, Version=6.1.7601.18140, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_1_for_KB2832414~31bf3856ad364e35~amd64~~6.1.1.2.2832414-8_neutral_GDR" RefExtra="3"/>
                <Install Application="4564761e21602085599bee5eebe25ff9, Culture=neutral, Version=6.1.7601.18140, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_1_for_KB2832414~31bf3856ad364e35~amd64~~6.1.1.2.2832414-10_neutral_GDR" RefExtra="3"/>
                <Install Application="3b2d92a9b35c82a0178c4a63bc04bfd0, Culture=neutral, Version=6.1.7601.18140, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_1_for_KB2832414~31bf3856ad364e35~amd64~~6.1.1.2.2832414-12_neutral_GDR" RefExtra="3"/>
                <Install Application="c41ad6a9882c5db61704dffad48784e4, Culture=neutral, Version=6.1.7601.18140, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_1_for_KB2832414~31bf3856ad364e35~amd64~~6.1.1.2.2832414-14_neutral_GDR" RefExtra="3"/>
                <Install Application="b9b638b3db7627f18507dfafb2c78403, Culture=neutral, Version=6.1.7601.18140, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_1_for_KB2832414~31bf3856ad364e35~amd64~~6.1.1.2.2832414-16_neutral_GDR" RefExtra="2"/>
                <Install Application="54ae1ba9684b6049e8d67dcdc4f58954, Culture=neutral, Version=6.1.7601.18140, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_1_for_KB2832414~31bf3856ad364e35~amd64~~6.1.1.2.2832414-18_neutral_GDR" RefExtra="2"/>
                <Install Application="4f41d944af2db3f0120fc02c77158999, Culture=neutral, Version=6.1.7601.18140, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_1_for_KB2832414~31bf3856ad364e35~amd64~~6.1.1.2.2832414-20_neutral_GDR" RefExtra="2"/>
            </Transaction>
            <Transaction TransactionId="TI4.30332431_1462782608:4/Package_for_KB2836943~31bf3856ad364e35~amd64~~6.1.2.0">
                <Install Application="588b833b8de1c71547d6a889dbb75439, Culture=neutral, Version=6.1.7601.18205, PublicKeyToken=b03f5f7f11d50a3a, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_1_for_KB2836943~31bf3856ad364e35~amd64~~6.1.2.0.2836943-3_neutral_GDR" RefExtra="2"/>
                <Install Application="0c2bb2bb69a4efa72cf82d30ab59e369, Culture=neutral, Version=6.1.7601.18205, PublicKeyToken=b03f5f7f11d50a3a, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_1_for_KB2836943~31bf3856ad364e35~amd64~~6.1.2.0.2836943-6_neutral_GDR" RefExtra="2"/>
                <Install Application="206b27624daebef1bb13dfa8dd6da833, Culture=neutral, Version=6.1.7601.18205, PublicKeyToken=b03f5f7f11d50a3a, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_1_for_KB2836943~31bf3856ad364e35~amd64~~6.1.2.0.2836943-8_neutral_GDR" RefExtra="16"/>
                <Install Application="bf6e4fabe941322fa7c42cb2ce5ab035, Culture=neutral, Version=6.1.7601.18205, PublicKeyToken=b03f5f7f11d50a3a, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_1_for_KB2836943~31bf3856ad364e35~amd64~~6.1.2.0.2836943-11_neutral_GDR" RefExtra="2"/>
                <Install Application="772cf3ed88bc1b0fc9931ec07075f86d, Culture=neutral, Version=6.1.7601.18205, PublicKeyToken=b03f5f7f11d50a3a, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_2_for_KB2836943~31bf3856ad364e35~amd64~~6.1.2.0.2836943-13_neutral_GDR" RefExtra="16"/>
                <Install Application="119d2a1cf82292079aacac2e30f2c14c, Culture=neutral, Version=6.1.7601.18205, PublicKeyToken=b03f5f7f11d50a3a, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_3_for_KB2836943~31bf3856ad364e35~amd64~~6.1.2.0.2836943-16_neutral_GDR" RefExtra="2"/>
                <Install Application="8c3eb9ca2caa78fb873d66d3c41a68c5, Culture=neutral, Version=6.1.7601.18205, PublicKeyToken=b03f5f7f11d50a3a, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_3_for_KB2836943~31bf3856ad364e35~amd64~~6.1.2.0.2836943-19_neutral_GDR" RefExtra="2"/>
                <Install Application="303a1ce634b3a16c69749f5139be8471, Culture=neutral, Version=6.1.7601.18205, PublicKeyToken=b03f5f7f11d50a3a, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_3_for_KB2836943~31bf3856ad364e35~amd64~~6.1.2.0.2836943-22_neutral_GDR" RefExtra="2"/>
                <Install Application="2be7629126ed2b6468203097350f0dfe, Culture=neutral, Version=6.1.7601.18205, PublicKeyToken=b03f5f7f11d50a3a, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_5_for_KB2836943~31bf3856ad364e35~amd64~~6.1.2.0.2836943-26_neutral_GDR" RefExtra="16"/>
            </Transaction>
            <Transaction TransactionId="TI4.30332431_1488382608:4/Package_for_KB2888049~31bf3856ad364e35~amd64~~6.1.1.1">
                <Install Application="6f20d92a7648d71eb43ee35ded059bb1, Culture=neutral, Version=6.1.7601.18254, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_2_for_KB2888049~31bf3856ad364e35~amd64~~6.1.1.1.2888049-9_neutral_GDR" RefExtra="2"/>
                <Install Application="f0ed83bda0697abd97fd471015aed5c2, Culture=neutral, Version=6.1.7601.17939, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_2_for_KB2888049~31bf3856ad364e35~amd64~~6.1.1.1.2888049-12_neutral_GDR" RefExtra="16"/>
                <Install Application="febe4281e112cc22eaba92dbd2b4d55c, Culture=neutral, Version=6.1.7601.18254, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_3_for_KB2888049~31bf3856ad364e35~amd64~~6.1.1.1.2888049-15_neutral_GDR" RefExtra="2"/>
                <Install Application="2f9f4d4b3253a56c28a30f0cb9598076, Culture=neutral, Version=6.1.7601.18264, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_3_for_KB2888049~31bf3856ad364e35~amd64~~6.1.1.1.2888049-17_neutral_GDR" RefExtra="2"/>
                <Install Application="6cccd8f687e69c579827fb5568f5bd2a, Culture=neutral, Version=6.1.7601.17939, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_3_for_KB2888049~31bf3856ad364e35~amd64~~6.1.1.1.2888049-20_neutral_GDR" RefExtra="3"/>
            </Transaction>
            <Transaction TransactionId="TI4.30332431_1507982608:4/Package_for_KB2861191~31bf3856ad364e35~amd64~~6.1.1.0">
                <Install Application="98968d78510963c63353649885f3ecf0, Culture=neutral, Version=6.1.7601.18219, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_1_for_KB2861191~31bf3856ad364e35~amd64~~6.1.1.0.2861191-2_neutral_GDR" RefExtra="17"/>
            </Transaction>
            <Transaction TransactionId="TI4.30332431_1608052608:4/Package_for_KB2872339~31bf3856ad364e35~amd64~~6.1.1.1">
                <Install Application="4eac8b2780d12dcb68dc93ac25ddea50, Culture=neutral, Version=6.1.7601.18229, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_2_for_KB2872339~31bf3856ad364e35~amd64~~6.1.1.1.2872339-9_neutral_GDR" RefExtra="17"/>
                <Install Application="f3f2fab1a47c8f10dba321b4564b5da2, Culture=neutral, Version=6.1.7601.18229, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_3_for_KB2872339~31bf3856ad364e35~amd64~~6.1.1.1.2872339-12_neutral_GDR" RefExtra="17"/>
                <Install Application="5683dbcbaaf84c80d448b8e4ff5c4102, Culture=neutral, Version=6.1.7601.18229, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_3_for_KB2872339~31bf3856ad364e35~amd64~~6.1.1.1.2872339-15_neutral_GDR" RefExtra="2"/>
                <Install Application="6a6f4875757b66f16c6a4827a5d031c4, Culture=neutral, Version=6.1.7601.18229, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_3_for_KB2872339~31bf3856ad364e35~amd64~~6.1.1.1.2872339-18_neutral_GDR" RefExtra="16"/>
                <Install Application="ed4721225b1075dc927cca1f55a4feb7, Culture=neutral, Version=6.1.7601.18229, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_4_for_KB2872339~31bf3856ad364e35~amd64~~6.1.1.1.2872339-21_neutral_GDR" RefExtra="2"/>
                <Install Application="8be73aa5d92530e63a3fa2360881e888, Culture=neutral, Version=6.1.7601.18229, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_5_for_KB2872339~31bf3856ad364e35~amd64~~6.1.1.1.2872339-24_neutral_GDR" RefExtra="17"/>
                <Install Application="5102c4e5b602cbe09557ed48ea490121, Culture=neutral, Version=6.1.7601.18229, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_5_for_KB2872339~31bf3856ad364e35~amd64~~6.1.1.1.2872339-27_neutral_GDR" RefExtra="3"/>
                <Install Application="7db7cf609e29d6d392051d1175075ae5, Culture=neutral, Version=6.1.7601.18229, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_5_for_KB2872339~31bf3856ad364e35~amd64~~6.1.1.1.2872339-30_neutral_GDR" RefExtra="2"/>
            </Transaction>
            <Transaction TransactionId="TI4.30332431_2531772608:4/Package_for_KB2834140~31bf3856ad364e35~amd64~~6.1.2.0">
                <Install Application="8a96329682d824abc0f8f934fb341ede, Culture=neutral, Version=7.1.7601.18142, PublicKeyToken=31bf3856ad364e35, ProcessorArchitecture=amd64, versionScope=NonSxS"
    RefGuid="{d16d444c-56d8-11d5-882d-0080c847b195}" RefIdentifier="Package_2_for_KB2834140~31bf3856ad364e35~amd64~~6.1.2.0.2834140-6_neutral_GDR" RefExtra=""/>
            </Transaction>
    andy

    Here is the contents of the CheckSur.log file:
    =================================
    Checking System Update Readiness.
    Binary Version 6.1.7601.22471
    Package Version 26.0
    2015-02-08 22:46
    Checking Windows Servicing Packages
    Checking Package Manifests and Catalogs
    Checking Package Watchlist
    Checking Component Watchlist
    Checking Packages
    Checking Component Store
    (f) CSI Missing Identity 0x00000000 appid win7-micros..anguagepack_31bf3856ad364e35_7.1.7601.16492_eb5d85075a07f78b 
    (f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft-windows-directx-direct3d11_31bf3856ad364e35_7.1.7601.16492_none_3ef665796f74e084  
    (f) CSI Missing Winning Component Key 0x00000000 x86_microsoft-windows-directx-direct3d11_31bf3856ad364e35_7.1.7601.16492_none_e2d7c9f5b7176f4e  
    (f) CSI Missing Winning Component Key 0x00000000 x86_microsoft-windows-activexcompat_31bf3856ad364e35_8.0.7601.18126_none_13026217d8d91020  
    (f) CSI Missing Winning Component Key 0x00000000 amd64_microsoft-windows-activexcompat_31bf3856ad364e35_8.0.7601.18126_none_6f20fd9b91368156  
    Summary:
    Seconds executed: 825
     Found 5 errors
      CSI Missing Identity Total count: 1
      CSI Missing Winning Component Key Total count: 4
    andy

  • Reconnecting macmini server 2009

    Since I moved my apartment and got a new ISP, I am unable to connect to my mac mini server.
    Mac Mini is connected to my Airport WIFI and the TA/Modem but can't access using my Imac nor
    mac book pro.
    Please help.
    Thank you,
    A

    Hello,
    Make a New Location, Using network locations in Mac OS X ...
    http://support.apple.com/kb/HT2712
    10.7…
    System Preferences>Network, top of window>Locations>Edit Locations, little plus icon, give it a name.
    10.5.x/10.6.x/10.7.x instructions...
    System Preferences>Network, click on the little gear at the bottom next to the + & - icons, (unlock lock first if locked), choose Set Service Order.
    The interface that connects to the Internet should be dragged to the top of the list.
    Instead of joining your Network from the list, click the WiFi icon at the top, and click join other network. Fill in everything as needed.
    Try turning off IPv6:
    System Preferences » Network » AirPort » TCP/IP tab » Configure IPv6
    Or for whatever Interface you use.

  • Commerce Server 2009 and BizTalk 2009

    Hi,
    Just a simple question. Will CS2009 work with BizTalk 2009? Are the adapter compatible? Where can I find the documentation for this?
    Regards
    MagnusMagnus

    We are currently working an implementation of this, and haven't found any issues, however there is no documentation that i have found yet.
    I would read this, and follow here...
    http://blogs.msdn.com/commerce/archive/2009/06/15/biztalk-2006-r2.aspx

  • 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.

  • How to enter hidden SSID in Snow Leopard Server

    I am re-installing Snow Leopard Server on a Mac Mini Server (2009) from the recovery disk.  I successfully installed, using Remote Installation.  However, it did not keep my network settings.  The SSID is hidden, so normally, I would select to enter "other network".  But, in this case, that option is not showing up. What am I missing?

    Airport was enabled; however, the network name box did not have an option to "Join Other Network". I was very surprised, because I had used Airport to remotely install the OS in the first place, and that box did have the "Join Other Network" option.
    I understand that sniffing tools, used by any network-savvy person, can easily find hidden networks. As a matter of fact, most newer network selection software distributed with network card drivers are able to find and display hidden SSIDs. I just like to use the most security I possibly can, and that's one tool at my disposal. Along with WPA2 and a strong key, the hidden SSID keeps my network out of sight and mind of the casual hacker who just wants to see what's out there to pick and poke at. They're most likely to hack at the easily displayed stuff and, hopefully, ignore what they can't see. Again, just one more tool - not the best, but not totally useless, either.

  • SQL Server 2008 Installation on Windows 7

    I tried to install SQL Server 2008 on a Windows 7 Home Premium 64 bit (Enterprise Edition Trial Edition). The system check was ok and the installation started successfully but at the end there were some errors. In the logfile there were stacktraces describing failures trying write operations on the registry. What can I do to install SQL Server 2008 on my operating system?

    Hello ChunSong Feng,
    thanks for your advice. Herewith I send you the text parts from detail.txt with the detailed error description. The whole file is too big to send as content.
    Thanks in advance:
    2009-11-17 21:05:10 Slp: ReplaceAccountWithSidInSddl -- SDDL to be returned:  D:(A;CI;KR;;;S-1-5-21-2556463381-1186548668-390171815-1028)
    2009-11-17 21:05:10 Slp: Prompting user if they want to retry this action due to the following failure:
    2009-11-17 21:05:10 Slp: ----------------------------------------
    2009-11-17 21:05:10 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
    2009-11-17 21:05:10 Slp: Inner exceptions are being indented
    2009-11-17 21:05:10 Slp:
    2009-11-17 21:05:10 Slp: Exception type: Microsoft.SqlServer.Configuration.Sco.ScoException
    2009-11-17 21:05:10 Slp:     Message:
    2009-11-17 21:05:10 Slp:         Es wurde versucht, einen nicht autorisierten Vorgang auszuführen.
    2009-11-17 21:05:10 Slp:     Data:
    2009-11-17 21:05:10 Slp:       WatsonData = Microsoft SQL Server
    2009-11-17 21:05:10 Slp:       DisableRetry = true
    2009-11-17 21:05:10 Slp:     Inner exception type: System.UnauthorizedAccessException
    2009-11-17 21:05:10 Slp:         Message:
    2009-11-17 21:05:10 Slp:                 Es wurde versucht, einen nicht autorisierten Vorgang auszuführen.
    2009-11-17 21:05:10 Slp:         Stack:
    2009-11-17 21:05:10 Slp:                 bei System.Security.AccessControl.Win32.GetSecurityInfo(ResourceType resourceType, String name, SafeHandle handle, AccessControlSections accessControlSections, RawSecurityDescriptor& resultSd)
    2009-11-17 21:05:10 Slp:                 bei System.Security.AccessControl.NativeObjectSecurity.CreateInternal(ResourceType resourceType, Boolean isContainer, String name, SafeHandle handle, AccessControlSections includeSections, Boolean createByName, ExceptionFromErrorCode exceptionFromErrorCode, Object exceptionContext)
    2009-11-17 21:05:10 Slp:                 bei Microsoft.SqlServer.Configuration.Sco.SqlRegistrySecurity..ctor(ResourceType resourceType, SafeRegistryHandle handle, AccessControlSections includeSections)
    2009-11-17 21:05:10 Slp:                 bei Microsoft.SqlServer.Configuration.Sco.SqlRegistrySecurity.Create(InternalRegistryKey key)
    2009-11-17 21:05:10 Slp:                 bei Microsoft.SqlServer.Configuration.Sco.InternalRegistryKey.SetSecurityDescriptor(String sddl, Boolean overwrite)
    2009-11-17 21:05:10 Slp: ----------------------------------------
    2009-11-17 21:05:28 Slp: User has chosen to cancel this action
    2009-11-17 21:05:30 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20091117_204850\Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_
    2009-11-17 21:05:30 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20091117_204850\Registry_SOFTWARE_Microsoft_Windows_CurrentVersion_Uninstall.reg_
    2009-11-17 21:05:30 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\MSSQLServer to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20091117_204850\Registry_SOFTWARE_Microsoft_MSSQLServer.reg_
    2009-11-17 21:05:30 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Wow6432Node\Microsoft\Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20091117_204850\Registry_SOFTWARE_Wow6432Node_Microsoft_Microsoft SQL Server.reg_
    2009-11-17 21:05:30 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20091117_204850\Registry_SOFTWARE_Wow6432Node_Microsoft_Windows_CurrentVersion_Uninstall.reg_
    2009-11-17 21:05:30 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Wow6432Node\Microsoft\MSSQLServer to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20091117_204850\Registry_SOFTWARE_Wow6432Node_Microsoft_MSSQLServer.reg_
    2009-11-17 21:05:44 Slp: Es wurde versucht, einen nicht autorisierten Vorgang auszuführen.
    2009-11-17 21:05:45 Slp: Watson bucket for exception based failure has been created
    2009-11-17 21:05:45 SQLBrowser: SQL Server Browser Install for feature 'SQL_Browser_Redist_SqlBrowser_Cpu32' failed with cancel exception: Microsoft.SqlServer.Configuration.Sco.ScoException: Es wurde versucht, einen nicht autorisierten Vorgang auszuführen. ---> System.UnauthorizedAccessException: Es wurde versucht, einen nicht autorisierten Vorgang auszuführen.
       bei System.Security.AccessControl.Win32.GetSecurityInfo(ResourceType resourceType, String name, SafeHandle handle, AccessControlSections accessControlSections, RawSecurityDescriptor& resultSd)
       bei System.Security.AccessControl.NativeObjectSecurity.CreateInternal(ResourceType resourceType, Boolean isContainer, String name, SafeHandle handle, AccessControlSections includeSections, Boolean createByName, ExceptionFromErrorCode exceptionFromErrorCode, Object exceptionContext)
       bei Microsoft.SqlServer.Configuration.Sco.SqlRegistrySecurity..ctor(ResourceType resourceType, SafeRegistryHandle handle, AccessControlSections includeSections)
       bei Microsoft.SqlServer.Configuration.Sco.SqlRegistrySecurity.Create(InternalRegistryKey key)
       bei Microsoft.SqlServer.Configuration.Sco.InternalRegistryKey.SetSecurityDescriptor(String sddl, Boolean overwrite)
       --- Ende der internen Ausnahmestapelüberwachung ---
       bei Microsoft.SqlServer.Configuration.Sco.InternalRegistryKey.SetSecurityDescriptor(String sddl, Boolean overwrite)
       bei Microsoft.SqlServer.Configuration.Sco.SqlRegistryKey.SetSecurityDescriptor(String sddl, Boolean overwrite)
       bei Microsoft.SqlServer.Configuration.SqlBrowser.SqlBrowserPrivateConfigBase.SetSecurityDescriptorByLocation(String sRegLocation, RegistryView regView, String sSddl, Boolean bOptional)
       bei Microsoft.SqlServer.Configuration.SqlBrowser.SqlBrowserPrivateConfigBase.ApplyRegPermissions(XmlNodeList xmlNodeListRegPermissions, Dictionary`2 dictionaryGroups, Dictionary`2 dicLocationFragments)
       bei Microsoft.SqlServer.Configuration.SqlBrowser.SqlBrowserPrivateConfig.ApplyRegCommonPermissions(XmlElement xmlRootPermissions, Dictionary`2 dictionaryGroups, Dictionary`2 dicLocationFragments)
       bei Microsoft.SqlServer.Configuration.SqlBrowser.SqlBrowserPrivateConfig.ApplyPermissions(String sXmlPermissionsFile, String sBrowserPrincipal)
       bei Microsoft.SqlServer.Configuration.SqlBrowser.SqlBrowserPrivateConfig.ConfigStaticProperties(SqlBrowserPublicConfig publicConfigSqlBrowser)
       bei Microsoft.SqlServer.Configuration.SqlBrowser.SqlBrowserPrivateConfig.ExecConfigNonRC(SqlBrowserPublicConfig publicConfigSqlBrowser)
       bei Microsoft.SqlServer.Configuration.SqlBrowser.SqlBrowserPrivateConfig.SelectAndExecTiming(ConfigActionTiming timing, Dictionary`2 actionData, PublicConfigurationBase spcbPublicConfig)
       bei Microsoft.SqlServer.Configuration.SqlBrowser.SqlBrowserPrivateConfigBase.ExecWithRetry(ConfigActionTiming timing, Dictionary`2 actionData, PublicConfigurationBase spcbPublicConfig).
    2009-11-17 21:05:45 SQLBrowser: The last attempted operation: Der '(A;CI;KR;;;[SQLServer2005SQLBrowserUser$UTAS-URMEL])'-Zugriffssteuerungseintrag wird dem Registrierungsschlüssel 'SOFTWARE\Microsoft\Microsoft SQL Server' in der 'Wow6432'-Sicht hinzugefügt, um den SQL Server Browser-Dienst zu konfigurieren..
    2009-11-17 21:05:45 Slp: Fehler bei der Konfigurationsaktion für Feature SQL_Browser_Redist während der Zeitangabe ConfigNonRC und Szenario ConfigNonRC.
    2009-11-17 21:05:45 Slp: Es wurde versucht, einen nicht autorisierten Vorgang auszuführen.
    2009-11-17 21:05:45 Slp: Fehler bei der Konfigurationsaktion für Feature SQL_Browser_Redist während der Zeitangabe ConfigNonRC und Szenario ConfigNonRC.
    2009-11-17 21:05:45 Slp: Microsoft.SqlServer.Configuration.Sco.ScoException: Es wurde versucht, einen nicht autorisierten Vorgang auszuführen. ---> System.UnauthorizedAccessException: Es wurde versucht, einen nicht autorisierten Vorgang auszuführen.
    2009-11-17 21:05:45 Slp:    bei System.Security.AccessControl.Win32.GetSecurityInfo(ResourceType resourceType, String name, SafeHandle handle, AccessControlSections accessControlSections, RawSecurityDescriptor& resultSd)
    2009-11-17 21:05:45 Slp:    bei System.Security.AccessControl.NativeObjectSecurity.CreateInternal(ResourceType resourceType, Boolean isContainer, String name, SafeHandle handle, AccessControlSections includeSections, Boolean createByName, ExceptionFromErrorCode exceptionFromErrorCode, Object exceptionContext)
    2009-11-17 21:05:45 Slp:    bei Microsoft.SqlServer.Configuration.Sco.SqlRegistrySecurity..ctor(ResourceType resourceType, SafeRegistryHandle handle, AccessControlSections includeSections)
    2009-11-17 21:05:45 Slp:    bei Microsoft.SqlServer.Configuration.Sco.SqlRegistrySecurity.Create(InternalRegistryKey key)
    2009-11-17 21:05:45 Slp:    bei Microsoft.SqlServer.Configuration.Sco.InternalRegistryKey.SetSecurityDescriptor(String sddl, Boolean overwrite)
    2009-11-17 21:05:45 Slp:    --- Ende der internen Ausnahmestapelüberwachung ---
    2009-11-17 21:05:45 Slp:    bei Microsoft.SqlServer.Configuration.Sco.InternalRegistryKey.SetSecurityDescriptor(String sddl, Boolean overwrite)
    2009-11-17 21:05:45 Slp:    bei Microsoft.SqlServer.Configuration.Sco.SqlRegistryKey.SetSecurityDescriptor(String sddl, Boolean overwrite)
    2009-11-17 21:05:45 Slp:    bei Microsoft.SqlServer.Configuration.SqlBrowser.SqlBrowserPrivateConfigBase.SetSecurityDescriptorByLocation(String sRegLocation, RegistryView regView, String sSddl, Boolean bOptional)
    2009-11-17 21:05:45 Slp:    bei Microsoft.SqlServer.Configuration.SqlBrowser.SqlBrowserPrivateConfigBase.ApplyRegPermissions(XmlNodeList xmlNodeListRegPermissions, Dictionary`2 dictionaryGroups, Dictionary`2 dicLocationFragments)
    2009-11-17 21:05:45 Slp:    bei Microsoft.SqlServer.Configuration.SqlBrowser.SqlBrowserPrivateConfig.ApplyRegCommonPermissions(XmlElement xmlRootPermissions, Dictionary`2 dictionaryGroups, Dictionary`2 dicLocationFragments)
    2009-11-17 21:05:45 Slp:    bei Microsoft.SqlServer.Configuration.SqlBrowser.SqlBrowserPrivateConfig.ApplyPermissions(String sXmlPermissionsFile, String sBrowserPrincipal)
    2009-11-17 21:05:45 Slp:    bei Microsoft.SqlServer.Configuration.SqlBrowser.SqlBrowserPrivateConfig.ConfigStaticProperties(SqlBrowserPublicConfig publicConfigSqlBrowser)
    2009-11-17 21:05:45 Slp:    bei Microsoft.SqlServer.Configuration.SqlBrowser.SqlBrowserPrivateConfig.ExecConfigNonRC(SqlBrowserPublicConfig publicConfigSqlBrowser)
    2009-11-17 21:05:45 Slp:    bei Microsoft.SqlServer.Configuration.SqlBrowser.SqlBrowserPrivateConfig.SelectAndExecTiming(ConfigActionTiming timing, Dictionary`2 actionData, PublicConfigurationBase spcbPublicConfig)
    2009-11-17 21:05:45 Slp:    bei Microsoft.SqlServer.Configuration.SqlBrowser.SqlBrowserPrivateConfigBase.ExecWithRetry(ConfigActionTiming timing, Dictionary`2 actionData, PublicConfigurationBase spcbPublicConfig)
    2009-11-17 21:05:45 Slp:    bei Microsoft.SqlServer.Configuration.SqlBrowser.SqlBrowserPrivateConfig.Install(ConfigActionTiming timing, Dictionary`2 actionData, PublicConfigurationBase spcbPublicConfig)
    2009-11-17 21:05:45 Slp:    bei Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.ExecuteAction(String actionId)
    2009-11-17 21:05:45 Slp:    bei Microsoft.SqlServer.Configuration.SqlConfigBase.SlpConfigAction.Execute(String actionId, TextWriter errorStream)
    2009-11-17 21:05:45 Slp: Ausnahme: Microsoft.SqlServer.Configuration.Sco.ScoException.
    2009-11-17 21:05:45 Slp: Quelle: Microsoft.SqlServer.Configuration.Sco.
    2009-11-17 21:05:45 Slp: Meldung: Es wurde versucht, einen nicht autorisierten Vorgang auszuführen..
    2009-11-17 21:05:45 Slp: Innere Ausnahme:
    2009-11-17 21:05:45 Slp:  Ausnahme: System.UnauthorizedAccessException.
    2009-11-17 21:05:45 Slp:  Quelle: mscorlib.
    2009-11-17 21:05:45 Slp:  Meldung: Es wurde versucht, einen nicht autorisierten Vorgang auszuführen..
    2009-11-17 21:05:45 Slp: Completed Action: SqlBro
    2009-11-17 21:05:50 Slp: Prompting user if they want to retry this action due to the following failure:
    2009-11-17 21:05:50 Slp: ----------------------------------------
    2009-11-17 21:05:50 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
    2009-11-17 21:05:50 Slp: Inner exceptions are being indented
    2009-11-17 21:05:50 Slp:
    2009-11-17 21:05:50 Slp: Exception type: Microsoft.SqlServer.Configuration.Sco.ScoException
    2009-11-17 21:05:50 Slp:     Message:
    2009-11-17 21:05:50 Slp:         Es wurde versucht, einen nicht autorisierten Vorgang auszuführen.
    2009-11-17 21:05:50 Slp:     Data:
    2009-11-17 21:05:50 Slp:       WatsonData = 100
    2009-11-17 21:05:50 Slp:       DisableRetry = true
    2009-11-17 21:05:50 Slp:     Inner exception type: System.UnauthorizedAccessException
    2009-11-17 21:05:50 Slp:         Message:
    2009-11-17 21:05:50 Slp:                 Es wurde versucht, einen nicht autorisierten Vorgang auszuführen.
    2009-11-17 21:05:50 Slp:         Stack:
    2009-11-17 21:05:50 Slp:                 bei System.Security.AccessControl.Win32.GetSecurityInfo(ResourceType resourceType, String name, SafeHandle handle, AccessControlSections accessControlSections, RawSecurityDescriptor& resultSd)
    2009-11-17 21:05:50 Slp:                 bei System.Security.AccessControl.NativeObjectSecurity.CreateInternal(ResourceType resourceType, Boolean isContainer, String name, SafeHandle handle, AccessControlSections includeSections, Boolean createByName, ExceptionFromErrorCode exceptionFromErrorCode, Object exceptionContext)
    2009-11-17 21:05:50 Slp:                 bei Microsoft.SqlServer.Configuration.Sco.SqlRegistrySecurity..ctor(ResourceType resourceType, SafeRegistryHandle handle, AccessControlSections includeSections)
    2009-11-17 21:05:50 Slp:                 bei Microsoft.SqlServer.Configuration.Sco.SqlRegistrySecurity.Create(InternalRegistryKey key)
    2009-11-17 21:05:50 Slp:                 bei Microsoft.SqlServer.Configuration.Sco.InternalRegistryKey.SetSecurityDescriptor(String sddl, Boolean overwrite)
    2009-11-17 21:05:50 Slp: ----------------------------------------
    2009-11-17 21:05:57 Slp: User has chosen to cancel this action
    2009-11-17 21:05:58 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20091117_204850\Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_
    2009-11-17 21:05:59 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20091117_204850\Registry_SOFTWARE_Microsoft_Windows_CurrentVersion_Uninstall.reg_
    2009-11-17 21:05:59 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\MSSQLServer to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20091117_204850\Registry_SOFTWARE_Microsoft_MSSQLServer.reg_
    2009-11-17 21:05:59 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Wow6432Node\Microsoft\Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20091117_204850\Registry_SOFTWARE_Wow6432Node_Microsoft_Microsoft SQL Server.reg_
    2009-11-17 21:05:59 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20091117_204850\Registry_SOFTWARE_Wow6432Node_Microsoft_Windows_CurrentVersion_Uninstall.reg_
    2009-11-17 21:05:59 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Wow6432Node\Microsoft\MSSQLServer to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20091117_204850\Registry_SOFTWARE_Wow6432Node_Microsoft_MSSQLServer.reg_
    2009-11-17 21:06:17 Slp: Es wurde versucht, einen nicht autorisierten Vorgang auszuführen.
    2009-11-17 21:06:17 Slp: Watson bucket for exception based failure has been created
    2009-11-17 21:06:17 SSIS: Failed to set registry permission on key 'SOFTWARE\Microsoft\Microsoft SQL Server\100' to SID 'S-1-5-21-2556463381-1186548668-390171815-1029'. Error: 'Es wurde versucht, einen nicht autorisierten Vorgang auszuführen.'
    2009-11-17 21:06:17 Slp: ReplaceAccountWithSidInSddl -- SDDL to be returned:  D:(A;OICI;KR;;;S-1-5-21-2556463381-1186548668-390171815-1029)
    2009-11-17 21:06:17 Slp: Prompting user if they want to retry this action due to the following failure:
    2009-11-17 21:06:17 Slp: ----------------------------------------
    2009-11-17 21:06:17 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
    2009-11-17 21:06:17 Slp: Inner exceptions are being indented
    2009-11-17 21:06:17 Slp:
    2009-11-17 21:06:17 Slp: Exception type: Microsoft.SqlServer.Configuration.Sco.ScoException
    2009-11-17 21:06:17 Slp:     Message:
    2009-11-17 21:06:17 Slp:         Es wurde versucht, einen nicht autorisierten Vorgang auszuführen.
    2009-11-17 21:06:17 Slp:     Data:
    2009-11-17 21:06:17 Slp:       WatsonData = SSIS
    2009-11-17 21:06:17 Slp:       DisableRetry = true
    2009-11-17 21:06:17 Slp:     Inner exception type: System.UnauthorizedAccessException
    2009-11-17 21:06:17 Slp:         Message:
    2009-11-17 21:06:17 Slp:                 Es wurde versucht, einen nicht autorisierten Vorgang auszuführen.
    2009-11-17 21:06:17 Slp:         Stack:
    2009-11-17 21:06:17 Slp:                 bei System.Security.AccessControl.Win32.GetSecurityInfo(ResourceType resourceType, String name, SafeHandle handle, AccessControlSections accessControlSections, RawSecurityDescriptor& resultSd)
    2009-11-17 21:06:17 Slp:                 bei System.Security.AccessControl.NativeObjectSecurity.CreateInternal(ResourceType resourceType, Boolean isContainer, String name, SafeHandle handle, AccessControlSections includeSections, Boolean createByName, ExceptionFromErrorCode exceptionFromErrorCode, Object exceptionContext)
    2009-11-17 21:06:17 Slp:                 bei Microsoft.SqlServer.Configuration.Sco.SqlRegistrySecurity..ctor(ResourceType resourceType, SafeRegistryHandle handle, AccessControlSections includeSections)
    2009-11-17 21:06:17 Slp:                 bei Microsoft.SqlServer.Configuration.Sco.SqlRegistrySecurity.Create(InternalRegistryKey key)
    2009-11-17 21:06:17 Slp:                 bei Microsoft.SqlServer.Configuration.Sco.InternalRegistryKey.SetSecurityDescriptor(String sddl, Boolean overwrite)
    2009-11-17 21:06:17 Slp: ----------------------------------------
    2009-11-17 21:06:24 Slp: User has chosen to cancel this action
    2009-11-17 21:06:26 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20091117_204850\Registry_SOFTWARE_Microsoft_Microsoft SQL Server.reg_
    2009-11-17 21:06:26 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20091117_204850\Registry_SOFTWARE_Microsoft_Windows_CurrentVersion_Uninstall.reg_
    2009-11-17 21:06:26 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Microsoft\MSSQLServer to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20091117_204850\Registry_SOFTWARE_Microsoft_MSSQLServer.reg_
    2009-11-17 21:06:26 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Wow6432Node\Microsoft\Microsoft SQL Server to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20091117_204850\Registry_SOFTWARE_Wow6432Node_Microsoft_Microsoft SQL Server.reg_
    2009-11-17 21:06:26 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20091117_204850\Registry_SOFTWARE_Wow6432Node_Microsoft_Windows_CurrentVersion_Uninstall.reg_
    2009-11-17 21:06:26 Slp: Sco: Attempting to write hklm registry key SOFTWARE\Wow6432Node\Microsoft\MSSQLServer to file C:\Program Files\Microsoft SQL Server\100\Setup Bootstrap\Log\20091117_204850\Registry_SOFTWARE_Wow6432Node_Microsoft_MSSQLServer.reg_
    2009-11-17 21:06:47 Slp: Es wurde versucht, einen nicht autorisierten Vorgang auszuführen.
    2009-11-17 21:06:47 Slp: Watson bucket for exception based failure has been created
    2009-11-17 21:06:47 SSIS: Failed to set registry permission on key 'SOFTWARE\Microsoft\Microsoft SQL Server\100\SSIS' to SID 'S-1-5-21-2556463381-1186548668-390171815-1029'. Error: 'Es wurde versucht, einen nicht autorisierten Vorgang auszuführen.'
    2009-11-17 21:06:47 Slp: Sco: Attempting to open registry subkey SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib
    2009-11-17 21:06:47 Slp: ReplaceAccountWithSidInSddl -- SDDL to be returned:  D:(A;OICI;KR;;;S-1-5-21-2556463381-1186548668-390171815-1029)(A;CI;KR;;;LU)(A;CI;KR;;;MU)
    2009-11-17 21:06:47 Slp: Prompting user if they want to retry this action due to the following failure:
    2009-11-17 21:06:47 Slp: ----------------------------------------
    2009-11-17 21:06:47 Slp: The following is an exception stack listing the exceptions in outermost to innermost order
    2009-11-17 21:06:47 Slp: Inner exceptions are being indented
    2009-11-17 21:06:47 Slp:
    2009-11-17 21:06:47 Slp: Exception type: Microsoft.SqlServer.Configuration.Sco.ScoException
    2009-11-17 21:06:47 Slp:     Message:
    2009-11-17 21:06:47 Slp:         Es wurde versucht, einen nicht autorisierten Vorgang auszuführen.
    2009-11-17 21:06:47 Slp:     Data:
    2009-11-17 21:06:47 Slp:       WatsonData = Perflib
    2009-11-17 21:06:47 Slp:       DisableRetry = true
    2009-11-17 21:06:47 Slp:     Inner exception type: System.UnauthorizedAccessException
    2009-11-17 21:06:47 Slp:         Message:
    2009-11-17 21:06:47 Slp:                 Es wurde versucht, einen nicht autorisierten Vorgang auszuführen.
    2009-11-17 21:06:47 Slp:         Stack:
    2009-11-17 21:06:47 Slp:                 bei System.Security.AccessControl.Win32.GetSecurityInfo(ResourceType resourceType, String name, SafeHandle handle, AccessControlSections accessControlSections, RawSecurityDescriptor& resultSd)
    2009-11-17 21:06:47 Slp:                 bei System.Security.AccessControl.NativeObjectSecurity.CreateInternal(ResourceType resourceType, Boolean isContainer, String name, SafeHandle handle, AccessControlSections includeSections, Boolean createByName, ExceptionFromErrorCode exceptionFromErrorCode, Object exceptionContext)
    2009-11-17 21:06:47 Slp:                 bei Microsoft.SqlServer.Configuration.Sco.SqlRegistrySecurity..ctor(ResourceType resourceType, SafeRegistryHandle handle, AccessControlSections includeSections)
    2009-11-17 21:06:47 Slp:                 bei Microsoft.SqlServer.Configuration.Sco.SqlRegistrySecurity.Create(InternalRegistryKey key)
    2009-11-17 21:06:47 Slp:                 bei Microsoft.SqlServer.Configuration.Sco.InternalRegistryKey.SetSecurityDescriptor(String sddl, Boolean overwrite)
    2009-11-17 21:06:47 Slp: ----------------------------------------
    2009-11-17 21:06:52 Slp: User has chosen to cancel this action

  • List of sql services required for deployment server?

    What are the role of list of sql services in case of BizTalk, like notification service is required for BAM.
    Along with can any one let me know the minimum services of SQL required on production.
    1.Database Engine Services
     SQL Server Replication
      Full-Text Search
    2.Analysis Services
    3.Reporting Services
    4.Shared Features
     Business Intelligence Development Studio
     Client Tools Connectivity
     Integration Services
     Management Tools – Basic
    Is it mandatory to install  analysis, integration services on production server.
    Please suggest!
    Fred

    Sorry, that is not correct.  SQL components beyond Database Services are required in most circumstances.
    It's important you understand what to install based on your application requirements.
    The definitive guides can be found here:
    BizTalk Server 2009:
    http://www.microsoft.com/en-us/download/details.aspx?id=4066
    BizTalk Server 2010:
    http://msdn.microsoft.com/en-us/library/aa561167.aspx
    BizTalk Server 2013:
    http://msdn.microsoft.com/en-us/library/jj248688(v=bts.80).aspx
    As a matter of practice, I always install all BizTalk realted SQL Server features, even if they are not used.  This is for consistency across environments, reliable patching and to accomodate any future BizTalk app features.

  • BizTalk 2009 WCF-SAP Adapter Could not load file or assembly 'Microsoft.Adapters.SAP.SAPGInvoker...' one of its dependencies error

    Hello,
    I have a BizTalk Server 2009 running on Windows Server 2003 x64. I am installing WCF-SAP adapter and have done the following for the same. However, I am getting an error as mentioned below when I click on the Configure button of WCF-SAP adapter in send
    port. I would appreciate if anyone could let me know how to fix this error and make the WCF-SAP adapter working.
    TITLE: BizTalk Server 2009 Administration Console
    Exception has been thrown by the target of an invocation. (mscorlib)
    ADDITIONAL INFORMATION:
    Exception has been thrown by the target of an invocation. (mscorlib)
    Could not load file or assembly 'Microsoft.Adapters.SAP.SAPGInvoker, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. This application has failed to start because the application configuration is incorrect. Reinstalling
    the application may fix this problem. (Exception from HRESULT: 0x800736B1) (Microsoft.Adapters.SAP)
    This application has failed to start because the application configuration is incorrect. Reinstalling the application may fix this problem. (Exception from HRESULT: 0x800736B1)
    I have copied the following 32 bit & 64 bit unicode DLLs in SysWOW64 and System32 folders respectively.
    icudt30.dll
    icuin30.dll
    icuuc30.dll
    librfc32u.dll
    libsapu16vc71.dll
    libsapucum.dll
    Following r3dllinst DLLs are there in System32 folder.
    mfc42.dll
    mfc42u.dll
    mfc71.dll
    mfc71u.dll
    msvcp60.dll
    msvcp71.dll
    msvcp80.dll
    msvcr71.dll
    msvcr80.dll
    Following r3dllinst DLLs are there in SysWOW64 folder.
    mfc40.dll
    mfc40u.dll
    mfc42.dll
    mfc42u.dll
    mfc71.dll
    mfc71u.dll
    mfc80.dll
    mfc80u.dll
    msvcp50.dll
    msvcp60.dll
    msvcp71.dll
    msvcp80.dll
    msvcr71.dll
    msvcr80.dll
    I have the following softwares installed on the server.
    Microsoft Visual C++ 2008 Redistributable x64
    Microsoft Visual C++ 2008 Redistributable x86
    WCF LOB Adapter SDK (64-bit)
    BizTalk Adapter Pack 2.0 (64-bit)
    BizTalk Adapter Pack 2.0 (32-bit)
    The following bindings are also present in the machine.config under Framework\v2.0.50727\CONFIG and Framework64\v2.0.50727\CONFIG
    <system.serviceModel>
    <extensions>
    <bindingElementExtensions>
    <add name="sapAdapter" type="Microsoft.Adapters.SAP.SAPAdapterExtensionElement, Microsoft.Adapters.SAP, Version=3.5.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" />
    </bindingElementExtensions>
    </extensions>
    <client>
    <endpoint binding="sapBinding" contract="IMetadataExchange" name="sap" />
    </client>
    </system.serviceModel>
    Thanks,
    Tarun

    Have you tried this?
    http://geekswithblogs.net/MoonWalker/archive/2013/07/17/could-not-load-file-or-assembly-microsoft.adapters.sap.sapginvoker.dll.aspx
    Morten la Cour

  • Report Server sudden crash

    My report server no1 was runing perfectly okay until recently, don't know what happened, it has the following error message
    REP-51002: Bind to Reports Server rep_webkiss_frhome1 failed
    I try to use the rwdiag -findall function and it could not find anyserver.
    Help!

    i got the following from the rwserver.log file which is keep under the reports\logs\ folder
    may be you can help.....
    *** 2009/5/27 7:14:4:734 -- Reading server config file C:\oracle\FRHome_1\reports\conf\rep_webkiss_frhome1.conf
    *** 2009/5/27 7:14:4:734 -- <server version="10.1.2.0.2">
    <!--Please do not change the id for reports engine.-->
    <!--The class specifies below is subclass of _EngineClassImplBase and implements EngineInterface.-->
    <cache class="oracle.reports.cache.RWCache">
    <property name="cacheSize" value="50"/>
    <!--property name="cacheDir" value="your cache directory"-->
    <!--property name="maxCacheFileNumber" value="max number of cache files"-->
    <!--property name="ignoreParameters" value="parameter names to be ignored in constructing cache key, separated by comma ','"-->
    </cache>
    <engine id="rwEng" class="oracle.reports.engine.EngineImpl" initEngine="1" maxEngine="1" minEngine="0" engLife="50" maxIdle="30" callbackTimeOut="90000">
    <!--property name="sourceDir" value="your reports source directory"/-->
    <!--property name="tempDir" value="your reports temp directory"/-->
    <!--property name="keepConnection" value="yes"/-->
    </engine>
    <engine id="rwURLEng" class="oracle.reports.urlengine.URLEngineImpl" initEngine="1" maxEngine="1" minEngine="0" engLife="50" maxIdle="30" callbackTimeOut="90000"/>
    <!--security id="rwSec" class="oracle.reports.server.RWSecurity">
    <property name="securityUserid" value="%PORTAL_DB_USERNAME%/%PORTAL_DB_PASSWORD%@%PORTAL_DB_TNSNAME%" confidential="yes" encrypted="no"/>
    <property name="oidEntity" value="%REPORTS_OID_ENTITY%"/>
    </security-->
    <!--destination destype="oraclePortal" class="oracle.reports.server.DesOraclePortal">
    <property name="portalUserid" value="%PORTAL_DB_USERNAME%/%PORTAL_DB_PASSWORD%@%PORTAL_DB_TNSNAME%" confidential="yes" encrypted="no"/>
    </destination-->
    <destination destype="ftp" class="oracle.reports.plugin.destination.ftp.DesFTP">
    <!--property name="proxy" value="proxyinfo.xml"/-->
    </destination>
    <destination destype="WebDav" class="oracle.reports.plugin.destination.webdav.DesWebDAV">
    <!--property name="proxy" value="proxyinfo.xml"/-->
    </destination>
    <!-- By default server will use rwnetwork.conf as network config file
    Use this element to override the same -->
    <!--networkConfig file="rwnetwork.conf"></networkConfig-->
    <job jobType="report" engineId="rwEng"/>
    <job jobType="rwurl" engineId="rwURLEng"/>
    <notification id="mailNotify" class="oracle.reports.server.MailNotify">
    <property name="succnotefile" value="succnote.txt"/>
    <property name="failnotefile" value="failnote.txt"/>
    </notification>
    <!--notification id="wfNotify" class="oracle.reports.server.WorkflowNotify">
    <property name="connStr" value="%WF_DB_USERNAME%/%WF_DB_PASSWORD%@%WF_DB_TNSNAME%" confidential="yes" encrypted="no"/>
    </notification-->
    <log option="noJob"/>
    <!--jobStatusRepository class="oracle.reports.server.JobRepositoryDB">
    <property name="repositoryConn" value="repo_db_username/repo_db_password@repo_db_tnsname" confidential="yes" encrypted="no"/>
    </jobStatusRepository-->
    <!--trace traceOpts="trace_all"/-->
    <connection maxConnect="200" idleTimeOut="15">
    <orbClient id="RWClient" publicKeyFile="clientpub.key"/>
    </connection>
    <queue maxQueueSize="1000"/>
    <!--jobRecovery auxDatFiles="yes"/-->
    <!--
    The value of the 'identifier' element is encrypted and is of the form SERVERACCESSKEY_USER/SERVERACCESSKEY_PASSWORD
    SERVERACCESSKEY_USER and SERVERACCESSKEY_PASSWORD in <server>.conf and targets.xml
    file should match for Reports EM pages to display data correctly.
    Corresponding entries of username and password in targets.xml:
    <Property NAME="Password" VALUE="SERVERACCESSKEY_PASSWORD" ENCRYPTED="FALSE"/>
    <Property NAME="UserName" VALUE="SERVERACCESSKEY_USER" ENCRYPTED="FALSE"/>
    -->
    <pluginParam name="mailServer">webkiss.olympia.my</pluginParam>
    <!--pluginParam name="proxy" type="file">proxyinfo.xml</pluginParam-->
    <pluginParam name="xmlpds" type="file">xmlpds.conf</pluginParam>
    <pluginParam name="jdbcpds" type="file">jdbcpds.conf</pluginParam>
    <pluginParam name="textpds" type="file">textpds.conf</pluginParam>
    </server>
    *** 2009/5/27 7:14:4:734 -- Reports Server is starting up
    *** 2009/5/27 7:14:8:609 -- Reports Server started up engine rwURLEng-0
    *** 2009/5/27 7:14:12:359 -- Reports Server started up engine rwEng-0
    *** 2009/5/27 7:44:9:375 -- Shutting down engine rwURLEng-0
    *** 2009/5/27 7:44:9:375 -- Reports Server shut down engine rwURLEng-0
    *** 2009/5/27 7:44:12:375 -- Shutting down engine rwEng-0
    *** 2009/5/27 7:44:12:375 -- Reports Server shut down engine rwEng-0

Maybe you are looking for

  • GL Open Item does not appear in F-03

    Hi Friends, I am trying to clear the GL open items thru F-03, while I see all the open items that appear in Line item display through FBL3N (total 25), out of them only 24 appear in F-03, I can not see the 25th item. I have checked the document in BS

  • Installing OWB on SLES 10

    Hi! Do somebody knows if Oracle OWB 10.0.2 install and run on Suse Linux Enterprise 10? It's seems it's certified only for SLES 9 but I need to install it on SLES10. Thanks in advance!

  • Forcing new tabs to open to immediate right of current tab

    Hi all, Is there a way to have new tabs open to the immediate right of the current tab you're in, as opposed to the default which is to the right of the last open tab? I know this is automatic when clicking on a link in the current tab, but would be

  • DHCP Failover feature in Windows 2012

    I am planning to configure DHCP on windows 2012 failover (Load balanced)mode.Just want to confirm two things: 1.How will the DCHP address be assigned to clients incase the DHCP Servers loose communication between them. 2.Regarding IP helpers that i n

  • Printer does not recognize ink cartridges

    Purchased a 2188 in China and brought back to Mexico.  Ink cartridges in China were 816 &817 models but in Mexico the equivalent cartridge for the 2180 series is 21 & 22.  They are same size, shape and fit perfectly. However, as soon as the Mexican c