From: Jeff J. - S. <J_...@MC...> - 2008-03-26 17:04:10
|
Well, after banging my head against this problem for two days, I finally figured out that the context file I had created was incomplete. I had: isql_path=C:/Program Files/Firebird/Firebird_1_5/bin/ I figured this was correct because this is the "path" to the isql.exe file. What I did not realize until I read the instructions more closely was that this parameter specifies not only the path but also the filename. So, when I changed it to: isql_path=C:/Program Files/Firebird/Firebird_1_5/bin/isql.exe it started working better. Hurrah! However, I now have a different problem (I am your problem child, after all!) When trying to run one of the tests that came with the testsuite, or running a simple test of my own, I get the following output in qmEditor: --- TEST RESULTS ------------------------------------------------------------- functional.database.create.create_database_29 : FAIL Expected error output from ISQL does not match actual error output. FirebirdTest.ISQL_stderr_actual: Statement failed, SQLCODE = -924 bad parameters on attach or create database Use CONNECT or CREATE DATABASE to specify a database Use CONNECT or CREATE DATABASE to specify a database FirebirdTest.ISQL_stderr_actual_stripped: Statement failed, SQLCODE = -924 bad parameters on attach or create database Use CONNECT or CREATE DATABASE to specify a database Use CONNECT or CREATE DATABASE to specify a database FirebirdTest.ISQL_stderr_expected: FirebirdTest.ISQL_stderr_expected_stripped: FirebirdTest.ISQL_stderr_stripped_diff: + Statement failed, SQLCODE = -924 + bad parameters on attach or create database + Use CONNECT or CREATE DATABASE to specify a database + Use CONNECT or CREATE DATABASE to specify a database qmtest.end_time: 2008-03-26T16:57:16Z qmtest.start_time: 2008-03-26T16:57:16Z qmtest.target: local --- TESTS THAT DID NOT PASS -------------------------------------------------- functional.database.create.create_database_29 : FAIL Expected error output from ISQL does not match actual error output. --- STATISTICS --------------------------------------------------------------- 1 tests total 1 (100%) tests FAIL It does not appear to be connecting to the database, even though the command entered as the Python/SQL Code appears to be correct, and works when running isql from a command window. I have probably forgotten some simple thing in the setup, but I can't figure it out. Any ideas? Thanks! Jeff -----Original Message----- From: fir...@li... [mailto:fir...@li...] On Behalf Of Pavel Cisar Sent: Thursday, March 20, 2008 10:16 AM To: fir...@li... Subject: Re: [Firebird-test] Exception when running test Jeff Jones - SHERIFFX napsal(a): > Okay, I tried one of the tests that comes with the test suite, and it > also fails. Here is the output from qmtest: Same problem here. > I am not sure what you mean by checking the access rights for isql. How > would I do that? What would I look for? QMTest can't spawn new process (ISQL in this case) because Windows doesn't allow him to. It could be either because QMTest itself is restricted to spawn processes at all or can't execute ISQL due to insufficient OS rights. Maybe your have installed Firebird under Administrator account but run Python (QMTest) under your user account that has restricted access to FB installation? I never encountered such problem under XP workstation, but if you're on Vista or W2003 Server, it could be different thanks to UAC and its generally tightened security? If you can execute isql manually, then the problem is in OS rights tied to QMTest (resp. Python). You may try to assign Python executable to some more powerful user groups (or system ones). best regards Pavel Cisar ------------------------------------------------------------------------ - This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/ _______________________________________________ Firebird-test mailing list Fir...@li... https://lists.sourceforge.net/lists/listinfo/firebird-test |