Skip to main content

Hi.

I like to have most of the essential translation parameters as published. This typically includes the database server name and the database name when working with (MS/SQL) databases.

But when I press the "..." next to the current value to choose another, I get an unexpected error, stating that I gave an "Invalid authorization specification", even though I've set it to "Windows Authentication" originally, which worked then.

I cannot specify any other "authentification", so I'm left with having to write the database name manually. Not cool, and not very productive. And I cannot change the parameter into a choice list either.

Is there another way to get this to work ?

Cheers

I was able to reproduce the issue you've documented. We probably do need to look at this and see if we can fix it. I did find that if I select the Authentication method first, then set the Server and then select the Database it worked. In 2018 and up we have rearranged the order of the parameters, so that the Server is the first parameter, which makes more sense.


Hi Mark.

I'll try this workaround at once, but it actually makes sense, since the dialog starts out with SQL Authentication with no user or password.

Can I remedy the existing connection, or should I make a new to replace the old, you think ?

Cheers.


Hi Mark.

I'll try this workaround at once, but it actually makes sense, since the dialog starts out with SQL Authentication with no user or password.

Can I remedy the existing connection, or should I make a new to replace the old, you think ?

Cheers.

I tested it, and the workaround worked.

You do need to create a new replacement connection _and_ recreate the published parameter, as the deficiency of the original connection is inhereted into the parameter setup.

But when that's done, it works nicely. Thanks Mark. I'll make sure to set the Authentication first in all future connection dialogs 🙂


Reply