Error occurred during Default Reports Deployment "A call to SSPI failed, see inner exception".

(0) Share

Report

Posted on by Akhwand Usman

1,032

Hi, All

I am deploying Dynamics AX 2012R2 defaults reports through Power Shell for Dynamics AX and running it as an administrator. I can neither run Get-AXReport command nor Publish-AXReport command to view and deploy reports. I have checked for these cmdlets for availability in power shell and they are available. Below is the screen shot what I get.

Any Idea what is the reason for this issue.

Regards,

Akhwand Usman

*This post is locked for comments

I have the same question (0)

All responses (8)

Answers (1)

Verified answer

Tommy Skaue Moderator on at

Like (1)

Report

It looks like the WCF binding or configuration is not properly set.

Try to Refresh the WCF configuration.

The steps for refreshing the configuration are similar to the ones outlined here:

technet.microsoft.com/.../jj585430.aspx

- Create a new configuration by using the Microsoft Dynamics AX Configuration utility. To open the configuration utility, click Start > Control Panel > Administrative Tools > Microsoft Dynamics AX 2012 Configuration.

- In the Configuration target list, select Local client.

- Click Manage, and then click Create configuration.

- In the Create configuration dialog box, in the Name box, type a name.

- You can copy settings from either the active configuration or the original configuration, which is the default configuration. Select the configuration to copy settings from, and then click OK.

- Click the Connection tab.

- Click the Refresh button to update the service configuration for client SDK applications.

Was this reply helpful? Yes No
Akhwand Usman 1,032 on at

Like (0)

Report

Thanks Tommy Skaue

I just re-created configuration by copying Active Configuration and then refresh WCF service. And this resolved my problem.

Keep contributing and thanks for the tip.

Regards,

Akhwand Usman

Was this reply helpful? Yes No
Tommy Skaue Moderator on at

Like (0)

Report

My pleasure! Thanks for marking the answer. ;-)

Was this reply helpful? Yes No
jimwat 565 on at

Like (0)

Report

technet.microsoft.com/.../aa496652(v=ax.50).aspx first thing to do

technet.microsoft.com/.../dd362109(v=ax.50).aspx second thing to n ur sorted...

here is the solution:

Setspn.exe -A HTTP/Server1.contoso.corp.contoso.com contoso\AccountName

open cmd and run this on all servers with .net connector.

Was this reply helpful? Yes No
Tommy Skaue Moderator on at

Like (0)

Report

Why on all servers with .Net Connector?

That doesn't make any sense to me.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

Hi Tommy,

Do we have to re-install the AOS and then create a new configuration?

Or just create a new Configuration?

Was this reply helpful? Yes No
Tommy Skaue Moderator on at

Like (0)

Report

No need to reinstall the AOS Service. These are client configurations and can be refreshed using the Microsoft Dynamics AX Configuration utility where the client is installed. The trick is to make sure you persist a complete and working configuration, and finally make sure the configuration is used when starting the client.

Remember a configuration can be saved both in the registry on the machine where the client is run from, or the client can be run using a configuration saved on the file system. Familiarize yourself with how this works and you never have to struggle with this in the future. :-)

Was this reply helpful? Yes No
lennynyk 55 on at

Like (0)

Report

The marked solution worked for me, thank you!

I had previously created a new configuration because we were changing service accounts. I got hit with this issue, when I tried to refresh a Dynamics AX Model Project dataset for an SSRS report in Visual Studio. I was opening VS with the appropriate config and running as admin, but was still getting this SSPI error.

After reading the answer, I opened the Microsoft Dynamics AX 2012 Configuration tool, imported the configuration file that I was interested in, went to the connection tab and simply clicked Refresh Configuration.

This resolved the issue for me.

Thanks again!

Was this reply helpful? Yes No