locked
MDS Model deployment loosing business rules RRS feed

  • Question

  • Our current MDS model isn't deploying with Business Rules.
    We have tried it into 3 diffrent MDS servers with no luck. Both with and with out data.
     
    Our understanding was the latest version of MDS  which we are running (Version:  10.51.2772.0 ) had this issue resolved.
     
    Our Model with data is 157MB.
    There are 7 entities with 8 core Business Rules in each.
     
    would be great if we could get this working.
    Is there a resolution?

    Tamzyn!
    Friday, September 9, 2011 5:21 AM

Answers

  • Hi,

    Just found out this is a known issue (thanks to N.Raja from Microsoft Australia)

     http://technet.microsoft.com/en-au/library/ff487018.aspx#errors

    Unfortunatly because data isn't loading befor business rules being created we have a problem that still needs resolving for deployment of our model with large amount of data.

                          The package processes but errors are generated

                          When you deploy a package, business rules may not be deployed successfully to the destination environment.
                          This issue occurs when the business rules take action based on attribute values and the deployment package does not contain master data.

                          To fix this issue, you can create the business rules in the destination environment or create a new package that contains the data.

    Thanks again for your time Xavier.


    Tamzyn!
    • Marked as answer by tamzynb Monday, September 19, 2011 4:57 AM
    Monday, September 19, 2011 4:57 AM

All replies

  • Hi Tamzyn

    did you include data when creating the model ?

    if not, some data based business rules may crash when deploying

    you could also activate the MDS Website trace (in web.config) and check the trace log to see if any B.R. related errors

    http://sqlblog.com/blogs/mds_team/archive/2010/01/05/trace-logging-in-sql-server-2008-r2-master-data-services.aspx

     

    Regards,



    Xavier Averbouch
    Microsoft Community Contributor
    Avanade , FRANCE
    If a post answers your question, please click "Mark As Answer" on that post and "Vote as Helpful".
    Tuesday, September 13, 2011 2:16 PM
  • Hi Xavier

    thanks for your reponse. we have tried with and with out data.

    there are 26 entities with 7 of them having Business rules.

    no errors are generated when deploying the model. BUT when I go into the Business Rule of the entity that should have rules against it it is producing this in the MDSTrace (see below)

    have you seen that befor? any ideas?
    cheers Tamzyn

    <BusinessRulesGetResponse xmlns="http://schemas.datacontract.org/2004/07/Microsoft.MasterDataServices.Services.MessageContracts" xmlns:i="http://www.w3.org/2001/XMLSchema-instance">
      <OperationResult xmlns:a="http://schemas.microsoft.com/sqlserver/masterdataservices/2009/09">
        <a:Errors />
        <a:RequestId>a1ccdc64-89c8-4589-9069-2a20d037428c</a:RequestId>
      </OperationResult>
      <BusinessRuleSet xmlns:a="http://schemas.microsoft.com/sqlserver/masterdataservices/2009/09">
        <a:BRActions />
        <a:BRConditionTreeNodes />
        <a:BRConditions />
        <a:BusinessRules />
      </BusinessRuleSet>
    </BusinessRulesGetResponse>
        DateTime=2011-09-14T00:38:20.2203166Z
    MDS Verbose: 0 : Unable to convert value of query string parameter Id = MID to an integer
        DateTime=2011-09-14T00:38:20.2203166Z
    MDS Verbose: 0 : Unable to convert value of query string parameter Id = VID to an integer
        DateTime=2011-09-14T00:38:20.2203166Z
    MDS Verbose: 0 : Unable to convert value of query string parameter Id = MID to an integer
        DateTime=2011-09-14T00:38:20.2203166Z
    MDS Verbose: 0 : Unable to convert value of query string parameter Id = VID to an integer
        DateTime=2011-09-14T00:38:20.2203166Z


    Tamzyn!
    Wednesday, September 14, 2011 12:42 AM
  • Hi Xavier,

    I also looked backingto the MDSTrace log and found that the load logged that "request timed out" when checking batch status.
    I have tried to include the full log segment (see below). The time out is 7 line from the bottom. Are Business rules the last item to be loaded and could the time out be effecting the load. where would I change the load time?

    Cheer
    Tamzyn

    MDS Start: 1 : Deployment: checking batch status
        DateTime=2011-09-14T00:27:29.0671707Z
    MDS Start: 1 :
                      Begin operation: ExecuteRequest
                      Host info:       http://localhost:80/MDS/Admin/Wizards/WizardDeployment/Pages/DeployModelPage.aspx
                      User Name:       OVLE63202PCQ2Q1\MDS_ADMIN
                      Time:            09/14/2011 10:27:29
        DateTime=2011-09-14T00:27:29.0671707Z
    MDS Verbose: 0 : Request message:
    <StagingGetRequest xmlns="http://schemas.datacontract.org/2004/07/Microsoft.MasterDataServices.Services.MessageContracts" xmlns:i="http://www.w3.org/2001/XMLSchema-instance">
      <International i:nil="true" xmlns:a="http://www.w3.org/2005/09/ws-i18n" />
      <IncludeUnbatchedInformation>false</IncludeUnbatchedInformation>
      <StagingResultCriteria xmlns:a="http://schemas.microsoft.com/sqlserver/masterdataservices/2009/09">
        <a:All>true</a:All>
      </StagingResultCriteria>
      <StagingSearchCriteria xmlns:a="http://schemas.microsoft.com/sqlserver/masterdataservices/2009/09">
        <a:StagingBatches>
          <a:Identifier>
            <a:Id>cceb7762-c2e4-4154-a5b7-1dee13cab9d4</a:Id>
            <a:Name>Education_VERSION_1_09/14/2011 00:23:08</a:Name>
            <a:InternalId>0</a:InternalId>
          </a:Identifier>
        </a:StagingBatches>
        <a:StagingDataStatus>Error</a:StagingDataStatus>
      </StagingSearchCriteria>
    </StagingGetRequest>
        DateTime=2011-09-14T00:27:29.0671707Z
    MDS Start: 1 : RequestContext.InitializeRequestContext
        DateTime=2011-09-14T00:27:29.0671707Z
    MDS Start: 1 : RequestContext.InitializeDatabaseContext
        DateTime=2011-09-14T00:27:29.0671707Z
    MDS Stop: 2 : RequestContext.InitializeDatabaseContext
        DateTime=2011-09-14T00:27:29.0671707Z
    MDS Start: 1 : RequestContext.InitializeCurrentUser
        DateTime=2011-09-14T00:27:29.0671707Z
    MDS Verbose: 0 : Successfully obtained the current Windows principal from the host context.
        DateTime=2011-09-14T00:27:29.0671707Z
    MDS Information: 0 : Successfully obtained the current windows identity: Name=OVLE63202PCQ2Q1\MDS_ADMIN, SID=S-1-5-21-1543031505-3126953139-3705730488-1011 from the windows principal.
        DateTime=2011-09-14T00:27:29.0671707Z
    MDS Information: 0 : Session support is enabled for the current request for user OVLE63202PCQ2Q1\MDS_ADMIN.
        DateTime=2011-09-14T00:27:29.0671707Z
    MDS Start: 1 : RequestContext.IsExistingSession
        DateTime=2011-09-14T00:27:29.0671707Z
    MDS Information: 0 : An existing session or conversation has been found for session u01p0i45xzsyvmrdrkosw045.
        DateTime=2011-09-14T00:27:29.0671707Z
    MDS Stop: 2 : RequestContext.IsExistingSession
        DateTime=2011-09-14T00:27:29.0671707Z
    MDS Information: 0 : Cached information is being used for user OVLE63202PCQ2Q1\MDS_ADMIN.
        DateTime=2011-09-14T00:27:29.0671707Z
    MDS Information: 0 : User OVLE63202PCQ2Q1\MDS_ADMIN successfully authenticated to MDS.
        DateTime=2011-09-14T00:27:29.0671707Z
    MDS Stop: 2 : RequestContext.InitializeCurrentUser
        DateTime=2011-09-14T00:27:29.0671707Z
    MDS Stop: 2 : RequestContext.InitializeRequestContext
        DateTime=2011-09-14T00:27:29.0671707Z
    MDS Stop: 2 :
                      End  operation: StagingGet
                      Host info:       http://localhost:80/MDS/Admin/Wizards/WizardDeployment/Pages/DeployModelPage.aspx
                      User Name:       OVLE63202PCQ2Q1\MDS_ADMIN
                      Time:            09/14/2011 10:27:29
        DateTime=2011-09-14T00:27:29.2387710Z
    MDS Verbose: 0 : Response message:
    <StagingGetResponse xmlns="http://schemas.datacontract.org/2004/07/Microsoft.MasterDataServices.Services.MessageContracts" xmlns:i="http://www.w3.org/2001/XMLSchema-instance">
      <OperationResult xmlns:a="http://schemas.microsoft.com/sqlserver/masterdataservices/2009/09">
        <a:Errors />
        <a:RequestId>63eb4b97-91e0-4b3b-bfdb-30fc6ed0333b</a:RequestId>
      </OperationResult>
      <UnbatchedInformation xmlns:a="http://schemas.microsoft.com/sqlserver/masterdataservices/2009/09" />
    </StagingGetResponse>
        DateTime=2011-09-14T00:27:29.2387710Z
    MDS Stop: 2 : Deployment: checking batch status
        DateTime=2011-09-14T00:27:29.2387710Z
    MDS Error: 0 : Request timed out.
        DateTime=2011-09-14T00:27:34.3711800Z
    MDS Start: 1 : HostContext.GetHostContext
        DateTime=2011-09-14T00:37:52.4794677Z
    MDS Information: 0 : The host context is detected to be ASP.NET.
        DateTime=2011-09-14T00:37:52.4794677Z
    MDS Information: 0 : Successfully set culture to 'en-AU'.


    Tamzyn!
    Wednesday, September 14, 2011 1:04 AM
  • OK been doing some further testing by loading with out data and the rules aren't coming through cause they get

     

    MDS Error: 0 : The attribute code is not valid.
       at Microsoft.MasterDataServices.Core.DataAccess.DbHelper.HandleExceptions(Exception ex)
       at Microsoft.MasterDataServices.Core.DataAccess.DbHelper.ExecuteNonQuery(String query, CommandType commandType, CloseConnectionBehavior closeBehavior)
       at Microsoft.MasterDataServices.Core.DataAccess.BusinessRules.BusinessRuleItemPropertySave(CloseConnectionBehavior closeBehavior, SaveType saveType, Int32 itemId, BRPropertyType propertyType, BRPropertyName propertyName, String value, String attributeName, Int32 sequence, Boolean isLeftHandSide, Int32 parentId, Boolean suppressText, Guid& muid, Int32& id)
       at Microsoft.MasterDataServices.Core.BusinessLogic.BusinessRules.SaveArgument(BRArgument argument, SaveType saveType, Int32 itemId, Int32 sequence, Int32 parentId, Boolean isPrefix, AttributeDataType anchorDataType, OperationResult result)
    SQL Error Debug Info: Number: 400022, Message: Invalid Attribute Code., Server: OVLE63202PCQ2Q1\TAM_DWH01, Proc: udpBusinessRuleItemPropertyAddHelper, Line: 62

    Has anyone seen this error?

     

    cheers


    Tamzyn!
    Thursday, September 15, 2011 6:42 AM
  • Hi 

    what kind of code value do you have that could make MDS crash ?



    Xavier Averbouch
    Microsoft Community Contributor
    Avanade , FRANCE
    If a post answers your question, please click "Mark As Answer" on that post and "Vote as Helpful".
    Thursday, September 15, 2011 7:44 AM
  • Hi,

    Just found out this is a known issue (thanks to N.Raja from Microsoft Australia)

     http://technet.microsoft.com/en-au/library/ff487018.aspx#errors

    Unfortunatly because data isn't loading befor business rules being created we have a problem that still needs resolving for deployment of our model with large amount of data.

                          The package processes but errors are generated

                          When you deploy a package, business rules may not be deployed successfully to the destination environment.
                          This issue occurs when the business rules take action based on attribute values and the deployment package does not contain master data.

                          To fix this issue, you can create the business rules in the destination environment or create a new package that contains the data.

    Thanks again for your time Xavier.


    Tamzyn!
    • Marked as answer by tamzynb Monday, September 19, 2011 4:57 AM
    Monday, September 19, 2011 4:57 AM