SSOSettingsFileReader error

Topics: General Questions
Apr 14, 2010 at 2:33 AM

System.IO.FileNotFoundException: Could not load file or assembly 'SSOSettingsFileReader ,Version=1.0.0.0, Culture=neutral, PublicKeyToken=b9585ffc9d454e4a' or one of its dependencies. The system cannot find the file specified at DeploymentFramework.BuildTasks.UpdateSSOConfigItem.Execute()

Should this file be in the GAC?

Thanks.

Coordinator
Apr 14, 2010 at 6:12 AM

Could you please give me some context around this?  What were you doing?  Is this from a normal deploy from Visual Studio?

In the meantime, SSOSettingsFileReader.dll can be found under the install folder under Framework\DeployTools.  It is fine to GAC it, but I'd like to understand your scenario.

Thanks,
Tom

Apr 14, 2010 at 4:54 PM

Yes, this was a normal deploy in VS2005 bts2006r2 to my local machine.  The SSOSettingsFileReader.dll is in the Framework\DeployTools.

Target DeploySSO:
        Target DevlSSO:
            "C:\Program Files\Deployment Framework for BizTalk\5.0\Framework\DeployTools\SSOSettingsFileImport.exe" //settingsFile:"C:\Source\BizTalk.Deployment\EnvironmentSettings\Devl_settings.xml" /userGroupName:"BIZTALKDEV\sso_administrators" /adminGroupName:"BIZTALKDEV\sso_administrators"
            Application already exists.
            Settings file was associated with application in SSO.
        C:\Program Files\MSBuild\DeploymentFrameworkForBizTalk\5.0\BizTalkDeploymentFramework.targets(1285,5): error MSB4018: The "UpdateSSOConfigItem" task failed unexpectedly.
        C:\Program Files\MSBuild\DeploymentFrameworkForBizTalk\5.0\BizTalkDeploymentFramework.targets(1285,5): error MSB4018: System.IO.FileNotFoundException: Could not load file or assembly 'SSOSettingsFileReader, Version=1.0.0.0, Culture=neutral, PublicKeyToken=b9585ffc9d454e4a' or one of its dependencies. The system cannot find the file specified.
        C:\Program Files\MSBuild\DeploymentFrameworkForBizTalk\5.0\BizTalkDeploymentFramework.targets(1285,5): error MSB4018: File name: 'SSOSettingsFileReader, Version=1.0.0.0, Culture=neutral, PublicKeyToken=b9585ffc9d454e4a'
        C:\Program Files\MSBuild\DeploymentFrameworkForBizTalk\5.0\BizTalkDeploymentFramework.targets(1285,5): error MSB4018:    at DeploymentFramework.BuildTasks.UpdateSSOConfigItem.Execute()
        C:\Program Files\MSBuild\DeploymentFrameworkForBizTalk\5.0\BizTalkDeploymentFramework.targets(1285,5): error MSB4018:    at Microsoft.Build.BuildEngine.TaskEngine.ExecuteTask(ExecutionMode howToExecuteTask, Hashtable projectItemsAvailableToTask, BuildPropertyGroup projectPropertiesAvailableToTask, Boolean& taskClassWasFound)
        C:\Program Files\MSBuild\DeploymentFrameworkForBizTalk\5.0\BizTalkDeploymentFramework.targets(1285,5): error MSB4018:
        C:\Program Files\MSBuild\DeploymentFrameworkForBizTalk\5.0\BizTalkDeploymentFramework.targets(1285,5): error MSB4018: === Pre-bind state information ===
        C:\Program Files\MSBuild\DeploymentFrameworkForBizTalk\5.0\BizTalkDeploymentFramework.targets(1285,5): error MSB4018: LOG: User = BIZTALKDEV\btsadm
        C:\Program Files\MSBuild\DeploymentFrameworkForBizTalk\5.0\BizTalkDeploymentFramework.targets(1285,5): error MSB4018: LOG: DisplayName = SSOSettingsFileReader, Version=1.0.0.0, Culture=neutral, PublicKeyToken=b9585ffc9d454e4a
        C:\Program Files\MSBuild\DeploymentFrameworkForBizTalk\5.0\BizTalkDeploymentFramework.targets(1285,5): error MSB4018:  (Fully-specified)
        C:\Program Files\MSBuild\DeploymentFrameworkForBizTalk\5.0\BizTalkDeploymentFramework.targets(1285,5): error MSB4018: LOG: Appbase = file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/
        C:\Program Files\MSBuild\DeploymentFrameworkForBizTalk\5.0\BizTalkDeploymentFramework.targets(1285,5): error MSB4018: LOG: Initial PrivatePath = NULL
        C:\Program Files\MSBuild\DeploymentFrameworkForBizTalk\5.0\BizTalkDeploymentFramework.targets(1285,5): error MSB4018: Calling assembly : DeploymentFramework.BuildTasks, Version=5.0.0.0, Culture=neutral, PublicKeyToken=null. C:\Program Files\MSBuild\DeploymentFrameworkForBizTalk\5.0\BizTalkDeploymentFramework.targets(1285,5): error MSB4018: === Pre-bind state information ===
        C:\Program Files\MSBuild\DeploymentFrameworkForBizTalk\5.0\BizTalkDeploymentFramework.targets(1285,5): error MSB4018: LOG: User = BIZTALKDEV\z_btsadm
        C:\Program Files\MSBuild\DeploymentFrameworkForBizTalk\5.0\BizTalkDeploymentFramework.targets(1285,5): error MSB4018: LOG: DisplayName = SSOSettingsFileReader, Version=1.0.0.0, Culture=neutral, PublicKeyToken=b9585ffc9d454e4a
        C:\Program Files\MSBuild\DeploymentFrameworkForBizTalk\5.0\BizTalkDeploymentFramework.targets(1285,5): error MSB4018:  (Fully-specified)
        C:\Program Files\MSBuild\DeploymentFrameworkForBizTalk\5.0\BizTalkDeploymentFramework.targets(1285,5): error MSB4018: LOG: Appbase = file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/
        C:\Program Files\MSBuild\DeploymentFrameworkForBizTalk\5.0\BizTalkDeploymentFramework.targets(1285,5): error MSB4018: LOG: Initial PrivatePath = NULL
        C:\Program Files\MSBuild\DeploymentFrameworkForBizTalk\5.0\BizTalkDeploymentFramework.targets(1285,5): error MSB4018: Calling assembly : DeploymentFramework.BuildTasks, Version=5.0.0.0, Culture=neutral, PublicKeyToken=null.
        C:\Program Files\MSBuild\DeploymentFrameworkForBizTalk\5.0\BizTalkDeploymentFramework.targets(1285,5): error MSB4018: ===
        C:\Program Files\MSBuild\DeploymentFrameworkForBizTalk\5.0\BizTalkDeploymentFramework.targets(1285,5): error MSB4018: LOG: This bind starts in LoadFrom load context.
        C:\Program Files\MSBuild\DeploymentFrameworkForBizTalk\5.0\BizTalkDeploymentFramework.targets(1285,5): error MSB4018: WRN: Native image will not be probed in LoadFrom context. Native image will only be probed in default load context, like with Assembly.Load().
        C:\Program Files\MSBuild\DeploymentFrameworkForBizTalk\5.0\BizTalkDeploymentFramework.targets(1285,5): error MSB4018: LOG: Using application configuration file: C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\MSBuild.exe.Config
        C:\Program Files\MSBuild\DeploymentFrameworkForBizTalk\5.0\BizTalkDeploymentFramework.targets(1285,5): error MSB4018: LOG: Using machine configuration file from c:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\config\machine.config.
        C:\Program Files\MSBuild\DeploymentFrameworkForBizTalk\5.0\BizTalkDeploymentFramework.targets(1285,5): error MSB4018: LOG: Post-policy reference: SSOSettingsFileReader, Version=1.0.0.0, Culture=neutral, PublicKeyToken=b9585ffc9d454e4a
        C:\Program Files\MSBuild\DeploymentFrameworkForBizTalk\5.0\BizTalkDeploymentFramework.targets(1285,5): error MSB4018: LOG: Attempting download of new URL file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/SSOSettingsFileReader.DLL.
        C:\Program Files\MSBuild\DeploymentFrameworkForBizTalk\5.0\BizTalkDeploymentFramework.targets(1285,5): error MSB4018: LOG: Attempting download of new URL file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/SSOSettingsFileReader/SSOSettingsFileReader.DLL.
        C:\Program Files\MSBuild\DeploymentFrameworkForBizTalk\5.0\BizTalkDeploymentFramework.targets(1285,5): error MSB4018: LOG: Attempting download of new URL file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/SSOSettingsFileReader.EXE.
        C:\Program Files\MSBuild\DeploymentFrameworkForBizTalk\5.0\BizTalkDeploymentFramework.targets(1285,5): error MSB4018: LOG: Attempting download of new URL file:///C:/WINDOWS/Microsoft.NET/Framework/v2.0.50727/SSOSettingsFileReader/SSOSettingsFileReader.EXE.
        C:\Program Files\MSBuild\DeploymentFrameworkForBizTalk\5.0\BizTalkDeploymentFramework.targets(1285,5): error MSB4018: LOG: Attempting download of new URL file:///C:/Program Files/MSBuild/DeploymentFrameworkForBizTalk/5.0/SSOSettingsFileReader.DLL.
        C:\Program Files\MSBuild\DeploymentFrameworkForBizTalk\5.0\BizTalkDeploymentFramework.targets(1285,5): error MSB4018: LOG: Attempting download of new URL file:///C:/Program Files/MSBuild/DeploymentFrameworkForBizTalk/5.0/SSOSettingsFileReader/SSOSettingsFileReader.DLL.
        C:\Program Files\MSBuild\DeploymentFrameworkForBizTalk\5.0\BizTalkDeploymentFramework.targets(1285,5): error MSB4018: LOG: Attempting download of new URL file:///C:/Program Files/MSBuild/DeploymentFrameworkForBizTalk/5.0/SSOSettingsFileReader.EXE.
        C:\Program Files\MSBuild\DeploymentFrameworkForBizTalk\5.0\BizTalkDeploymentFramework.targets(1285,5): error MSB4018: LOG: Attempting download of new URL file:///C:/Program Files/MSBuild/DeploymentFrameworkForBizTalk/5.0/SSOSettingsFileReader/SSOSettingsFileReader.EXE.
        C:\Program Files\MSBuild\DeploymentFrameworkForBizTalk\5.0\BizTalkDeploymentFramework.targets(1285,5): error MSB4018:
    Done building target "DeploySSO" in project "FRB.EC.OSI.BizTalk.Deployment.btdfproj" -- FAILED.
Done building target "Deploy" in project "FRB.EC.OSI.BizTalk.Deployment.btdfproj" -- FAILED.

Done building project "FRB.EC.OSI.BizTalk.Deployment.btdfproj" -- FAILED.

Coordinator
Apr 14, 2010 at 5:42 PM

This is fixed in 5.0.16, available now on the Downloads page.  Thanks for reporting this!

Tom

Apr 15, 2010 at 1:57 AM

uninstalled  previous version and installed 5.0.16

(the context of this deployment is the same.)

 I'm getting the following errors:

Target UndeploySchemas:
The "GenerateAssemblyNamesItemGroup" task failed unexpectedly.
error MSB4018: System.IO.FileNotFoundException: Could not load file or assembly
C:\Source\BizTalk\Schemas\bin\Debug\Schemas.dll


The Reqistry Key provided is not valid: SOFTWARE\Microsoft\BizTalk ESB Toolkit\2.0

Thanks,

Joseph

 

 

Coordinator
Apr 15, 2010 at 5:52 AM

Is the listed path for your schemas DLL incorrect?  You need to build the solution before you can deploy or undeploy.

If you're getting an error on that registry key, then I'm going to have to create a new release to fix that.  The intention was for the script to continue if the key isn't present.

Thanks,
Tom

Coordinator
Apr 15, 2010 at 4:47 PM

I checked into the ESB Toolkit registry key error and it's not a real error, just a harmless error message written to the MSBuild output.  To avoid confusion, I'll have a change in the next release that will prevent the error message from being displayed.

Thanks,
Tom

Apr 15, 2010 at 5:50 PM

Thanks for explaining the ESB Toolkit message

 

here's the path for my schemas:

c:\Source\BizTalk\MyProject.BizTalk.Artifacts\bin\Debug\BizTalk.Artifacts.dll

and in the btdfproj:

<Schemas>$(ProjectName).BizTalk.Artifacts</Schemas>

however the error reports:

System.IO.FileNotFoundException: Could not load file or assembly

C:\Source\MyProject.BizTalk\Schemas\bin\Debug\Schemas.dll

This configuration worked on the prior release.

Thanks,

Joseph

 

 

Coordinator
Apr 15, 2010 at 6:01 PM

Hi Joseph,

The file format was modified a few releases ago.  You just need to do a quick change in your .btdfproj to the new structure.  There are examples in the release notes.

Thanks,
Tom

Apr 16, 2010 at 6:13 PM

Hi Tom:

Removed the property group, added the item group as per your instructions in the release notes with the following modification of the example provided:

<ItemGroup>
        <Schemas Include="$(ProjectName).Biztalk.Artifacts.dll">
                  <LocationPath>..\$(ProjectName).Biztalk.Artifacts\bin\$(Configuration)</LocationPath>
        </Schemas>
</ItemGroup>

and deployed successfully.

Any timeline on when the ESB Toolkit error-message will be suppressed?

Thanks again for your help,

Joseph

Coordinator
Apr 16, 2010 at 7:23 PM

Great, thanks for the update.  The change to eliminate the false ESB Toolkit registry key error message is already checked in and available under the Source Code tab.  You'd just need to replace your DeploymentFramework.BuildTasks.dll and BizTalkDeploymentFramework.targets with the new versions.  My guess is that I won't publish a new official release for 2+ weeks.

Thanks,
Tom

Apr 16, 2010 at 8:48 PM

Hi Tom,

     Joseph and I are working together.

     We had another side effect in the upgrade to 5.0.16 Beta.  We also had a C# components library in some of our projects, and the following GAC built the wrong name:

"C:\Program Files\Deployment Framework for BizTalk\5.0\Framework\DeployTools\gacutil.exe" /i "..\ABC.EC.BookTransfer.Components\bin\Debug\ABC.EC.BookTransfer.Components.dll"

It should have been:

"C:\Program Files\Deployment Framework for BizTalk\5.0\Framework\DeployTools\gacutil.exe" /i "..\ABC.EC.BookTransfer.BizTalk.Components\bin\Debug\ABC.EC.BookTransfer.BizTalk.Components.dll"

The directory where our solution is located is ABC.EC.BookTransfer.BizTalk, but our btdfproj file shows Project Name as:

<ProjectName>FRB.EC.BookTransfer</ProjectName>

Looks like maybe you switched from using relative paths to using the $(ProjectName)?

So we also had to add the following statements to get around this problem:

 <ItemGroup>
  <Components Include="$(ProjectName).Biztalk.Components.dll">
   <!-- You must add the correct path to the DLL -->
   <LocationPath>..\$(ProjectName).Biztalk.Components\bin\$(Configuration)</LocationPath>
  </Components>
 </ItemGroup>
 

Thanks

Neal Walters

 

Coordinator
Apr 19, 2010 at 4:50 PM

If you're trying to use the default configuration where you do not explicitly specify the <Schemas>, <Components>, etc. in the .btdfproj, then you have to exactly follow the naming conventions that are explained in the documentation.  Basically each BizTalk project folder name would have to be the same as the output DLL filename (minus .dll of course), and the Schemas project must be named $(ProjectName).Schemas, Components $(ProjectName).Components, etc.

Those conventions haven't changed at all.  If you don't want to be restricted to the naming conventions, then you can easily override them as you did above with the ItemGroup.

If you were following all of the defaults, and your BizTalk projects were named ABC.EC.BookTransfer.BizTalk.Schemas, ABC.EC.BookTransfer.BizTalk.Components, etc. then your <ProjectName> should have been ABC.EC.BookTransfer.BizTalk.

In any case, what you have now will work perfectly well at the expense of a bit more configuration XML in the .btdfproj.

Thanks,
Tom

Jun 13, 2013 at 2:32 PM
tfabraham wrote:
This is fixed in 5.0.16, available now on the Downloads page.  Thanks for reporting this! Tom
I am using Latest version Beta for BTS 2013 but this error still persist

System.IO.FileNotFoundException: Could not load file or assembly 'SSOSettingsFileReader ,Version=1.0.0.0, Culture=neutral, PublicKeyToken=b9585ffc9d454e4a' or one of its dependencies. The system cannot find the file specified at DeploymentFramework.BuildTasks.UpdateSSOConfigItem.Execute()

Its working on development box but not on test or stage machines.
Coordinator
Jun 13, 2013 at 4:18 PM
SSOSettingsFileReader.dll is always deployed to the GAC automatically. Do you have anything named AdditionalAssemblies in your .btdfproj? Please search for Deploying additional assemblies to GAC... in the log after a deployment and capture the log output for review.

Thanks,
Tom
Jun 14, 2013 at 6:50 AM
I am only deploying schemas, maps, orchestration, and pipelines. I have Include SSO true. An application is being created in SSO when I see it from SSOSetting Editor. I am not recognising that how SSOSettingEditor is working though it also uses SSOSettingFileReader.dll. I tried to run SSOSettingFileImport alone. It is also creating an application in SSO. But when I try to run MSI on other boxes it fails in UpdateSSOConfigItem step saying file not found error.
Coordinator
Jun 14, 2013 at 7:06 AM
Please capture the log output from the DeployResults.txt on one of the servers. Search for Deploying additional assemblies to GAC.

Thanks,
Tom
Jun 14, 2013 at 7:33 AM
Please find attached log file...

Jun 14, 2013 at 7:34 AM
Build started 2013-06-13 17:46:00.

Project "D:\BizTalkApps\XXXXXXXXXXXXXXX\1.0\Deployment\Deployment.btdfproj" (Deploy target(s)):

Target Deploy:
Target SetModeDeploy:
    DEPLOYING APPLICATION TO BIZTALK...
Target ServerDeploy:
    Target SetWinVer:
        Running on Windows V61
        Detected IIS 7
        Detected 64-bit OS
    Target GetSoftwarePaths:
        Using .NET Framework Install Path 'C:\Windows\Microsoft.NET\Framework\v4.0.30319'.
        Using BizTalk Install Path 'C:\Program Files (x86)\Microsoft BizTalk Server 2013\'.
        Using Deployment Framework Install Path 'D:\BizTalkApps\XXXXXXXXXXXXXXX\1.0\Deployment\'.
        Using Deployment Framework Tools Path 'D:\BizTalkApps\XXXXXXXXXXXXXXX\1.0\Deployment\Framework\DeployTools'.
    Target ExportSettings:
        "D:\BizTalkApps\XXXXXXXXXXXXXXX\1.0\Deployment\Framework\DeployTools\EnvironmentSettingsExporter.exe" "D:\BizTalkApps\XXXXXXXXXXXXXXX\1.0\Deployment\EnvironmentSettings\SettingsFileGenerator.xml" "D:\BizTalkApps\XXXXXXXXXXXXXXX\1.0\Deployment\EnvironmentSettings"
        Environment Settings Spreadsheet to XML Exporter 1.6.1
        [http://EnvSettingsManager.codeplex.com]
        Copyright (C) 2007-11 Thomas F. Abraham.  All Rights Reserved.

        Importing from SettingsFileGenerator.xml...

        Output format is XmlPreprocess (multi-file).

        Exporting to Exported_LocalSettings.xml...
        Exporting to Exported_DevSettings.xml...
        Exporting to Exported_TestSettings.xml...
        Exporting to Exported_ProdSettings.xml...

        Finished.
    Target InitSettingsFilePath:
        SetRegistryValue: Attempting to create/update value 'D:\BizTalkApps\XXXXXXXXXXXXXXX\1.0\Deployment\EnvironmentSettings\Exported_TestSettings.xml' in registry value 'LastDeploySettingsFilePath' at key 'HKEY_LOCAL_MACHINE\SOFTWARE\Vattenfall AB\XXXXXXXXXXXXXXX'...
        SetRegistryValue: Successfully created/updated value.
        Using settings file D:\BizTalkApps\XXXXXXXXXXXXXXX\1.0\Deployment\EnvironmentSettings\Exported_TestSettings.xml
    Target SetPropertiesFromEnvironmentSettings:
        Setting properties from environment settings file (D:\BizTalkApps\XXXXXXXXXXXXXXX\1.0\Deployment\EnvironmentSettings\Exported_TestSettings.xml)
        Setting property to value 'MYDOMAIN\User'.
        Setting property to value 'MYDOMAIN\Admin'.
    Target InitializeAppName:
        BizTalk Application Name is XXXXXXXXXXXXXXX
    Target PreprocessBindings:
        Clearing file attributes for '..\Bindings\XXXXXXXXXXXXXXX.xml'.
        "D:\BizTalkApps\XXXXXXXXXXXXXXX\1.0\Deployment\Framework\DeployTools\xmlpreprocess.exe" /f /v /c /noDirectives /i:"D:\BizTalkApps\XXXXXXXXXXXXXXX\1.0\Deployment\XXXXXXXXXXXXXXX.PortBindingsMaster.xml" /o:"D:\BizTalkApps\XXXXXXXXXXXXXXX\1.0\Deployment\..\Bindings\XXXXXXXXXXXXXXX.Bindings.xml" /d:CurDir="D:\BizTalkApps\XXXXXXXXXXXXXXX\1.0" /s:"D:\BizTalkApps\XXXXXXXXXXXXXXX\1.0\Deployment\EnvironmentSettings\Exported_TestSettings.xml"
        XmlPreprocess v2.0.13.0
        Copyright (c) 2004-2010 Loren M Halvorson
        XML File Preprocessor

        Settings XML file: "D:\BizTalkApps\XXXXXXXXXXXXXXX\1.0\Deployment\EnvironmentSettings\Exported_TestSettings.xml"
        Preprocessing "D:\BizTalkApps\XXXXXXXXXXXXXXX\1.0\Deployment\XXXXXXXXXXXXXXX.PortBindingsMaster.xml" to "D:\BizTalkApps\XXXXXXXXXXXXXXX\1.0\Deployment\..\Bindings\XXXXXXXXXXXXXXX.Bindings.xml"...
        XXXXXXXXXXXXXXX.Bindings.xml : Set the value 'XXXXXXXXXXXXXXX' of 6 node(s) matching XPath '//ApplicationName'.
        "D:\BizTalkApps\XXXXXXXXXXXXXXX\1.0\Deployment\Framework\DeployTools\ElementTunnel.exe" /i:"D:\BizTalkApps\XXXXXXXXXXXXXXX\1.0\Deployment\..\Bindings\XXXXXXXXXXXXXXX.Bindings.xml" /o:"D:\BizTalkApps\XXXXXXXXXXXXXXX\1.0\Deployment\..\Bindings\XXXXXXXXXXXXXXX.Bindings.xml" /x:"D:\BizTalkApps\XXXXXXXXXXXXXXX\1.0\Deployment\Framework\DeployTools\adapterXPaths.txt" /encode+
        Nested XML Encoder/Decoder v5.1.100.0
        Copyright (C) 2005-2013 Scott Colestock, Tim Rayburn, Thomas F. Abraham

        XML encodes/decodes content of element(s) by XPath. Applies escaping rules such
        as &gt; for '<'. Namespace decls, PIs, etc. of nested XML are not preserved.

        XPaths                        : 15
        Transformed Nodes             : 0
        Empty Nodes (skipped)         : 7
        No Transform Req'd (skipped)  : 18
        Total Matched Nodes           : 25

        Complete - output file has been saved.
    Target CustomSSODeploy:
        "D:\BizTalkApps\XXXXXXXXXXXXXXX\1.0\Deployment\Framework\DeployTools\SSOSettingsFileImport.exe" "XXXXXXXXXXXXXXX" /deleteApp
        Affiliate application 'XXXXXXXXXXXXXXX' deleted.
        "D:\BizTalkApps\XXXXXXXXXXXXXXX\1.0\Deployment\Framework\DeployTools\SSOSettingsFileImport.exe" "XXXXXXXXXXXXXXX" /settingsFile:"D:\BizTalkApps\XXXXXXXXXXXXXXX\1.0\Deployment\EnvironmentSettings\Exported_TestSettings.xml" /userGroupName:"MYDOMAIN\USer" /adminGroupName:"MYDOMAIN\Admin"
        Affiliate application 'XXXXXXXXXXXXXXX' was created.
        Settings file was associated with application 'XXXXXXXXXXXXXXX' in SSO.
        D:\BizTalkApps\XXXXXXXXXXXXXXX\1.0\Deployment\Deployment.btdfproj(179,5): error MSB4018: The "UpdateSSOConfigItem" task failed unexpectedly.
        D:\BizTalkApps\XXXXXXXXXXXXXXX\1.0\Deployment\Deployment.btdfproj(179,5): error MSB4018: System.IO.FileNotFoundException: Could not load file or assembly 'SSOSettingsFileReader, Version=1.0.0.0, Culture=neutral, PublicKeyToken=b9585ffc9d454e4a' or one of its dependencies. The system cannot find the file specified.
        D:\BizTalkApps\XXXXXXXXXXXXXXX\1.0\Deployment\Deployment.btdfproj(179,5): error MSB4018: File name: 'SSOSettingsFileReader, Version=1.0.0.0, Culture=neutral, PublicKeyToken=b9585ffc9d454e4a'
        D:\BizTalkApps\XXXXXXXXXXXXXXX\1.0\Deployment\Deployment.btdfproj(179,5): error MSB4018:    at DeploymentFramework.BuildTasks.UpdateSSOConfigItem.Execute()
        D:\BizTalkApps\XXXXXXXXXXXXXXX\1.0\Deployment\Deployment.btdfproj(179,5): error MSB4018:    at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute()
        D:\BizTalkApps\XXXXXXXXXXXXXXX\1.0\Deployment\Deployment.btdfproj(179,5): error MSB4018:    at Microsoft.Build.BackEnd.TaskBuilder.<ExecuteInstantiatedTask>d__20.MoveNext()
        D:\BizTalkApps\XXXXXXXXXXXXXXX\1.0\Deployment\Deployment.btdfproj(179,5): error MSB4018: 
        D:\BizTalkApps\XXXXXXXXXXXXXXX\1.0\Deployment\Deployment.btdfproj(179,5): error MSB4018: WRN: Assembly binding logging is turned OFF.
        D:\BizTalkApps\XXXXXXXXXXXXXXX\1.0\Deployment\Deployment.btdfproj(179,5): error MSB4018: To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
        D:\BizTalkApps\XXXXXXXXXXXXXXX\1.0\Deployment\Deployment.btdfproj(179,5): error MSB4018: Note: There is some performance penalty associated with assembly bind failure logging.
        D:\BizTalkApps\XXXXXXXXXXXXXXX\1.0\Deployment\Deployment.btdfproj(179,5): error MSB4018: To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
        D:\BizTalkApps\XXXXXXXXXXXXXXX\1.0\Deployment\Deployment.btdfproj(179,5): error MSB4018: 
    Done building target "CustomSSODeploy" in project "Deployment.btdfproj" -- FAILED.
Done building target "ServerDeploy" in project "Deployment.btdfproj" -- FAILED.
Done building target "Deploy" in project "Deployment.btdfproj" -- FAILED.

Done building project "Deployment.btdfproj" -- FAILED.

Build FAILED.

D:\BizTalkApps\XXXXXXXXXXXXXXX\1.0\Deployment\Deployment.btdfproj(179,5): error MSB4018: The "UpdateSSOConfigItem" task failed unexpectedly.
D:\BizTalkApps\XXXXXXXXXXXXXXX\1.0\Deployment\Deployment.btdfproj(179,5): error MSB4018: System.IO.FileNotFoundException: Could not load file or assembly 'SSOSettingsFileReader, Version=1.0.0.0, Culture=neutral, PublicKeyToken=b9585ffc9d454e4a' or one of its dependencies. The system cannot find the file specified.
D:\BizTalkApps\XXXXXXXXXXXXXXX\1.0\Deployment\Deployment.btdfproj(179,5): error MSB4018: File name: 'SSOSettingsFileReader, Version=1.0.0.0, Culture=neutral, PublicKeyToken=b9585ffc9d454e4a'
D:\BizTalkApps\XXXXXXXXXXXXXXX\1.0\Deployment\Deployment.btdfproj(179,5): error MSB4018: at DeploymentFramework.BuildTasks.UpdateSSOConfigItem.Execute()
D:\BizTalkApps\XXXXXXXXXXXXXXX\1.0\Deployment\Deployment.btdfproj(179,5): error MSB4018: at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute()
D:\BizTalkApps\XXXXXXXXXXXXXXX\1.0\Deployment\Deployment.btdfproj(179,5): error MSB4018: at Microsoft.Build.BackEnd.TaskBuilder.<ExecuteInstantiatedTask>d__20.MoveNext()
D:\BizTalkApps\XXXXXXXXXXXXXXX\1.0\Deployment\Deployment.btdfproj(179,5): error MSB4018:
D:\BizTalkApps\XXXXXXXXXXXXXXX\1.0\Deployment\Deployment.btdfproj(179,5): error MSB4018: WRN: Assembly binding logging is turned OFF.
D:\BizTalkApps\XXXXXXXXXXXXXXX\1.0\Deployment\Deployment.btdfproj(179,5): error MSB4018: To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
D:\BizTalkApps\XXXXXXXXXXXXXXX\1.0\Deployment\Deployment.btdfproj(179,5): error MSB4018: Note: There is some performance penalty associated with assembly bind failure logging.
D:\BizTalkApps\XXXXXXXXXXXXXXX\1.0\Deployment\Deployment.btdfproj(179,5): error MSB4018: To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!Enab
Jun 14, 2013 at 7:35 AM
Coordinator
Jun 14, 2013 at 7:56 AM
You have added a custom target CustomSSODeploy that runs before the assemblies have even been deployed. You should schedule your custom target to run after DeploySharedAssemblies, and probably after DeploySSO.

Tom
Jun 14, 2013 at 8:11 AM
Edited Jun 14, 2013 at 10:50 AM
It worked. MSI installation doesn't work. I ran the .bat file as admin it worked.

Thanks for your quick response. Will come back with new issues if occurs :) :) It may multiple BAM activity deployment (in different definition files)
Jun 14, 2013 at 1:30 PM
Hi Tom,
I found the real issue now but not the solution. I have BizTalk clustered environment(2 instances). When I run the msi on instance1 it works fine. But when I run the msi from instance2 it gives the above error (SSOFileReader.dll not found).
Issue is with GACing of SSOSettingFileReader. I am not able able to understand why it is not gaced in 2nd isntance.
What could be the possible reason. Please suggest.
Coordinator
Jun 14, 2013 at 6:21 PM
As I mentioned above, you have implemented your own custom SSO deployment (CustomSSODeploy target) and that is the source of the problem. It appears that the custom target is a copy of the default DeploySSO target except with a property that overrides the SSO app name.

If you change the Name of the target CustomDeployTarget to CustomSSO, it will execute your custom SSO processing after the assembly has been deployed to the GAC.

Tom