You’re offline. This is a read only version of the page.
80
We recently enforced password complexity rules and i understand this should be pulling the policy from AD. What happens is when users are prompted to reset their passwords they cannot type in anything. The system says the new password is invalid. I have to manually reset the password as 'sa'. When I login as 'sa' I can type the same password the user just tried without any issues. Of course, I have to uncheck the 'reset upon login' box otherwise we are back to square one.
GP 9 - SQL 2005
Any help would be appreciated,
Tony.
*This post is locked for comments
Yes. But I would cover the server (2003) too.
Forgive me for the questions but I want to make sure I have the correct things.
A little background...
GP/FRx 6.7 itself and SQL 2005 are installed on the same server - 2003 member server in 2008 domain.
I have the GP installed on XP computers and 2 Citrix 2008 (x86, non-R2) servers.
Just checked SQL ODBC driver on the Citrix server - SQL Driver 6.00.6001.18000
I checked MS site as noted and found Native SQL Client x86 v9.00.3042 dated Feb17.2007
I checked the GP / SQL Server and there are 2 drivers:
- SQL Native Client 2005.90.5000.00
- SQL Server 2000.86.3959.00
I assume only install the Native Client on the Citrix and XP computers.
Your version is ok "9.00.0352" means you have installed SP4. I miss typed the version number on my previous comment. You implementation still lacks for some hotfix (for ex. my current version is 9.00.358) but none of them has to do with your problem.
Continue with the next steps..
Sorry for the delay. I work on this system once a week and today is the day.
OK so I checked the version and I do not have the latest version numbers as you have posted.
We are running 9.00.0352 - I will go check for service packs now and see if I can bring it up to a more current version today if they let me reboot.
Don't Fear, there is still hope for GP 9 users
Tony did it work?
I can tell you there was bugs with these security options and GP 9 back in the day. Since GP 9 is not supported I cannot provide information but I would highely recommend you upgrade to a supported version of GP as these bugs are fixed.
1. I Assume your using the last service pack (9.99.0352)
2. Check on SQL (security section) that users has the proper permission/roles
3. Check that your using ODBC connection with SQL Native driver for Microsoft SQL Server 2005
otherwise download it at support.microsoft.com/.../910016 (also check odbc config - 870416 How to setup an ODBC data Source on SQL Server for Microsoft Dynamics GP).
4. Check that the MSSQL public group do have the execute permission on the "smDex_Max_Char store procedure in the master database
4.1 Access SQL Server Management Studio
4.2 Logon as the "sa" user
4.2 Under the server that is running SQL expand databases, expand system databases, expand master, expand programmability, and then expand store procedures.
4.3 On the permission tab click the ADD button under users roles
4.4. In the "Select Users or Roles" window click the browse button
4.5 Click the "Public" check box and then click "OK" two times
4.6 On the permission tab, verify that Public appears under users or roles
4.7 Click to select the Execute/Grant check box, and then click "OK"
5. If your using mandatory profiles together with terminal server, to fix this easily download hotfix 947362
6. If your using Microsoft Small Business Financials, get the SBF 9.0 Logon Hotfix (MIcrosoftSBF90HotFixes)
7. Last Resource (Destroy and Create) equivalent to Microsoft Universal Solution (Ctrl+Alt+Del)
7.-0 Run this script to clean users who didn't log off properly
Delete DYNAMICS..SY00800
Delete DYNAMICS..SY00801
Delete DYNAMICS..ACTIVITY
Delete TEMPDB..DEX_LOCK
Delete TEMPDB..DEX_SESSION
** Everybody must be out of GP **
7.1 Remove user ID from Microsoft Dynamics GP database
7.2 View the problematic users on SQL
select name from master.sys,sql_logins
drop user '<loginID>'
7.3 Recreate users on GP (Tools->setup->System->User
Hope that one these potential solutions may help you fix the problem
Sorry, that did not work.
I started SQL management and used (Security->Login->Properties) to reset the password.
Then i logged in as the user and GP prompted to reset the password.
I typed in a password and it did not accept. I tried a few more and it still did not take those.
I logged into GP as sa and reset the users password.
I then logged in as the user and i could get in.
I went to Tools > User Preferences > Password to reset the password as the user.
It said successful then when i closed out of GP it said it failed. Please use old password next login.
GP does that thing every now and then, in order to solve the situation, do the settings through SQL (Security->Login->Properties) just once, then GP "should" behaves.
Tell me how things came out
Kervin Peguero
Stay up to date on forum activity by subscribing. You can also customize your in-app and email Notification settings across all subscriptions.
#1
André Arnaud de Cal...
291,253
Super User 2024 Season 2
#2
Martin Dráb
230,188
Most Valuable Professional
#3
nmaenpaa
101,156
Share
Report
All responses (
Answers (