Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Thankyou smqlikview for your reply. I was following exactly the steps you mentioned in your post. I click the Connect button, then I specify the driver add, on the secon tab I compile all the fileds: server name, username, password, uncheck blank password, check Allow to save password and Test connection is successful. I've even checked the All properties tab and I see that are properly compiled. When I press ok, the invalid user name error message appears, no chance to insert a new username or password. See the picture below, connection is Ok!
...And this is the error I get after I press Ok. I left unhidden the '\' to highlight that Qlik is using my Domain credentials, instead of a DB user name. I use DB username in different contexts, so I don't think that the problem is outside Qlik..
So I think I'm acting correctly. What is wrong?
Regards
Andrea,
I'm having the exact same problem (old post, new user 
). I've narrowed down the actual issue a bit more, and I don't think we're doing anything wrong. I think it's a bug:
This connection builder utility is not converting the "Use a specific user name and password:" selection into the correct initialization property value. Look on the "All" or "Tutte le proprieta" tab, the problem property is Integrated Security. When Windows NT is chosen, Integrated Security's value is "SSPI", and that works fine. When Specific User Name and Password is selected, Integrated Security's value is blank\empty string. Blank isn't a valid value for the connection builder, so the connection builder tries to use Windows NT by default. That's why you see your NT credentials in the error message. People that have both WindowsNT access and user+pwd credentials for the database don't get the error because their NT credentials are valid.
There was just one server here that I didn't have an NT account for and everyone else did. It was driving me crazy.
We can work around this by changing the Integrated Security property value right before hitting OK using the [Edit Value...] button. Changing the value to "false" or using the [Reset Value] button both work for me. The resulting OLEDB connection omits the Integrated Security property completely. If someone else builds a connection with "Integrated Security ="";" included, you'll have to delete that text before you can reload.
