login issue with .NET SDK in BI 4.2 SP4

[former_member280203]

Dear experts,

we have a in house tool, which is built using .net sdk to schedule webi and Crystal reports, which is working well with BI 4.1 SP4.
.NET sdk internally using the soap and restful webservices .

After upgrading to BI 4.2 we are facing few Errors when we try to schedule the reports.

after upgrade we have rebuild the tool with the latest dlls from BI 4.2 .referred sap kba s(2433337) to understand the new security implementations in BI 4.2.

when the .net sdk tool trying to create a new session Errors are encountered..

Code used:

boCred

　 .Login = username

.Password = password

.Domain = ""

.AuthType = "secEnterprise"

_boSession = New Session(boConn)

BoSession.Login(boCred)

Error Message:

Error BOConnect BusinessObjects.DSWS.DSWSException: Login exception (Error: WSE 99999)
at BusinessObjects.DSWS.Session.Session.Login(Credential credential)
at BoWeb.BoService.Logon(String baseUrl, String username, String password)

Error BOLogout BusinessObjects.DSWS.DSWSException: Invalid connection state. (Error: WSE 90001)
at BusinessObjects.DSWS.Session.Session.Logout()
at BoWeb.BoService.Logon(String baseUrl, String username, String password)

LogOut: Error Invalid connection state. (Error: WSE 90001).

Please suggest any options to be changed in BI 4.2 config files.

Thank you for your help.

[daniel_paulsen]

Hi Divi,

Did you compile the tool with the DSWS assemblies embedded with the application or do you rely on the Assemblies being in the application's bin folder or the GAC? We do not install DSWS assemblies to the GAC by default so if they exist there then it could be the older 14.1 versions.

another way to check that he correct file versions for the DSWS consumer assemblies are loaded is to use the ProcessMonitor utility from Microsoft. This utility will show you where the assemblies are loaded from and which File Version is loaded.

Dan

[former_member11696]

Moved to BOE Platform SDK tag.

Check the references in ALL of your app.config files. They need to be pointing to the updated versions.

Likely you may be referencing version 12 assemblies.

Don