7. January 2013 13:24
This is a really niche problem, as its not already out there, worth posting. Whenever a user
tried to void a sales document, the user session would hang. Lock escalation in SQL would then
follow due to the blocking.
If you check in SQL activity, the problem is caused by two sids from the user concerned,
example SQL associated with those sessions is:
select count(*) from IS010001
and SOPTYPE=2 and LNITMSEQ=16384 and CMPNTSEQ=0
The problem in the case I was examining was that the manufacturing module had been installed
but not fully configured, not being used.
Taking the manufacturing module references out of DEX.INI of the client GP folder stopped
15. November 2012 08:00
Found someone had made this mistake, beware when doing something like
where @LOCNCODE is a varchar
The function is defined as:
STR ( float_expression [ , length [ , decimal ] ] )
So the variable is getting converted to a float before it is then turned back into a character data type, problem in my case was that it had worked for years until LOCNCODE one day contained letters as well as numbers.
28. February 2012 15:16
Note to self:
The solution for this appalling BUG in Microsoft IIS & Excel is terrific:
- Create directory "C:\Windows\SysWOW64\config\systemprofile\Desktop " (for 64 bit Windows) or "C:\Windows\System32\config\systemprofile\Desktop " (for 32 bit Windows)
- Set Full control permissions for directory Desktop (for example in Win7 & IIS 7 & DefaultAppPool set permissions for user
20. November 2011 16:14
eConnect WCF exception handling
For this example a WCF service reference to the server endpoint running the GP2010 eConnect integration service as a reference named “GPeConnect” is used.
If an exception were to occur from eConnect on say the CreateEnity mehods, and the exception examined as type system.exception, then the following message is found from ex.message,
System.ServiceModel.FaultException: The creator of this fault did not specify a Reason
To retrieve the error message from econnect that we are interested in, use the System.ServiceModel.FaultException class as shown below. By accessing the Detail.Message property, it is possible to get message of interest.