SQL Server Error : Work Space Limit Exceeded (PTF3)

General discussion forum about all databases other than SqlBase.
Adrian Whittell
Great Britain
Posts: 80
Joined: 04 Dec 2018, 14:47
Location: Norwich, England

SQL Server Error : Work Space Limit Exceeded (PTF3)

Post by Adrian Whittell » 17 May 2011, 12:30

CTD 52 PTF3
Win 7 and XP
All versions of SQL Server

We started getting this error when running some of our Stored Procedures using all versions of SQL Server when EMP5319 was introduced.
To fix the error we have to go back to EMP5309.
We waited for PTF3 where it was scheduled to be fixed but we still get the error making our apps unusable with PTF3.
I have notified UNIFY who have run my test app and UNIFY don't get the error in SQL Server 2005.
I have attached a test app here to see if anyone else gets this error.
I have also included the offending sql dll (sqlodb32.dll)
The SP needs to be created in your DB.
Note the SP has no SQL apre from one declare statement.
The error is with declaration of the parameters. If I remove the params it works.
There is an ini file called TEST.INI. In there enter your DB ODBC source and user/pw.
There is simply a call to the SP in the SAM_CreateComplete of the form.
We have tested on:-
SQL 2000
SQL 2005
SQL 2008
SQL 2008 Express
It falls over in all those versions.
Any assistance would be much appreciated
Adrian
Tribal
You do not have the required permissions to view the files attached to this post.

Adrian Whittell
Great Britain
Posts: 80
Joined: 04 Dec 2018, 14:47
Location: Norwich, England

Re: SQL Server Error : Work Space Limit Exceeded (PTF3)

Post by Adrian Whittell » 24 May 2011, 15:23

This issue is critical for us.
We were hoping to find at least one other user who uses SQL Server and 5.2.
If it affects us, it could potentially affect all users.
It's a bit of a stalemate in that UNIFY support can't replicate the issue - hence cannot send the issue to development to be fixed.
So we'd really love to hear even if others can/cannot replicate with the test app supplied - It qwould take no more than 5 mins to download and test.
All our apps fall over on all versions of SQL Server in both Win 7 and XP

And just to re-iterate as soon as we replace sqlodb32.dll in PTF3 with the one from EMP3109 the issue is solved.
So we know it occurred between EMP5309 and EMP5319.
But this issue has both us and UNIFY stumped.
And we cannot deploy our apps with CTF3 with this issue.
So we must resolve it somehow.

The only other bit of info missing is from SQL.INI
We use this setting:-
[win32client.dll]
comdll=sqlodb32

So if anyone does have SQL Server then it would help a great deal if you could say whether this issue is reproducable.

Adrian
Tribal

David Johnston
Great Britain
Posts: 20
Joined: 06 Feb 2018, 21:03
Location: Basingstoke, UK

Re: SQL Server Error : Work Space Limit Exceeded (PTF3)

Post by David Johnston » 24 May 2011, 18:17

Adrian.
We support library software written in TD with SQL Server as the back end. We have found that we have to experiment with different versions of sqlodb32.dll and the settings in the [odbcrtr] section. We tend to revert to older versions of sqlodb32.dll in these situations.

What does your [odbcrtr] section in the sql.ini look like?
Are these 64 bit or 32 bit machines? We had problems with some 64 bit architectures.
What version of MDAC is loaded?

I do not have a solution to your problem, but I suspect that Unify staff need to know the above, because these really seem to make a difference.

We do have issues with dates with Microsoft SQL Server 2008 having date formats DATETIME and DATETIME2. But these issues are not peculiar to TD; we have found it very difficult to use the Microsoft SQL Server OLEDB client from Microsoft Visual Studio. Apparently the solution to the date problem is to avoid using the OLEDB drivers, but we have found that the old SQL Server OLEDB drivers for SQL Server 2005 work fine with SQL Server 2008 and we do not need DATETIME2 anyway.

Adrian Whittell
Great Britain
Posts: 80
Joined: 04 Dec 2018, 14:47
Location: Norwich, England

Re: SQL Server Error : Work Space Limit Exceeded (PTF3)

Post by Adrian Whittell » 25 May 2011, 12:29

We can't really go back to an older version of the dll.
There was a critical issue fixed recently where in SQL Server 2008, the milliseconds of a datetime value were truncated by the odbc router and caused us all sorts of problems.
That is now fixed in PTF 3.

All we have in [odbcrtr] is a pointer to a File DSN
In the file DSN we have:-
[ODBC]
DRIVER=SQL Server
Trusted_Connection=yes
AutoTranslate=No
DATABASE=IDR_EDEM
APP=IDR_Client_20113103145810
SERVER=AW07-nr
WSID=AW07-NR

But in the test app we just set the user/sa and db manually from an ini file.
So it will just use the ODBC source specified.

Issue is with 32 and 64 bit machines
MDAC is 2.81.1132.0

We don't use Datetime2. We don't need that level of precision.

just out of interest, did you try and download test app to see if it fell over with same error using latest sqlodb32.dll from PTF3?

Adrian Whittell
Great Britain
Posts: 80
Joined: 04 Dec 2018, 14:47
Location: Norwich, England

Re: SQL Server Error : Work Space Limit Exceeded (PTF3)

Post by Adrian Whittell » 26 Jul 2011, 15:39

Another UNIFY support engineer has had a look at this and has reproduced the issue immediately with my test app.
The issue has been logged.
So this error does effect all users using SQL Server 2005 and 2008.
I think the engineer who originally tested this issue was using SQL Server 2000 which we do not support.
Thanks
Adrian

Return to “General Discussion”

Who is online

Users browsing this forum: [Ccbot] and 0 guests