Key Generation Failed Sql State S1000 In Sqlexecdirect Informix 12

16.12.2020
Key Generation Failed Sql State S1000 In Sqlexecdirect Informix 12 Rating: 8,9/10 9753 reviews

Not endorsed by or affiliated with SAP

Register Login

Want to sponsor BOB? (Opens a new window)

Index About

Sponsors Contact Us Calendar FAQ Rules and Guidelines Privacy Policy Search

General Notice: BOB is going to retire.please see details here.
General Notice: No events within the next 45 days.

Key Generation Failed Sql State S1000 In Sqlexecdirect Informix 12 10

SQL Generation Failed. WIS 00013.

Search this topic. Search XI Server Discussion. Search Box

Key Generation Failed Sql State S1000 In Sqlexecdirect Informix 12 10

Foundry license utility download mac. When the SQLATTRODBCVERSION environment attribute is set to SQLOVODBC2, the driver posts ODBC 2.x SQLSTATEs instead of ODBC 3.x SQLSTATEs when SQLGetDiagField or SQLGetDiagRec is called. A specific mapping can be determined by noting the ODBC 2.x SQLSTATE in column 1 of the following table that corresponds to the ODBC 3.x SQLSTATE in column 2. SQLExecDirect failed with ODBC Error: state=23000, nativeErr=547, err=MicrosoftSQL Server Native Client 10.0SQL ServerThe INSERT statement conflicted with the FOREIGN KEY constraint 'FKStatDataStatID0F975522'. The conflict occurred in database 'poweradmin', table 'dbo.Statistic', column 'StatID'.

Register or Login to Post Forum Index ->Server Administration, Installation, Upgrades ->XI Server Discussion
AuthorMessage
chopwood
Forum Member
Joined: 15 Jun 2007
Posts: 1

Posted: Mon Sep 08, 2008 12:32 pm
Post subject: SQL Generation Failed. WIS 00013.
I have seen some descriptions of this issue on the forums but none ever got so far as to answer my issue.
I'm getting the error message listed in the Subject line: SQL Generation Failed. WIS 00013.
I have tried setting the Connection Time Out in the CMC. While I have that setting in the CMC set to 45 minutes, WebI times out in 15 minutes with this error, when the report is left idle. Is this the correct setting?
Back to top
Bomada
Senior Member
Joined: 25 Jun 2008
Posts: 42
Location: Norway

Posted: Fri Nov 07, 2008 6:08 am
Post subject: Re: SQL Generation Failed. WIS 00013.
Hi chopwood,
you could try the following:
- Log on to the BO server.
- Open the folder <install directory>Program FilesBusiness ObjectsTomcatconf.
- Open the server.xml file (save a copy of the original file before doing any changes).
- Find the tag with the following comment:
<!-- Define a non-SSL Coyote HTTP/1.1 Connector on port 8080 -->
- Change connectionTimeout='20000' to connectionTimeout='-1'.
- Save and close the file.
- Open Central Configuration Manager (startAll ProgramsBusiness ObjectsBusiness Objects Crystal DecisionsCentral Configuration Manager).
- Restart the Apache Tomcat server.
Back to top
gajulas
Forum Member
Joined: 07 Jul 2009
Posts: 2

Posted: Tue Jul 07, 2009 1:52 pm
Post subject: Re: SQL Generation Failed. WIS 00013.
chopwood - Please let me know if the changes in serve.xml resolved the issue - we are also having same issues. - Thanks
Back to top
gary_scott
Principal Member
Joined: 17 Dec 2004
Posts: 151
Location: Gloucestershire, England

Posted: Tue May 18, 2010 3:32 am
Post subject: Re: SQL Generation Failed. WIS 00013.
Solution can be found here :-
http://www.forumtopics.com/busobj/viewtopic.php?t=69793&postdays=0&postorder=asc&highlight=wis+00013&start=15
Cheers,
Gary
Back to top
Register or Login to Post Forum Index ->Server Administration, Installation, Upgrades ->XI Server Discussion
Page 1 of 1All times are GMT - 5 Hours

Index About FAQ RAG Privacy Search Register Login

Get community updates via Twitter: /windows-7-enterprise-64-bit-key-generator.html.

  • Jun 21, 2017  If you are using surrogate keys or primary keys in the SQL tables that are set to auto increment, you may notice this issue in production. MS SQL Server, when restarted, auto increments those values by 1000. So if a ID column value was 10112 the next record that gets added after restart will get ID value 11112. Here is a thread on this issue.
  • Although positioned updates do not apply to all types of applications, try to use positioned updates and deletes whenever possible. Positioned updates (with UPDATE WHERE CURRENT OF CURSOR) allow you to update data by positioning the database cursor to the row to be changed and signaling the driver to change the data.
  • I checked the credentials. I am able to login into the sql server by those credentials but not not able to make odbc connection and SQL aunthenticated mode is enabled for the sql server. FYI- There are two servers in picture, one from which i am trying to make odbc connection and another one where sql server is installed.
Not endorsed by or affiliated with SAP
Powered by phpBB © phpBB Group
Generated in 0.0271 seconds using 17 queries. (SQL 0.0023 Parse 0.0008 Other 0.0239)
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.103 Safari/537.36
Hosted by ForumTopics.com Terms of Service
phpBB Customizations by the phpBBDoctor.com
Shameless plug for MomentsOfLight.com