For those who love Excel and Great Plains, here's a quick (5 minutes) video intro on how to do Excel Based Budgeting in Great Plains.
Thanks Dynamic Shepra and the guys at DynamicAccounting.net!
Here's their website, chock full of other GP video how to goodness!
When attempting to install GP 10 SP1 on a PC with NET 2.0 SP1, I got an error like so:
"Product: Dexterity Shared Components -- .NET Framework 2.0 is not installed. The installation cannot continue"
Well, come to find out, the GP 10 installer checks for .NET 2.0 but has an issue if you have .NET SP 1 installed.
The work around is to uninstall .NET 2.0 SP1 (and in my case, .NET 3.0 as well) and then my install got past this particular error.
If you don't have the luxury of uninstalling .NET 2.0 SP 1 (as most people don't), you can try this fix from MS:
Good luck and let me know how you make out!
Here's some of the crazy stuff I had to do:
1) Go into the bowels of my DCOM security setup and open everything up (more details to come).
2) Run msdtc -install / hack the registry / run msdtc -reinstall.
3) Create some funky looking user in my SQL db so that trusted authentication would work for connecting to the distributor.
4) Enable MSDTC on my servers (since its disabled by default!), which involves doing an install of the MSDTC windows component (makes me wonder why they didn't just call in installing MSDTC versus "enabling" it?)
5) Had to create a linked server specifically named with my Server Name
6) Had to go into Windows Firewall and add port 135 and the MSDTC program as exceptions, even though Windows Firewall wasn't running!
7) Used tool DTCPing to tell me I wasn't crazy. But it reported everything was successfull, even though I couldn't get a distributed transaction to run, so I am crazy! :-)
Whew. OK. This is just a first post to vent my frustrations with setting up replication. I promise to come back and tidy this up with more details, screen shots, and KB links!
Great way to check out FRx using a hosted virtual lab! Nothing to install, runs in your browser, and comes with a nice little Hands On Lab type walk through.
Check it out!
(UPDATE: The labs moved! Here they are: http://msfrx-vdms.demoservers.com/VDMS)
"Operation must use an updateable query"
I love these kind of error messages, because they're just so darn recognizable. (I'm not kidding, really, its quite sad when you can recognize error messages, like, "Hey, there's Larry!")
I instantly recognized this to be an Access database error that occurs usually for one of two reasons (actually its the same reason, the database cannot be written to, but there's two different causes).
The first cause is if the Access .mdb file has been marked with the readonly attribute. This can happen when you copy it from a CD or if you inadvertly had it selected when you selected another file and marked it for read only.
The second cause (and more common, I think) is if you don't have permissions to write to the database, which was the case for MES.
Which Access database file am I referring to? The IM.mdb file that Integration Manager uses to store its integration definitions.
So, if you get this error when trying to run an integration, make sure that the user who you are logged in as when trying to run the integration has permissions to write to the IM.mdb file!
If that aint it, make sure the file hasn't been marked read only.
I happen to have had this same issue and using my trusty SQL Profiler, I found that when I manually uncheck Outlook from my home page, GP ran a SQL statement like the following :
SET Visible = 0
WHERE COLNUMBR = 1
AND SEQNUMBR = 3
AND Visible = 1
AND USERID = 'dpatrick' -- comment this if you want to do it for all users
AND SectionID = 2
This works great, but it doesn't actually stop any particular user re-checking Outlook on the home page (but it got me what I wanted, which is to default Outlook to being off for everyone).
Dave Musgrave, from Microsoft, later chimed in and gave us this link:
which discusses how to actually disable Outlook from the homepage (and uses a script that looks pretty close to the one I use).
Thanks Dave and thanks 2020 for asking the question!
Neil Jordan shot me an email about one of my recent posts and mentioned that it would be nice to have a central place to discuss GP Developer related issues.
I agreed that it would be nice to have a central depot for sharing GP developer information.
The challenge I find is that there already are several "central" places to share info, and the fact that there are several of them kind of takes away from any of one of them being the "central" one!
That said, here's my short list of GP dev resources:
Great Plains Microsoft Public Newsgroups
There's two newsgroups here, Microsoft Dynamics GP and Microsoft Dynamics GP Developer, make sure to check both.
Log in required, but worth signing up if you're a GP customer
Lots of good stuff, access to the Knowledge Base is probably what I use most
You mean you're not a partner? Why not become one!
Lots of good resources here for partners.
Great Plains User Group
Not free, but host web based meetings, so you can join from anywhere
Free to read, costs money to ask your own questions, but could be well worth it!
One of only a few GP Developer blogs that I know of
Lots of free GP SQL scripts
Micosoft Dynamics Forums
A non-MS newsgroup dedicated to Dynamics
Tech Round Up
A friend of mine's (and GP MVP) GP dev blog. Hasn't been updated in a while, but still lots of good stuff!
Great Plains Guy
If I had to pick one to be the grand daddy central place, it'd have to be the GP newsgroups (but there really are 2 of them that I check, so I guess I still can't pick just one, ack!).
The nice thing about the newsgroups is that they are read and answered by MS folks and (even better) by MVPs. So, it's not a bad place to voice your concerns, share your issues, and sometimes even help your fellow GP dev guy out.
Do you have any resources to add to my list? Maybe we need a central list of GP dev resources? Maybe a wiki or something?
What do you think?
That pops up the Table Descriptions window. From there you can click the elispes to select a table.
I don't know my company ID! I know the name, and I guess I can guess that my company ID might be 1, since the default company record that the FRxForecaster install has listed has a company ID that is zero (and 1 comes after zero, as my son might tell me).
But I need to know for sure...so I am off to try out my google fu....
Minutes later (because that's all I have the patience for)...NOTHING.
Ah well, so, I remember from one of my many GP upgrades that I had some script somewhere that told me what companies I had installed and what was their various state of upgradiness. I also remember distinctly that the script showed me what my company ID was (I also remember seeing one company ID listed as somthing like -32676, which was weird. I think it might have been TWO).
So, I go digging through my scripts archive ('cause you know I keep them all, hey, drive space is cheap!) and voila!, here it is:
SELECT b.fileOSName, a.Status, a.errornum, c.INTERID
FROM DYNAMICS.dbo.DU000030 a
JOIN DYNAMICS.dbo.DU000010 b ON a.fileNumber = b.fileNumber
JOIN DYNAMICS.dbo.SY01500 c ON a.companyID = c.CMPANYID
WHERE a.Status <> 0 or a.errornum <> 0
From this script I gather that the SY01500 table is the one holding my company info (and ID!). Sure enough, the following gives me my answer:
which is, in my case, (ready for it?):
I know, I know, kind of anti-climatic, but whatcha gonna do.
Until next time...
If you ever get "locked" out of the system, i.e. something crashes and then you cannot log back in, this little piece of SQL will kick everyone off ( or,more specifically, it will delete everyone's login from the activity table):
DELETE FROM DYNAMICS.dbo.ACTIVITY
In Great Plains 7.5 and below, this was a life saver. You could also do individual users like so:
DELETE FROM DYNAMICS.dbo.ACTIVITY WHERE userid='username'
In Great Plains 9 and above, they now have a nice window that pops up that lets you delete yourself, if you happen to already be logged in, so the theory is that this script is no longer necessary.
That assumes that that little window will still pop up after a crash. And sometimes, after a crash, all bets are off, so I still keep this little guy handy, just in case...
- ► 2009 (27)
- ► March (6)