Sybase ODBC errror: Triggers and Procedures not supported in runtime server

Hi I hope someone has seen this before:

We are using a tried and tested application which works on a number of operating systems including XP.  The application is VB6 with a Sybase Adaptive Server Anywhere version 6.0.3 backend database which can reside locally or the db can run on a server as a server.  In this case it is has the database locally.  At first I noticed that the XP was Professional version with automatic updates switched on a XP SP2 loaded.  Therefore I thought this might be the problem.  However when I switched off the XP Firewall and uninstalled SP2 the problem persists.  The error is Sybase ODBC errror: Triggers and Procedures not supported in runtime server.  Can someone please help?

Thanks

Dave
LVL 4
barnesd1Asked:
Who is Participating?
 
CetusMODConnect With a Mentor Commented:
Closed, 500 points refunded.
CetusMOD
Community Support Moderator
0
 
leonstrykerCommented:
From ASA Error Messages:

http://sybooks.sybase.com/onlinebooks/group-sas/awg0800e/dberen8/@Generic__BookTextView/42413

You attempted to call a stored procedure or have modified a row in a table on which a trigger is defined and you are using the runtime server. Triggers and stored procedures are not supported in the runtime server. You must be running the full server to use these features.

Leon
0
 
barnesd1Author Commented:
Leon

Yes I found this message on the internet as well.  It doesn't explain why every other installation of the same product works fine.  I need to find out if there is a cause for this error to occur because of a bad installation, clash with some other product or service pack, etc.  It is not a code issue.
0
Cloud Class® Course: Microsoft Exchange Server

The MCTS: Microsoft Exchange Server 2010 certification validates your skills in supporting the maintenance and administration of the Exchange servers in an enterprise environment. Learn everything you need to know with this course.

 
leonstrykerCommented:
Are you saying that you have a local ASA db instal on a different operating system and it is working?

Leon
0
 
barnesd1Author Commented:
Yes it is local.  Also other installs are working fine on NT4, 2000, 98 and XP.
0
 
leonstrykerCommented:
Is it a particular procedure(s) which is not working or no database calls can be made?  At what point are you getting an error?

Leon
0
 
barnesd1Author Commented:
I appears to be failing when it is calling a stored procedure.  I am remote to this installation so its not easy to investigate.  Could security patches be causing this I wonder?
0
 
leonstrykerCommented:
According to everything I know it is running the way it should.  In order to get this to run the way you want it to run you would need to instal the ASA as a server on the local machine.

Leon
0
 
ChrisKingCommented:
I am aware that Sybase has an ASA database called "Ultralite" which is NOT the ull blown ASA.
Ultralite does not support triggers / procedures

Are you sure someone didn't install Ultralite by mistake ?
0
 
ChrisKingCommented:
Another thought:

Microsoft also have a "free" lightweight database (can't think what it is called) that might have been auto installed and could be interfering somehow.
It also does not support triggers / procedures
0
 
leonstrykerCommented:
Microsoft has a free database called MSDE and it does support store procedures.

http://www.microsoft.com/sql/msde/default.asp

The only time I heard of SQL Server interfering with Sybase was then both clients were installed on the same machine and that was for SQL Server 6.5 vs. Sybase 11 and the problem was that an application was trying to use the DB library instead of the CT library.

Leon
0
 
ChrisKingCommented:
no, not the MSDE (it does support procs/triggers), I am talking about a "lightweight database", can even be installed on WinCE devices
0
 
leonstrykerCommented:
There are versions of Access and SQL Server which can be installed on WinCE, but I never heard of these being installed on anything else but WinCE.

Leon
0
 
ChrisKingCommented:
doesn't matter, we are getting a bit off the track now.

barnesd1
can you post the output of SELECT @@version
0
 
barnesd1Author Commented:
@@version = 6.0.3.2747
0
 
barnesd1Author Commented:
The solution to this was actually a simple conflict.  The customer was running Ghost and this was causing this unlikely error message.
0
 
ChrisKingCommented:
well done for tracking that one down!
0
 
leonstrykerCommented:
I guess this is the time to close the question.  Please select one, or more, of the posted responses as an answer, if you feel that we were helpful, or place a request in the Community Support area asking for a refund if you believe you answered this question by yourself.

Leon
0
 
ChrisKingCommented:
I do believe that barnesd1 did indeed answer this one theirself
0
 
leonstrykerCommented:
No objections,

Leon
0
 
suryadipCommented:
Hello Dave,

I have the answer with me regarding your issue.

The reason you are getting the above error is because you are using the runtime standalone server.

So if you search the directory in which this standalone sybase is installed you will find rteng*.exe which is runtime engine and which doesnt support Stored Procedures And Triggers.

Instead you need to install dbeng*.exe file which contains the database engine which can process the Stored procedure and Triggers. Again writing the Stored procedure in ASA and ASE is slightly different. so you may have to resolve those issues as well.

Hope this solves the above problem. Please note that it is not an Operating System Issue.

--- Suryadip
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.