November 24, 2008 at 5:28 am
am facing a trubles when testing GP10 with Database mirroring.
details:
1- i have configured database mirroring for DYNMAICS and TWO database and its working fine from the database side.
2- on the client machine i have installed GP10, create an ODBC for the Princible database.
3- then run GP working fine (connected to the princible database), but when a failover happens the GP cannot connect to the Mirrored database.
any suggestions??
..>>..
MobashA
November 24, 2008 at 8:15 am
What is GP10?
What client are you using to connect? If you are not using the SNAC client, which comes with SS2KL5 and later, it will not automatically connect. The previous ADO/OLEDB/ODBC clients do not understand mirroring.
You can use a friendly name on your network, like an FQDN in DNS and let everyone connect there. When things fail, you can move that to the new IP, though clients would need to flush their DNS or wait for a timeout. Alternatively, you can publish instructions for them to move their connection to the mirror.
November 24, 2008 at 9:06 am
Your too quick Steve, was just gonna say that. Though prob not so eliquently :s
Adam Zacks-------------------------------------------Be Nice, Or Leave
November 24, 2008 at 9:12 am
Microsoft Dynamics GP 10.0.
u mean that i have to upgrade for SP2?
what dose SS2KL5 stands for?
..>>..
MobashA
November 25, 2008 at 8:57 am
Ahhh, the joy's of GP. :crying: This is NOT a normal SQL Server situation due to the way the application was written, it's extremely application specific.
Unless something drastic has changed, which hasn't happened since version 6, this should get you most of the way there. Note that there hasn't been much change in the system from a database stand point since they delivered their first version for SQL on MS SQL 6.0.
You are probably having difficulty with the user accounts on the new server. GP creates the SQL user accounts and grunges the passwords so they are only valid when used with the application. All except for sa. If these accounts, passwords and the user sid's don't match up you have a problem where you lose all the application access and security that has been setup. That really pleases the accounting department.
There are a few articles on CustomerSource(GP version of Technet) that can point you in the right direction, you need to handle this as a server move. They have a method documented to import the SQL user accounts into the Dyanmics database and create SQL users on the new server. I no longer have access to it so I can't help you navigate their joyous site. It's a fairly nice process, but the scripts need working on to be able to automate the addition of new users and mirroring.
Another option is to transferred the accounts from the Principle server outside of GP, you will need to do this so that the users are able to be authenticated, How to transfer logins and passwords between instances of SQL Server.
The other thing that is most critical, the databases MUST be owned by the DYNSA account, all of the GP databases must be owned by this account.
This should complete the circle and get you moving ahead.
November 25, 2008 at 9:15 am
Lee,
GP still won't switch automatically to the mirror, correct?
If you move the logins, use sp_help_revlogin from MS to script out the logins with the correct SID and passwords.
Not sure about GP, but we used to be able to add logins via SSMS/EM and then "match up" with new users added by Dynamics in the db.
November 25, 2008 at 10:19 am
thanks alot for this but the mean problem that GP still won't switch automatically to the mirror,
how can i made this happen??
the logins is another issue but if the GP cant make an automatic fail over then i have nothing to worry about.;)
..>>..
MobashA
November 25, 2008 at 4:32 pm
GP will not automatically switch to the backup server, it's not supported in the software. The technology used in GP doesn't have the intelligence to perform that function, the base code was written long before failover was an option and since they are working on the Next Gen product Fargo isn't going to invest the time or money to add that functionality. :crying:
The only option to make the switch is to close the app and without a connection to the Dynamics and Company database it will close hard. Then start the app and use the new DSN. Sometimes the workstation will require a reboot for the app to start again.
I have seen GP work better in a cluster, but if something like posting is going on during the failover there may be some maintenance to clean up the data.
November 25, 2008 at 11:37 pm
that nice and it make sence, but what i have found at microsoft site a single line tells u that GP support Mirroring but never explain who???
we can agree this is not right..
..>>..
MobashA
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply