IHE Integration Profiles

New Post: How we solved few issues we had while deploying the reference implementation

giusarac — Tue, 23 Dec 2008 14:39:25 GMT

Hello,
we buillt version 18637 and here are few hints on how we got around some bumps that we found on the road.
I hope that you might benefit from it ( and save time! ). Giuseppe

Q: My reference solution compiles and installs but I cannot browse to the services.

A: In the directory….. \Version1\WindowsServices\XDSRegistryServiceHost edit App.config

Browse for the following content and make sure that the part in red is commented out.

If not insert  before and after the block .

<behaviors>
            <serviceBehaviors>
                <behavior name="XDSRegistry_ServiceBehavior" >

                    <serviceDebug includeExceptionDetailInFaults="false" />

                    

                    
                    <serviceMetadata httpGetEnabled="true" httpsGetEnabled="true" />
                    

                   <!--

<serviceCertificate findValue="824aced4b7600d8547eceec02c3c86ea6d23cb2f"

storeLocation="LocalMachine"

storeName="Root"

x509FindType="FindByThumbprint" />

</serviceCredentials>

          -->
                </behavior>

            </serviceBehaviors>

        </behaviors>

Also make sure that IIS is stopped when using the services.

You can achieve that with typing the following command in the command line :

iisreset /stop

Database connection

If using SQLexpress the connection string for the database is similar to this : MYMACHINE\SQLEXPRESS

If you are using SQL server is : MYMACHINE.
If you are not sure open the

make sure the app.config files have the correct connection setting.

Use the Microsoft SQL – Surface Area Configuration and make sure that you allow for remote connections

Q: When I use the TestHarness the Query to the registry fails.

A: Make sure the the Registry server and the clients configurations are matching.

The services offered by the Registry can be used by the Repository or Document Consumer.

In the App.config for the Registry make sure that the bindings look like the following : ( note the messge encoding “text” ).

<binding name="XDSRegistry_HTTP" closeTimeout="00:10:00"

openTimeout="00:10:00" receiveTimeout="00:10:00" sendTimeout="00:10:00"

bypassProxyOnLocal="false" hostNameComparisonMode="StrongWildcard"

maxBufferPoolSize="524288" maxReceivedMessageSize="65536"

messageEncoding="Text" textEncoding="utf-8" useDefaultWebProxy="true"

allowCookies="false">

in the repository App.config AND test harness App.config the matching endpoint as a client should look like the following :

<binding name="XDSRegistry_HTTP_Endpoint" closeTimeout="00:01:00"

openTimeout="00:01:00" receiveTimeout="00:10:00" sendTimeout="00:01:00"

bypassProxyOnLocal="false" transactionFlow="false" hostNameComparisonMode="StrongWildcard"

maxBufferPoolSize="524288" maxReceivedMessageSize="65536" messageEncoding="Text"

textEncoding="utf-8" useDefaultWebProxy="true" allowCookies="false">

<readerQuotas maxDepth="32" maxStringContentLength="8192" maxArrayLength="16384"

maxBytesPerRead="4096" maxNameTableCharCount="16384" />

<reliableSession ordered="true" inactivityTimeout="00:10:00"

enabled="false" />

One last hint. When you deployed my solution I had to copy everything in a subdir closer to the root to shorten the filepath length.
The install script was failing because of it . My path looks like c:\IHE-18637\Version1\..and it works fine now.

Hope this helps.

New Post: 'Error 1068 The Dependency Service or Group Failed To Start' appear when i try to start XDS services

guti — Fri, 19 Dec 2008 08:53:20 GMT

Why does 'Error 1068 The Dependency Service or Group Failed To Start' appear when i try to start XDS services?????

Thx

New Post: Updated build instructions?

sinergy — Wed, 17 Dec 2008 20:01:05 GMT

Hello, I'm wondering if the build instructions are going to be updated? I'm really having a hard time setting this up with the current instructions.

I've been able to do a successful build from source, and installation of the services, but http://localhost:8080/XdsService/XDSRepository does NOT want to work. Does IIS have to be installed? Is winxp sufficient? SQL Server express ok? These are questions that should be put into a FAQ :)

Any help would be appreciated.

Thank you.

New Post: Cannot connect to Document Registry/Repository service

lisvi — Wed, 17 Dec 2008 09:52:00 GMT

Hi,

I found the reason why it was not possible to perform the "smoke test" after some debugging sessions. The whole secure configuration was the reason for this behaviour. I just comment in all App.config files the https configuration.
After this action, a smoke test could be done.

Viktor

Updated Release: Connect-a-thon Release (Jun 13, 2008)

tbachour — Wed, 10 Dec 2008 15:31:43 GMT

Connect-a-thon passed - Release build version 1 for IHE XDS.b Document Registry and Document Repository actors.

Download the code from http://www.codeplex.com/ihe/SourceControl/DownloadSourceCode.aspx?changeSetId=18637 and follow the instructions in the XDS.b Build and Deployment Guide in the Documentation folder.

This release build implements the following transactions:

* Provide and Register Document Set-b ITI-41
* Register Document Set-b ITI-42
* Registry Stored Query ITI-18
* Retrieve Document Set ITI-43
* ATNA
* Patient Identity Feed ITI-44/ITI-8

The build also includes a test harness and sample instances to verify the correct functionality of the services before proceeding with testing.

Released: Connect-a-thon Release (Jun 13, 2008)

Wed, 10 Dec 2008 15:31:43 GMT

Updated Release: Connect-a-thon Release (Feb 06, 2008)

tbachour — Wed, 10 Dec 2008 15:30:21 GMT

Updated Release: Connect-a-thon Release (Feb 06, 2008)

tbachour — Wed, 10 Dec 2008 15:28:24 GMT

Connect-a-thon passed - Release build version 1 for IHE XDS.b Document Registry and Document Repository actors.

Download the code from http://www.codeplex.com/ihe/SourceControl/DownloadSourceCode.aspx?changeSetId=15690 and follow the instructions in the XDS.b Build and Deployment Guide in the Documentation folder.

This release build implements the following transactions:

* Provide and Register Document Set-b ITI-41
* Register Document Set-b ITI-42
* Registry Stored Query ITI-18
* Retrieve Document Set ITI-43
* ATNA
* Patient Identity Feed ITI-44/ITI-8

The build also includes a test harness and sample instances to verify the correct functionality of the services before proceeding with testing.

New Post: Cannot connect to Document Registry/Repository service

lisvi — Mon, 08 Dec 2008 15:35:04 GMT

Hi all,

I installed the latest release with the help of the manual "XDSb Build and Deployment Guide.doc", the services are running in ServiceControl Manager ("Started") but I cannot connect to these services. I am also unable to browse the services. I started the Test harness tool and got the exception listed below. I saw in this discussion board that other people had the same problem but unfortunately without a description how to solve this problem.

------------------------------------------------------------------------Test harness exception----------------------------------------------------------------------------------------
System.ServiceModel.EndpointNotFoundException: Could not connect to http://localhost:19010/XdsService/XDSRepository. TCP error code 10061: No connection could be made because the target machine actively refused it 127.0.0.1:19010. ---> System.Net.WebException: Unable to connect to the remote server ---> System.Net.Sockets.SocketException: No connection could be made because the target machine actively refused it 127.0.0.1:19010

   at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)

   at System.Net.Sockets.Socket.InternalConnect(EndPoint remoteEP)

   at System.Net.ServicePoint.ConnectSocketInternal(Boolean connectFailure, Socket s4, Socket s6, Socket& socket, IPAddress& address, ConnectSocketState state, IAsyncResult asyncResult, Int32 timeout, Exception& exception)

   --- End of inner exception stack trace ---

   at System.Net.HttpWebRequest.GetRequestStream()

   at System.ServiceModel.Channels.HttpOutput.WebRequestHttpOutput.GetOutputStream()

   --- End of inner exception stack trace ---

Server stack trace:

   at System.ServiceModel.Channels.HttpOutput.WebRequestHttpOutput.GetOutputStream()

   at System.ServiceModel.Channels.HttpOutput.Send(TimeSpan timeout)

   at System.ServiceModel.Channels.HttpChannelFactory.HttpRequestChannel.HttpChannelRequest.SendRequest(Message message, TimeSpan timeout)

   at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)

   at System.ServiceModel.Dispatcher.RequestChannelBinder.Request(Message message, TimeSpan timeout)

   at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)

   at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs)

   at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)

   at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)

Exception rethrown at [0]:

   at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)

   at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)

   at Microsoft.XDS.Test.XDSRepository.XDSRepository.RetrieveDocumentSet(Message request)

   at Microsoft.XDS.Test.XDSRepository.XDSRepositoryClient.RetrieveDocumentSet(Message request) in E:\CodePlex\Version1\Testing\XDSTestHarness\Service References\XDSRepository.cs:line 68

   at Microsoft.XDS.Test.frmIheTstHarness.btnRetrieve_Click(Object sender, EventArgs e) in E:\CodePlex\Version1\Testing\XDSTestHarness\frmIheTstHarness.cs:line 360
---------------------------
OK
---------------------------

I will also paste the config files of repository and registry:
========================================================================================================================
Repository - app.config

<?xml version="1.0" encoding="utf-8"?>
<configuration>
    <configSections>
        <section name="dataConfiguration" type="Microsoft.Practices.EnterpriseLibrary.Data.Configuration.DatabaseSettings, Microsoft.Practices.EnterpriseLibrary.Data, Version=3.1.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />
        <section name="storageprovider" type="Microsoft.IHE.XDS.DocumentRepository.StorageProvider.SQLProviderSection,Microsoft.IHE.XDS.DocumentRepository.StorageProvider" />
    </configSections>

    <connectionStrings>
        <add name="XDSRepository" connectionString="Database=XDSRepositoryDB;Server=ris-demo-server;Integrated Security=SSPI"
          providerName="System.Data.SqlClient" />
        <add name="ATNA" connectionString="Database=XDSRepositoryDB;Server=ris-demo-server;Integrated Security=SSPI"
          providerName="System.Data.SqlClient" />
    </connectionStrings>

    <appSettings>
        <add key="HASH_ALGORITHM" value="SHA1" />
        <add key="SYSLOG_SERVER" value="129.6.24.109" />
        <add key="SYSLOG_PORT" value="8087" />

        
        <add key="XDSREPOSITORY_SERVICE_ADDRESS" value="https://localhost:19012/XdsService/XDSRepository" />
        <add key="XDSREGISTRY_SERVICE_ADDRESS" value="https://localhost:19013/XdsService/XDSRegistry"/>
        <add key ="XDSREGISTRY_ENDPOINT_NAME" value="XDSRegistry_HTTPS_Endpoint"/>
        

        
        <add key="XDSREPOSITORY_SERVICE_ADDRESS" value="http://localhost:19010/XdsService/XDSRepository" />
        <add key="XDSREGISTRY_SERVICE_ADDRESS" value="http://localhost:19011/XdsService/XDSRegistry"/>
        <add key ="XDSREGISTRY_ENDPOINT_NAME" value="XDSRegistry_HTTP_Endpoint"/>
        

    </appSettings>

    
    <storageprovider defaultProvider="SQLStorageProvider">
        
        <providers>
            <clear />
            
            <add name="SQLStorageProvider" type="Microsoft.IHE.XDS.DocumentRepository.StorageProvider.SQLServerStorageProvider,Microsoft.IHE.XDS.DocumentRepository.StorageProvider" />
        </providers>
    </storageprovider>
    <system.serviceModel>

        <services>
            <service name="Microsoft.IHE.XDS.DocumentRepository.DocumentRepositoryService" behaviorConfiguration="XDSRepository_ServiceBehavior">

                <host>
                    <baseAddresses>

                        
              <add baseAddress="https://localhost:19012/XdsService/XDSRepository" />
            

                        
                        <add baseAddress="http://localhost:19010/XdsService/XDSRepository" />
                        

                    </baseAddresses>
                </host>

                <endpoint name="XDSRepository_HTTPS_Endpoint"
                            address="https://localhost:19012/XdsService/XDSRepository"
                            contract="Microsoft.IHE.XDS.DocumentRepository.IDocumentRepository"
                            binding="wsHttpBinding"
                            bindingConfiguration="XDSRepository_HTTPS" />

                

                <endpoint name="XDSRepository_HTTP_Endpoint"
                            address="http://localhost:19010/XdsService/XDSRepository"
                            contract="Microsoft.IHE.XDS.DocumentRepository.IDocumentRepository"
                            binding="wsHttpBinding"
                            bindingConfiguration="XDSRepository_HTTP" />

                

                <endpoint name="XDSRepository_Metadata_Endpoint"
                            address="http://localhost/XdsService/XDSRepository"
                            binding="mexHttpBinding"
                            contract="IMetadataExchange" />

            </service>
        </services>

        <bindings>

            <wsHttpBinding>

                <binding name="XDSRepository_HTTPS" closeTimeout="00:10:00" openTimeout="00:10:00" receiveTimeout="00:10:00" sendTimeout="00:10:00" bypassProxyOnLocal="false" transactionFlow="false" hostNameComparisonMode="StrongWildcard" maxBufferPoolSize="524288" maxReceivedMessageSize="65536" messageEncoding="Mtom" textEncoding="utf-8" useDefaultWebProxy="true" allowCookies="false">
                    <readerQuotas maxDepth="32" maxStringContentLength="8192" maxArrayLength="16384" maxBytesPerRead="4096" maxNameTableCharCount="16384" />
                    <reliableSession ordered="true" inactivityTimeout="00:10:00" enabled="false" />
                    <security mode="Transport">
                        <transport clientCredentialType="Certificate" proxyCredentialType="None" />
                        <message clientCredentialType="None" establishSecurityContext="false" negotiateServiceCredential="false"/>
                    </security>
                </binding>

                

                <binding name="XDSRepository_HTTP" closeTimeout="00:10:00" openTimeout="00:10:00" receiveTimeout="00:10:00" sendTimeout="00:10:00" bypassProxyOnLocal="false" transactionFlow="false" hostNameComparisonMode="StrongWildcard" maxBufferPoolSize="524288" maxReceivedMessageSize="65536" messageEncoding="Mtom" textEncoding="utf-8" useDefaultWebProxy="true" allowCookies="false">
                    <readerQuotas maxDepth="32" maxStringContentLength="8192" maxArrayLength="16384" maxBytesPerRead="4096" maxNameTableCharCount="16384" />
                    <reliableSession ordered="true" inactivityTimeout="00:10:00" enabled="false" />
                    <security mode="None">
                        <transport clientCredentialType="None" proxyCredentialType="None" />
                        <message clientCredentialType="None" establishSecurityContext="false" negotiateServiceCredential="false"/>
                    </security>
                </binding>

                

                <binding name="XDSRegistry_HTTPS_Endpoint" closeTimeout="00:01:00"
                    openTimeout="00:01:00" receiveTimeout="00:10:00" sendTimeout="00:01:00"
                    bypassProxyOnLocal="false" transactionFlow="false" hostNameComparisonMode="StrongWildcard"
                    maxBufferPoolSize="524288" maxReceivedMessageSize="65536"
                    messageEncoding="Mtom" textEncoding="utf-8" useDefaultWebProxy="true"
                    allowCookies="false">
                    <readerQuotas maxDepth="32" maxStringContentLength="8192" maxArrayLength="16384"
                        maxBytesPerRead="4096" maxNameTableCharCount="16384" />
                    <reliableSession ordered="true" inactivityTimeout="00:10:00"
                        enabled="false" />
                    <security mode="Transport">
                        <transport clientCredentialType="Certificate" proxyCredentialType="None"
                            realm="" />
                        <message clientCredentialType="Windows" negotiateServiceCredential="true"
                            establishSecurityContext="true" />
                    </security>
                </binding>

                <binding name="XDSRegistry_HTTP_Endpoint" closeTimeout="00:01:00"
                    openTimeout="00:01:00" receiveTimeout="00:10:00" sendTimeout="00:01:00"
                    bypassProxyOnLocal="false" transactionFlow="false" hostNameComparisonMode="StrongWildcard"
                    maxBufferPoolSize="524288" maxReceivedMessageSize="65536"
                    messageEncoding="Mtom" textEncoding="utf-8" useDefaultWebProxy="true"
                    allowCookies="false">
                    <readerQuotas maxDepth="32" maxStringContentLength="8192" maxArrayLength="16384"
                        maxBytesPerRead="4096" maxNameTableCharCount="16384" />
                    <reliableSession ordered="true" inactivityTimeout="00:10:00"
                        enabled="false" />
                    <security mode="None">
                        <transport clientCredentialType="Windows" proxyCredentialType="None"
                            realm="" />
                        <message clientCredentialType="Windows" negotiateServiceCredential="true"
                            establishSecurityContext="true" />
                    </security>
                </binding>

            </wsHttpBinding>

        </bindings>

        <client>

            <endpoint address="https://localhost:19013/XdsService/XDSRegistry"
                 binding="wsHttpBinding" bindingConfiguration="XDSRegistry_HTTPS_Endpoint"
                 contract="Microsoft.IHE.XDS.DocumentRepository.XDSRegistry.XDSRegistry"
                 name="XDSRegistry_HTTPS_Endpoint" behaviorConfiguration="XDSRegistry_HTTPS_EndPointBehaviour" />

            <endpoint address="http://localhost:19011/XdsService/XDSRegistry"
                 binding="wsHttpBinding" bindingConfiguration="XDSRegistry_HTTP_Endpoint"
                 contract="Microsoft.IHE.XDS.DocumentRepository.XDSRegistry.XDSRegistry"
                 name="XDSRegistry_HTTP_Endpoint" />

        </client>

        <behaviors>

            <serviceBehaviors>
                <behavior name="XDSRepository_ServiceBehavior">
                    <serviceDebug includeExceptionDetailInFaults="false" />

                    <serviceMetadata httpGetEnabled="true" httpsGetEnabled="true" />

                    
                    
                    

                    <serviceCredentials>
                        <serviceCertificate findValue="824aced4b7600d8547eceec02c3c86ea6d23cb2f"
                          storeLocation="LocalMachine"
                          storeName="Root"
                          x509FindType="FindByThumbprint" />
                    </serviceCredentials>
                </behavior>
            </serviceBehaviors>

            <endpointBehaviors>
                <behavior name="XDSRegistry_HTTPS_EndPointBehaviour">
                    <clientCredentials>

                        <clientCertificate findValue="824aced4b7600d8547eceec02c3c86ea6d23cb2f"
                            storeLocation="LocalMachine"
                            storeName="My"
                            x509FindType="FindByThumbprint" />

                    </clientCredentials>
                </behavior>
            </endpointBehaviors>

        </behaviors>

    </system.serviceModel>
</configuration>

=====================================================================================================================
and Registry - app.config:

<?xml version="1.0" encoding="utf-8" ?>
<configuration>

    <configSections>
        <section name="dataConfiguration" type="Microsoft.Practices.EnterpriseLibrary.Data.Configuration.DatabaseSettings, Microsoft.Practices.EnterpriseLibrary.Data, Version=3.1.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" />
    </configSections>

    <connectionStrings>
        <add name="XDSRegistry" connectionString="Database=XDSRegistryDB;Server=ris-demo-server;Integrated Security=SSPI"
           providerName="System.Data.SqlClient" />
        <add name="ATNA" connectionString="Database=XDSRegistryDB;Server=ris-demo-server;Integrated Security=SSPI"
           providerName="System.Data.SqlClient" />
    </connectionStrings>

    <appSettings>
        <add key="SYSLOG_SERVER" value="129.6.24.109" />
        <add key="SYSLOG_PORT" value="8087" />
        <add key="XDSREGISTRY_SERVICE_ADDRESS" value="http://localhost:19011/XdsService/XDSRegistry" />
        <add key="PATIENT_ROOT_EXTENSION_SEPARATOR" value="{0}^^^&{1}&ISO"/>
    </appSettings>

    <system.serviceModel>

        <services>
            <service name="Microsoft.IHE.XDS.DocumentRegistry.DocumentRegistryService" behaviorConfiguration="XDSRegistry_ServiceBehavior">

                <host>
                    <baseAddresses>

                        
                        <add baseAddress="https://localhost:19013/XdsService/XDSRegistry"/>
                         

                        
                        <add baseAddress="http://localhost:19011/XdsService/XDSRegistry"/>
                        

                    </baseAddresses>
                </host>

                <endpoint name="XDSRegistry_HTTPS_Endpoint" contract="Microsoft.IHE.XDS.DocumentRegistry.IDocumentRegistry"
                            address="https://localhost:19013/XdsService/XDSRegistry"
                            binding="wsHttpBinding"
                            bindingConfiguration="XDSRegistry_HTTPS" />

                
                <endpoint name="XDSRegistry_HTTP_Endpoint" contract="Microsoft.IHE.XDS.DocumentRegistry.IDocumentRegistry"
                            address="http://localhost:19011/XdsService/XDSRegistry"
                            binding="wsHttpBinding"
                            bindingConfiguration="XDSRegistry_HTTP" />
                

                <endpoint name="XDSRegistry_Metadata_Endpoint"
                            address="http://localhost/XdsService/XDSRegistry"
                            binding="mexHttpBinding"
                            contract="IMetadataExchange" />

            </service>
        </services>

        <bindings>
            <wsHttpBinding>

        <binding name="XDSRegistry_HTTPS" closeTimeout="00:10:00"
                           openTimeout="00:10:00" receiveTimeout="00:10:00" sendTimeout="00:10:00"
                           bypassProxyOnLocal="false" hostNameComparisonMode="StrongWildcard"
                           maxBufferPoolSize="524288" maxReceivedMessageSize="65536"
                           messageEncoding="Text" textEncoding="utf-8" useDefaultWebProxy="true"
                           allowCookies="false">

                    <readerQuotas maxDepth="32" maxStringContentLength="8192" maxArrayLength="16384"
                       maxBytesPerRead="4096" maxNameTableCharCount="16384" />

                    <reliableSession ordered="true" inactivityTimeout="00:10:00"
                       enabled="false" />

                    <security mode="Transport">
                        <transport clientCredentialType="Certificate" proxyCredentialType="None" />
                        <message clientCredentialType="None" establishSecurityContext="false" negotiateServiceCredential="false"/>
                    </security>

                </binding>

                 

                <binding name="XDSRegistry_HTTP" closeTimeout="00:10:00"
                       openTimeout="00:10:00" receiveTimeout="00:10:00" sendTimeout="00:10:00"
                       bypassProxyOnLocal="false" hostNameComparisonMode="StrongWildcard"
                       maxBufferPoolSize="524288" maxReceivedMessageSize="65536"
                       messageEncoding="Text" textEncoding="utf-8" useDefaultWebProxy="true"
                       allowCookies="false">

                    <readerQuotas maxDepth="32" maxStringContentLength="8192" maxArrayLength="16384"
                       maxBytesPerRead="4096" maxNameTableCharCount="16384" />

                    <reliableSession ordered="true" inactivityTimeout="00:10:00"
                       enabled="false" />

                    <security mode="None">
                        <transport clientCredentialType="None" proxyCredentialType="None" />
                        <message clientCredentialType="None" establishSecurityContext="false" negotiateServiceCredential="false"/>
                    </security>

                </binding>

                

            </wsHttpBinding>
        </bindings>

        <behaviors>
            <serviceBehaviors>
                <behavior name="XDSRegistry_ServiceBehavior" >

                    <serviceDebug includeExceptionDetailInFaults="false" />

                    

                    
                    <serviceMetadata httpGetEnabled="true" httpsGetEnabled="true" />
                    

                    <serviceCredentials>
                        <serviceCertificate findValue="824aced4b7600d8547eceec02c3c86ea6d23cb2f"
                          storeLocation="LocalMachine"
                          storeName="Root"
                          x509FindType="FindByThumbprint" />
                    </serviceCredentials>

                </behavior>

            </serviceBehaviors>

        </behaviors>

    </system.serviceModel>

</configuration>

Does anybody have an idea where the problem could be??

Thanks in advance,
Viktor

New Post: Unable to Install Document Registry Service

Niresh — Tue, 25 Nov 2008 15:40:10 GMT

Hi

When i Try to install the document registry service , the folllowing error is logged in the eventvwr and the service installation is rolled back.

The ScRegSetValueExW call failed for ImagePath with the following error:
Access is denied.

Process 'd:\xds sourcecode\ihe-18637\Version1\windowsservices\xdsregistryservicehost\bin\Debug\xdsregistryservicehost.exe' exhibiting suspicious behavior pattern 'HIPS/RegMod-013'.

Access denied.

pls help me out in solving this problem

New Post: ATNA - Can't find 'Record Audit Event' on Node Authentication Failure

henkya — Tue, 11 Nov 2008 02:25:40 GMT

Hi,

I was browsing through the XDS profile implementation and can't seem to find the part where one of the XDS actors (Doc registry/repository) generate an audit message should a node authentication failure occured.

I did notice that you folks are handling the node-authentication by enabling transport security & using client/server certificates in WCF, but shouldn't there be any "Record Audit-Event" transaction when an unauthorized node try to access the service - (i was hoping to find some kind of a CustomX509CertificateValidator implementation)? Am I missing anything?

Thanks,

Henky

New Post: PIX Managers

Oganix — Wed, 15 Oct 2008 17:42:09 GMT

Which Patient Identifier Cross-reference Manager (PIX) are you using with this implementation? Are there any free/open source implementations available?

Created Issue: XDSFolder.lastUpdateDate is missing in query response

Oganix — Tue, 14 Oct 2008 19:47:04 GMT

When querying for a folder, the implementation does not return the XDSFolder.lastUpdateTime element for the folder. I have attached the AdhocQueryResponse message.

New Post: Repository was unable to access the Registry & SOAP error

leoace — Wed, 08 Oct 2008 03:19:58 GMT

Thenaks very much,
Problem solved, I changed the messageEnconding="Text" in client's config.app.
But another problem was occured.
It is life.

Best regards,

Leoace

New Post: How to force WCF to always send data stream using MTOM with XOP encoding even the data stream is smaller than 1024 bytes?

WagnerSilveira — Wed, 01 Oct 2008 21:56:22 GMT

Hi Edwood,

WCF endpoint will always using MTOM+XOP. The difference is that in the cases where the data stream is less than 1024 bytes, this data stream will not become an attachment, but will stay in the original body of the message. But the message will still have the MTOM+XOP header.

Cheers, Wagner.

New Post: Does the implementation support folders?

WagnerSilveira — Wed, 01 Oct 2008 21:53:29 GMT

Thanks for the heads up mate!

You should log this one as an error, so we can add it the fix to the next release.

Cheers, Wagner.

New Post: Repository was unable to access the Registry & SOAP error

WagnerSilveira — Wed, 01 Oct 2008 21:45:21 GMT

Piet answer is correct, apart from one detail:

XDSRegistry should be communicating using SOAP instead of MTOM+XOP, so the configs are:

1) Keep the messageEnconding="Text" in the ReigstryServiceHost app.config
2) On the client applications (in this case the test harness when you're running the register document set and the Repository when you're running the Provide and Register Document Set) the messageEnconding value for the client endpoints pointing to XDSRegistry service should also use "Text".

Probably the easiest way to do this is to change the configurations for the Registry Service and update the web references on both the Repository and the Test Harness. After this everything should be ok.

Cheers, Wagner.

New Post: We would like to hear from you about your XDS.b implementation

tbachour — Wed, 01 Oct 2008 02:14:34 GMT

Hi all,

My name is Teddy Bachour. I am the Technical Strategist on the WW Health Team at Microsoft Corporation. I would like to hear your story about your XDS.b implementation in a production environment using our Reference Implementation at codeplex.com/ihe.

You can reach me at teddy.bachour@microsoft.com.

I look forward to hearing from you.

Regards,
teddy

New Post: AdhocQuery element ids

Oganix — Tue, 30 Sep 2008 19:13:40 GMT

I have found out that IHE transaction 18 defines the ids assigned to XDS Stored Queries. See http://www.ihe.net/Technical_Framework/upload/IHE_ITI_TF_Supplement_XDS_Stored_Query_TI_2007_08_20-2.pdf

New Post: AdhocQuery element ids

Oganix — Mon, 29 Sep 2008 19:56:31 GMT

In the StoredQueryGetDocumentRequest example the id of the AdhocQuery element is referring to the storedQueryUniqueID
column in the StoredQuery table in the XDSRegistryDatabase. Are these id values standard or are they specific to this
implementation?