"parameter name already exists" while trying to Process Database in SSMS

Question

If I try to Process Database in SQL Management Studio on either of my computers, I get the error:

"parameter name already exists", 
"Parameter name: name (Microsoft.AnalysisServices.BackEnd).

It seems to be an error returning from the AAS server itself (it happens in SSMS 2017 two PCs).

Oddly, I can still successfully process the database if I run the refresh XMLA script above in SQL Management Studio or if I choose to process default or full under "Processing Option" in SSDT.

I have tried deleting the database and redeploying, no luck! Next will be to delete the server and try from scratch.

Is this a known issue, or something we can troubleshoot without deleting the AAS server and starting again?

Answer 1

I have created a new Resource Group, with new AAS server in the same region and deployed the model to it. I'm getting the same parameter name already exists error in SQL Management Studio 2017 when I try to process the database, yet it will process fine with SSDT.

I'm using the same Azure On-Premise Gateway as before, I wonder if there is something happening at the gateway... I'll check the logs.

Answer 2

How are you connecting to the server in the SSMS Connection Dialog?  Which version of SSMS?  Have you tried 17.3 from here?

https://docs.microsoft.com/en-us/sql/ssms/download-sql-server-management-studio-ssms

Thanks,

Matt

Answer 3

Hi Matt,

I'm using v17.3 connecting with Active Directory - Universal with MFA Support.

Following your question, I've tested by connecting with Active Directory - Password and the Process Database works!  When I switch back to Active Directory - Universal with MFA Support I can repro the error again.

Strange. I know I was able to Process Database connected using Active Directory - Universal with MFA Support before... (I think)

Answer 4

I have raised an issue with Microsoft Connect:

https://connect.microsoft.com/SQLServer/feedback/details/3144413

Answer 5

Thanks Brian - I have responded to the Connect and provided a few workarounds.

Answer 6

Thanks for the response Matt. I understand the fact that Active Directory - Universal with MFA Support doesn't work is a bug that is now being investigated.

For completeness on this thread, here's the workaround:

"

Fortunately there are a few workarounds.

1. Generate a script while going through the processing workflow, this will allow you to maintain the existing connection string and process
2. On the initial connection to the server, use Active Directory - Password authentication. 
3. Give the Federated Windows User you are logging into <g class="gr_ gr_16 gr-alert gr_spell gr_inline_cards gr_run_anim ContextualSpelling ins-del multiReplace" data-gr-id="16" id="16">SSMS</g> as process permissions on the model.

"

Answer 7

Hello,

Hopefully this will help others with the "parameter name already exists", "Parameter name: name (Microsoft.AnalysisServices.BackEnd)" issue.

I had the same issue, but discovered my 'Connect to database' was connecting to a specific database.  

Once I changed it to <default>, I was then able to connect via Active Directory - Universal with MFA Support.  

Also, I'm running SSMS v17.4

Thanks

---

Peter Florenzano

Answer 8

I am able to resolve the same with setting Connect to Database to default. Once any database is used here, the tool is considering the value as default for every connection, not sure how to clear this. But every time you connect  make sure it is set to "Default"

Answer 9

Currently we are experiencing the issue when we are processing the Azure Analysis tabular cubes from SSMS. The issue is not there when we process using .Net SDK for SSAS. Finally we were able to workaround by generating the query from the SSMS process dialog and executing the same.

It seems some SSMS UI issue since the query from SSMS works.

Joy

---

www.joyfulwpf.blogspot.com , www.silverlightedweb.blogspot.com, www.joymonscode.blogspot.com

Answer 10

in the SSMS wizart you can use generate script and run the script manually to avoid this issue.

Answer 11

I can confirm this worked for me.  Thanks Peter!

Weston Burr

Answer 12

Tks Peter,

That worked for me also :-)

---

JK

Answer 13

I have just applied the 18.4 update and I am now seeing the same thing.  I get the error in the UI, but I can run the query that is generated from that dialog no problem. Defo a UI issue.

I have the database set to Default.

JK

Answer 14

I have just applied the 18.4 update and I am now seeing the same thing.  I get the error in the UI, but I can run the query that is generated from that dialog no problem. Defo a UI issue.

I have the database set to Default.

JK

I had similar issues after installing 18.4. While I made sure my connection in registered services was set to "<default>", what I found was that when I actually used it to connect it was attempting to connect to a specific database anyway. Changing it again there on the connection dialog made everything work.