on 06-10-2011 4:09 AM
Hi,
I've patched BPC 7.5 NW SP05 to SP07 Patch 1 on the server and now whenever users are modifying the BPF in BPC Admin Client, on the Define Actions, whenever they click on Browse, the error below occured.
System.IO.FileLoadException: Could not load file or assembly 'OSoftAdminSecurity, Version=7.50.7.0, Culture=neutral, PublicKeyToken=bf6c37fa78f5a648' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
File name: 'OSoftAdminSecurity, Version=7.50.7.0, Culture-neutral, PublicKeyToken=bf6c37fa78f5a648'
at
OSoft.Consumers.Admin.AdminBPFClient50.ManageDataSet.GetTeamsAndUsers()
at
OSoft.Consumers.Admin.AdminBPFClient50.Main.GetSiteInforXMLForFileBrowser()
at
OSoft.Consumers.Admin.AdminBPFClient50.Main.OpenWebFolder(String sAppsName, String sTask, String sSubTask, WebFolderFilterType iFilterType, String sDocumentFolder)
at
OSoft.Consumers.Admin.AdminBPFClient50.Main.btn.FileBrowse_Click(Object sender, EventArgs e)
WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
Can anyone please help urgently?
I've enabled the assembly bind failure logging and the additional information obtained from the error are below:
=== Pre-bind state information ===
LOG: User = DOMAIN\USERNAME
LOG: DisplayName = OSoftAdminSecurity, Version=7.50.7.0, Culture=neutral, PublicKeyToken=bf6c37fa78f5a648 (Fully-Specified)
LOG: Appbase = file:///C:/Program Files/SAP BusinessObjects/PC_NW/
LOG: Initial PrivatePath = NULL
Calling assembly : OSoftAdminBPFClient, Version 7.50.7.0, Culture=neutral, PublicKeyToken=bf6c37fa78f5a648.
===
LOG: This bind starts in default load context.
LOG: No application configuration file found.
LOG: Using machine configuration file from C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\CONFIG\machine.config.
LOG: Post-policy reference: OSoftAdminSecurity, Version=7.50.7.0, Culture=neutral, PublicKeyToken=bf6c37fa78f5a648
LOG: Attempting download of new URL file:///C:/Program Files/SAP BusinessObjects/PC_NW/OSoftAdminSecurity.DLL.
WRN: Comparing the assembly name resulted in the mismatch: Revision number
ERR: Failed to complete setup of assembly (hr = 0x80131040). Probing terminated.
Edited by: Philip Tan Keng Ping on Jun 10, 2011 8:20 AM
Resolved.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
If you are also using the same environment as me Windows Server 2003 with IIS 6.0, then you will need to do a clean uninstall and then re-install the .NET server. After that while installing the client patch, use the OSoftAdminSecurity.dll from the client installation SP07 Patch 0. Using the Patch 2 client patch seems to have created this error.
User | Count |
---|---|
6 | |
5 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.