2011-05-06 1 views
1

동일한 가상 컴퓨터에서 서로 다른 두 가상 디렉터리에 dev 환경과 prod 환경을 설정하고 Configuring Multiple WMS Instances을 사용하여 둘 다 제대로 설정되도록하십시오. 워크 플로 인스턴스가 연결된 클라이언트를 기반으로 적절한 환경에서 유지되는 워크 플로 인스턴스를 볼 수 있으므로 제대로 작동하는 것 같습니다. 이 문제는 IIS 관리자에서 지속 된 인스턴스를 보려고 시도 할 때 발생합니다. 나는 다음과 같은 오류를 얻을 :여러 인스턴스의 Windows Server AppFabric 구성

IIS Error Displayed when trying to look at persisted instances

Error message presented when clicking on "Error(s) encountered" link

내가 가진

관련 설정 파일 (* 내가 직접이 게시물 *에 이미지를 업로드하는 방법을 모른다, appologize) 다음과 같다 :

기본의 Web.config

<microsoft.applicationServer> 
    <monitoring lockElements="bulkCopyProviders, collectors"> 
     <bulkCopyProviders> 
      <bulkCopyProvider providerName="System.Data.SqlClient" type="Microsoft.ApplicationServer.Monitoring.EventCollector.SqlServerBulkCopy, Microsoft.ApplicationServer.Monitoring, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" /> 
     </bulkCopyProviders> 
     <collectors> 
      <collector name="" session="0"> 
       <settings retryCount="5" eventBufferSize="10000" retryWait="00:00:15" samplingInterval="00:00:05" aggregationEnabled="true" /> 
      </collector> 
     </collectors> 
     <default enabled="true" connectionStringName="ProductionApplicationServerMonitoringConnectionString" monitoringLevel="HealthMonitoring" /> 
    </monitoring> 
    <persistence> 
     <instanceStoreProviders lockItem="true"> 
      <add name="SqlPersistenceStoreProvider" storeProvider="Microsoft.ApplicationServer.StoreProvider.Sql.SqlWorkflowInstanceStoreProvider, Microsoft.ApplicationServer.StoreProvider, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" storeControlProvider="Microsoft.ApplicationServer.StoreManagement.Sql.Control.SqlInstanceControlProvider, Microsoft.ApplicationServer.StoreManagement, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" storeQueryProvider="Microsoft.ApplicationServer.StoreManagement.Sql.Query.SqlInstanceQueryProvider, Microsoft.ApplicationServer.StoreManagement, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35" /> 
     </instanceStoreProviders> 
     <workflowManagement> 
      <workflowManagementServiceInstances lockItem="true"> 
       <workflowManagementServiceInstance name=""> 
        <instanceStores> 
         <instanceStore name="productionSqlPersistenceStore" location="Workflows.Prod" /> 
        </instanceStores> 
       </workflowManagementServiceInstance> 
       <workflowManagementServiceInstance name="Dev"> 
        <instanceStores> 
         <instanceStore name="devSqlPersistenceStore" location="Workflows.Dev" /> 
        </instanceStores> 
       </workflowManagementServiceInstance> 
      </workflowManagementServiceInstances> 
     </workflowManagement> 
     <instanceStores> 
      <add name="devSqlPersistenceStore" provider="SqlPersistenceStoreProvider" connectionStringName="ApplicationServerWorkflowInstanceStoreConnectionString" /> 
      <add name="productionSqlPersistenceStore" provider="SqlPersistenceStoreProvider" connectionStringName="ProductionApplicationServerWorkflowInstanceStoreConnectionString" /> 
     </instanceStores> 
    </persistence> 
    <hosting> 
     <serviceManagement endpointConfiguration="ServiceManagementNetPipeEndpoint" enabled="true" authorizedWindowsGroup="AS_Administrators" /> 
    </hosting> 
</microsoft.applicationServer> 
<connectionStrings> 
    <add connectionString="BigSecret" name="ApplicationServerMonitoringConnectionString" /> 
    <add connectionString="BigSecret" name="ApplicationServerWorkflowInstanceStoreConnectionString" /> 
    <add connectionString="BigSecret" name="ProductionApplicationServerMonitoringConnectionString" /> 
    <add connectionString="BigSecret" name="ProductionApplicationServerWorkflowInstanceStoreConnectionString" /> 
</connectionStrings> 

생산의 Web.config :

<?xml version="1.0" encoding="utf-8"?> 
<configuration> 
    <system.web> 
     <compilation debug="true" targetFramework="4.0" /> 
    </system.web> 
    <system.serviceModel> 
     <protocolMapping> 
      <remove scheme="net.pipe" /> 
     </protocolMapping> 
     <behaviors> 
      <serviceBehaviors> 
       <behavior> 
        <serviceMetadata httpGetEnabled="false" /> 
        <serviceDebug includeExceptionDetailInFaults="false" /> 
        <sqlWorkflowInstanceStore instanceCompletionAction="DeleteAll" instanceEncodingOption="None" instanceLockedExceptionAction="NoRetry" connectionStringName="ProductionApplicationServerWorkflowInstanceStoreConnectionString" hostLockRenewalPeriod="00:00:30" runnableInstancesDetectionPeriod="00:00:05" /> 
        <workflowInstanceManagement authorizedWindowsGroup="AS_Administrators" /> 
        <workflowUnhandledException action="AbandonAndSuspend" /> 
        <workflowIdle timeToPersist="00:00:00" timeToUnload="00:01:00" /> 
       </behavior> 
      </serviceBehaviors> 
     </behaviors> 
     <serviceHostingEnvironment multipleSiteBindingsEnabled="true" /> 
    </system.serviceModel> 
    <system.webServer> 
     <modules runAllManagedModulesForAllRequests="true" /> 
    </system.webServer> 
    <microsoft.applicationServer> 
     <monitoring lockElements="bulkCopyProviders, collectors"> 
      <default enabled="true" connectionStringName="workflowStoreConnectionString" monitoringLevel="HealthMonitoring" /> 
     </monitoring> 
     <persistence> 
      <instanceStores> 
       <remove name="defaultSqlPersistenceStore" /> 
       <add name="defaultSqlPersistenceStore" provider="SqlPersistenceStoreProvider" connectionStringName="workflowStoreConnectionString" /> 
      </instanceStores> 
     </persistence> 
     <hosting> 
      <serviceManagement endpointConfiguration="ServiceManagementNetPipeEndpoint" enabled="false" /> 
     </hosting> 
    </microsoft.applicationServer> 
    <connectionStrings> 
     <add connectionString="BigSecret" name="workflowStoreConnectionString" /> 
    </connectionStrings> 
</configuration> 

데브의 Web.config - 생산하지만 다른 연결 문자열

오류 메시지를 해결하고 볼 수있는에 어떤 도움을와 동일 지속 된 인스턴스가 인정됩니다. TIA. JH

답변

1

msi 설치 프로그램이 SQL 스크립트를 제대로 실행하지 않아 자동으로 실패하고 일부 테이블이 누락되어 문제가 발생했습니다. 스크립트를 수동으로 다시 실행 (C : \ windows \ System32 \ AppFabric \ Schema에있는 Create_Persistence_Schema.sql, Create_Persistence_Logic.sql, Create_Monitoring_Schema.sql 및 Create_Monitoring_Logic.sql)하여 문제를 해결했습니다.