Jiwa

Thanks Mike and Stuart

Have already tried this, even reupgrading the database. I think the problem is that the users dont exist in the master database. If It try to create them using below queries, I get the errors underneath the queries. Have also uploaded a screenshot

CREATE LOGIN JiwaUser WITH Password = 'JiwaFinancials123'
CREATE LOGIN JiwaReports WITH Password = 'JiwaFinancials123'

Msg 15025, Level 16, State 1, Line 1
The server principal 'JiwaUser' already exists.
Msg 15025, Level 16, State 1, Line 2
The server principal 'JiwaReports' already exists.

Riyaz wrote:Thanks Mike and Stuart

Have already tried this, even reupgrading the database. I think the problem is that the users dont exist in the master database. If It try to create them using below queries, I get the errors underneath the queries. Have also uploaded a screenshot

CREATE LOGIN JiwaUser WITH Password = 'JiwaFinancials123'
CREATE LOGIN JiwaReports WITH Password = 'JiwaFinancials123'

Msg 15025, Level 16, State 1, Line 1
The server principal 'JiwaUser' already exists.
Msg 15025, Level 16, State 1, Line 2
The server principal 'JiwaReports' already exists.

They are not needed in the master database.

Riyaz wrote:Have already tried this, even reupgrading the database.

So can you or can you not login to SSMS as JiwaUser?

I cannot, I’ve tried all known passwords, JiwaFinancials123, etc

Just change the password with a script like

Code: Select all

alter login JiwaUser with password = 'JiwaFinancials123'


Have tried that too, get the attached error.

Read what the error says, you need the manager to show the database up the top as master in Azure you cant just change it up the top you need to be on that database when you open the sql window.

Yes Stuart, but the users are not listed in master database, pls see my screenshot that I had sent earlier. Its very strange, could be the restriction with Azure SQL

This is not a problem related to Azure SQL under normal SQL they don't exist on the master database either, they are logins to the actual server but you must be on the master database to execute those commands.

Understood, thanks for that