Problems loggin in after N4.0 SP2 update on SQL ?!

wester
Member Posts: 33
Hi there
I've implemented a Navision 4.02 environment on SQL. I also installed the SP2 update preventing the 2 cm right margin to show up. This works on Native, but running SQL I cannot log into Navision anymore. It simply says, that username or password is incorrect?! Even user SA is rejected!
I've checked almost everything (I guess), and when I return the original files to the client it works again.
Have anyone experienced that? Any ideas how to solve that?
Thanks, in advance
/Wester
I've implemented a Navision 4.02 environment on SQL. I also installed the SP2 update preventing the 2 cm right margin to show up. This works on Native, but running SQL I cannot log into Navision anymore. It simply says, that username or password is incorrect?! Even user SA is rejected!
I've checked almost everything (I guess), and when I return the original files to the client it works again.
Have anyone experienced that? Any ideas how to solve that?
Thanks, in advance
/Wester
0
Comments
-
The first thing you can try is to open the SQL Enterprise Manager (SQL Server Management Studio for SQL 2005) and then make sure that the
databaseuser accounts of you native database are created in the Security
part of the SQL EM. Also check that they have access rights to the SQL navision DB. If thus not help, make one of your users inside the SQL EM a member of the group sysadmin.
After that this user can access the db with the client.
Hope this helps,
Regards,Now, let's see what we can see.
...
Everybody on-line.
...
Looking good!0 -
Hi there
I've checked that out. All users have "God" rights (access to everything).
Even SA can't login...
I haven't changed anything on the SQL Server 2000. The files in the update package has just been overwritten on the client PCs, and then SQL Server rejects the user (wrong username or password).0 -
Can you check if your sql server is working in mixed mode or not.
Mixed mode meaning that Windows Authenticatio and Database authentication are allowed. If this isn't the case only windows authentication is allowed and the SA account won't work.
You can find this in the properties of the sql server instance itself.
Can you also check if the users have access rights to the database itself.
Did you add the xp_ndo.dll to the binn directory of you sql serer and did you add the extended stored procedures in the master database (xp_ndo_enumusergroups and xp_ndo_enumuserids)?
Regards,Now, let's see what we can see.
...
Everybody on-line.
...
Looking good!0
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 320 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions