Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

"Exception Access Violation" error message when opening IM

4 posts in PB Infomaker Report Writer Last posting was on 1999-05-27 14:48:39.0Z
Rick Marden Posted on 1999-05-26 15:13:30.0Z
Newsgroups: sybase.public.infomaker.general
Reply-To: "Rick Marden" <rmarden@primavera.com>
From: "Rick Marden" <rmarden@primavera.com>
Subject: "Exception Access Violation" error message when opening IM
Date: Wed, 26 May 1999 11:13:30 -0400
Lines: 19
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Message-ID: <348_NdBTWn4p#GA.206@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.infomaker.general:6286
Article PK: 241272

We have a customer getting this error attempting to open IM 5.0.03 on NT
4.0. It appears to connect to the DB successfully before the error occurs.
The error results in closing IM. Our application (a PB app) opens fine
connecting to the same DB that IM connects to.

We have checked their IM.INI file and all appears correct. We have deleted
the values after "DefLib=" and "WorkingDir=" which in the past has solved
this problem for us in the past where the user did not have access to the
default PBL that IM was attempting to open. This method did not work in
this case.

I searched the solved cases and could find a related problem.

Has anyone seen this? Any suggestions?

Rick Marden
Primavera Systems, Inc.


Terry Dykstra Posted on 1999-05-26 17:09:51.0Z
Newsgroups: sybase.public.infomaker.general
From: "Terry Dykstra" <tdykstra@cfol.ab.ca>
Subject: Re: "Exception Access Violation" error message when opening IM
Date: Wed, 26 May 1999 11:09:51 -0600
Lines: 27
X-Newsreader: Microsoft Outlook Express 4.72.3110.5
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Message-ID: <348_uxyXnn5p#GA.205@forums.sybase.com>
References: <348_NdBTWn4p#GA.206@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.infomaker.general:6285
Article PK: 241271

Can you give the exact memory address? What DB?

--
Terry Dykstra (TeamSybase)
Canadian Forest Oil Ltd.

Rick Marden wrote in message ...
>We have a customer getting this error attempting to open IM 5.0.03 on NT
>4.0. It appears to connect to the DB successfully before the error occurs.
>The error results in closing IM. Our application (a PB app) opens fine
>connecting to the same DB that IM connects to.
>
>We have checked their IM.INI file and all appears correct. We have deleted
>the values after "DefLib=" and "WorkingDir=" which in the past has solved
>this problem for us in the past where the user did not have access to the
>default PBL that IM was attempting to open. This method did not work in
>this case.
>
>I searched the solved cases and could find a related problem.
>
>Has anyone seen this? Any suggestions?
>
>Rick Marden
>Primavera Systems, Inc.
>
>


Rick Marden Posted on 1999-05-26 17:54:10.0Z
Newsgroups: sybase.public.infomaker.general
Reply-To: "Rick Marden" <rmarden@primavera.com>
From: "Rick Marden" <rmarden@primavera.com>
Subject: Re: "Exception Access Violation" error message when opening IM
Date: Wed, 26 May 1999 13:54:10 -0400
Lines: 44
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 5.00.2314.1300
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Message-ID: <348_vY$$MB6p#GA.51@forums.sybase.com>
References: <348_NdBTWn4p#GA.206@forums.sybase.com> <348_uxyXnn5p#GA.205@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.infomaker.general:6284
Article PK: 241270

Actually, there have been some more developments since my first post. The
customer removed and reinstalled our application, which also performs an
install of IM. Now upon starting IM, the IM workspace appears and briefly
says "Connecting to Database" at the bottom and then disappears with no
error message. Again, everything in the IM.INI appears to be correct.

The DB I spoke of is an SQLA 5.5.03 database customized for our application.
The database does not appear to be the problem as it can be started by
running dbeng50 <the db> or can be connected to via ODBC from our
application.

Terry Dykstra <tdykstra@cfol.ab.ca> wrote in message
news:uxyXnn5p#GA.205@forums.sybase.com...
> Can you give the exact memory address? What DB?
>
> --
> Terry Dykstra (TeamSybase)
> Canadian Forest Oil Ltd.
> Rick Marden wrote in message ...
> >We have a customer getting this error attempting to open IM 5.0.03 on NT
> >4.0. It appears to connect to the DB successfully before the error
occurs.
> >The error results in closing IM. Our application (a PB app) opens fine
> >connecting to the same DB that IM connects to.
> >
> >We have checked their IM.INI file and all appears correct. We have
deleted
> >the values after "DefLib=" and "WorkingDir=" which in the past has solved
> >this problem for us in the past where the user did not have access to the
> >default PBL that IM was attempting to open. This method did not work in
> >this case.
> >
> >I searched the solved cases and could find a related problem.
> >
> >Has anyone seen this? Any suggestions?
> >
> >Rick Marden
> >Primavera Systems, Inc.
> >
> >
>
>


Terry Dykstra Posted on 1999-05-27 14:48:39.0Z
Newsgroups: sybase.public.infomaker.general
From: "Terry Dykstra" <tdykstra@cfol.ab.ca>
Subject: Re: "Exception Access Violation" error message when opening IM
Date: Thu, 27 May 1999 08:48:39 -0600
Lines: 56
X-Newsreader: Microsoft Outlook Express 4.72.3110.5
X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3
Message-ID: <348_2IZAV9Eq#GA.205@forums.sybase.com>
References: <348_NdBTWn4p#GA.206@forums.sybase.com> <348_uxyXnn5p#GA.205@forums.sybase.com> <348_vY$$MB6p#GA.51@forums.sybase.com>
Path: forums-1-dub!forums-1-dub!forums-master.sybase.com!forums.sybase.com
Xref: forums-1-dub sybase.public.infomaker.general:6277
Article PK: 241264

Check the im.ini [database] section that it is indeed connecting to your DB,
and not the default demo database. Is the app path set correctly for IM?

--
Terry Dykstra (TeamSybase)
Canadian Forest Oil Ltd.

Rick Marden wrote in message ...
>Actually, there have been some more developments since my first post. The
>customer removed and reinstalled our application, which also performs an
>install of IM. Now upon starting IM, the IM workspace appears and briefly
>says "Connecting to Database" at the bottom and then disappears with no
>error message. Again, everything in the IM.INI appears to be correct.
>
>The DB I spoke of is an SQLA 5.5.03 database customized for our
application.
>The database does not appear to be the problem as it can be started by
>running dbeng50 <the db> or can be connected to via ODBC from our
>application.
>
>Terry Dykstra <tdykstra@cfol.ab.ca> wrote in message
>news:uxyXnn5p#GA.205@forums.sybase.com...
>> Can you give the exact memory address? What DB?
>>
>> --
>> Terry Dykstra (TeamSybase)
>> Canadian Forest Oil Ltd.
>> Rick Marden wrote in message ...
>> >We have a customer getting this error attempting to open IM 5.0.03 on NT
>> >4.0. It appears to connect to the DB successfully before the error
>occurs.
>> >The error results in closing IM. Our application (a PB app) opens fine
>> >connecting to the same DB that IM connects to.
>> >
>> >We have checked their IM.INI file and all appears correct. We have
>deleted
>> >the values after "DefLib=" and "WorkingDir=" which in the past has
solved
>> >this problem for us in the past where the user did not have access to
the
>> >default PBL that IM was attempting to open. This method did not work in
>> >this case.
>> >
>> >I searched the solved cases and could find a related problem.
>> >
>> >Has anyone seen this? Any suggestions?
>> >
>> >Rick Marden
>> >Primavera Systems, Inc.
>> >
>> >
>>
>>
>
>