There was an unexpected error running sql scripts setup will now terminate

SQL Server: Fix Msg 8630, Level 16, State 1, Line 1 – Internal Query Processor Error: The query processor encountered an unexpected error during execution (HRESULT = 0x80040e19).

This is going to be a quick reference for people encountering this error and to do the fix more than a blog post but I do show a small trick on how to do an UPDATE in chunks 😉

The Error:

I ran into this error with

• (Microsoft SQL Server 2012 (SP4-GDR) (KB4057116) – 11.0.7462.6 (X64) Jan 5 2018 22:11:56 Copyright (c) Microsoft Corporation Standard Edition (64-bit) on Windows NT 6.2 (Build 9200: ) (Hypervisor)

When you run a query such as below:

It produced an obscure error

The problem – Memory pressure?

Initial Google search indicated that it was due to memory pressure and a fix is needed via a Service Pack (for the older versions of SQL Server).

Thinking it was trying to do too much at once, I broke the UPDATE to do it in chunks of 10000 rows thinking it would help with the memory pressure part :-). Indeed, it might help you if that was the case for you, but it did not help me! Basically, the idea is to keep updating rows that qualify in chunks of 10000 inside a loop until no more rows qualify for the UPDATE and we exit the loop. A supporting index that makes this query efficient would be helpful.

..or corruption?

However, this link listed many possible problems that could cause this error and I decided to try DBCC CHECKTABLE on the table in question.

Doing a quick check, the table indeed had a corrupted index

The Solution:

To fix the index corruption, I tried doing an online index rebuild and it wasn’t supported in the Standard edition I was running. So, I just dropped and recreated the index.

Then, I ran the UPDATE and it worked like a charm!

Источник

JCB Service Parts Pro 1.17.0001 [03.2013] ISO

(07-12-2016, 12:29 AM) vic13r Wrote: I can’t install it i get always the error:there was an unexpected error running SQL scripts.Setup will now terminate.
There are any instructions,or a solution for the error?

No one can help me.

mate inside the folders and before to install the program you need to install other programs to can run correctly. so. go on with the first step.

(07-12-2016, 12:29 AM) vic13r Wrote: I can’t install it i get always the error:there was an unexpected error running SQL scripts.Setup will now terminate.
There are any instructions,or a solution for the error?

No one can help me.

mate inside the folders and before to install the program you need to install other programs to can run correctly. so. go on with the first step.

(07-12-2016, 12:29 AM) vic13r Wrote: I can’t install it i get always the error:there was an unexpected error running SQL scripts.Setup will now terminate.
There are any instructions,or a solution for the error?

No one can help me.

mate inside the folders and before to install the program you need to install other programs to can run correctly. so. go on with the first step.

I have allready done this.
The solution is to unistall all 2008 sql instalation and start the installation again it will ask again for the sql before the spp and everything is OK on win7 64bit but on win8 32 bit I get a localhost error has anyone a solution for this??

do the normal way. fresh windows installation and all new inside and after install again. If still have an error then maybe the archive it is not ok.

(07-12-2016, 12:29 AM) vic13r Wrote: I can’t install it i get always the error:there was an unexpected error running SQL scripts.Setup will now terminate.
There are any instructions,or a solution for the error?

No one can help me.

mate inside the folders and before to install the program you need to install other programs to can run correctly. so. go on with the first step.

I have allready done this.
The solution is to unistall all 2008 sql instalation and start the installation again it will ask again for the sql before the spp and everything is OK on win7 64bit but on win8 32 bit I get a localhost error has anyone a solution for this??

do the normal way. fresh windows installation and all new inside and after install again. If still have an error then maybe the archive it is not ok.

Источник

SQL Server Agent Job stops SSIS Step with «unexpected error» and without any error informations

I am dealing with my problem on some Windows Server 2019 (Core) with one running SQL Server 2019 CU4 instance each.

What we try to do

We are currently building a data warehouse with distributed databases. The individual layers of the DWH are located on one database server each. The data exchange between the layers/servers takes place via SSIS ETLs, which use Linked Servers to reach the other layers and drag and drop data. Each layer also has its own SSIS service instance and executes the corresponding SSIS packets. The SSIS packages are called by SQL Server Agent jobs. We have a job that executes the SSIS packets (#1), which in turn calls another job (#2) as the last step, which after a short wait time executes the calling job (#1). Thus, controlled by schedules, a loop is created and data is continuously transferred with ETLs.

I hope this was not too much unnecessary background

The error

Basically the job is running and there are numerous successful executions. However, we are observing interruptions at job #1 without helpful information regarding the error. This means that the job history log refers to the SSIS log, which again only contains an «unexpected termination». In the SSIS log, we only see behavior that indicates that the ETL packet active at that time stopped after validation. Depending on the log level, nothing is logged at all, not even the execution of single packages of the project. The package where this error occurs is different and not limited to a specific one.

What I have already tried

• Re-create the jobs and SSIS Enviroments by hand (scripted before)
• Using the 32Bit Runtime
• Upgrade the SSIS project/package version to 2019
• Increase the log level to «verbose»
• Patching the SQL Server to CU4
• Save ssis dump files (couldn’t find them or they weren’t created)
• Search Windows and SQL Server Logfiles

Does anyone have some suggestions or some ideas how to become more error specific informations?

Thank you very much and take care 🙂

UPDATE We have an error message (OLE DB 0xC0202009 and 0X80004005)! In order to exclude the use of environments as a cause, I manually set the parameters in the SSIS job step instead of overwriting them by selecting an environment.

Long story short: Today it turns out that the parameter for an OLE DB Connection String is not passed correctly.

The following is specified as a parameter in the job step:

However, the following connection string is specified in the context of the error message: Please note that some arguments are added twice to the parameter (red).

Источник

Error during «Run SQL Script» #15

I installed JDK, MySQL, and Apache Tomcat. And now when I get to the part where I run schema.sql in MySQL 5.5 I get an error that says:

**Error During «Run SQL Script»

error calling Python module function
SQLIDEUtils.runSQLScript**

The text was updated successfully, but these errors were encountered:

Are there any more details on which line of the script failed? It could be the drop user command at the beginning of the script (the script is written to allow to recreate everything when executed for the second time; hence the -f parameter in the installation instructions).

If so, you could try to remove (or comment out) the drop user line and rerun the script.

That one error screen is all that I get when I try to run schema.sql in Workbench. I tried commenting out that line you reference and it doesn’t change anything.

Now, I am running this from my Windows 10 laptop, so I’m not sure if that platform isn’t supported. But I have installed everything I’m supposed to. For some background, I’m trying this out personally before I bring it to my IT department.

In the MySQLWorkbench, instead of File > Run SQL Script, could you try to use File > Open SQL Script followed by Query > Execute (All or Selection)? This way, you should see an output from each query of the schema.sql script.

You could also try to use the mysql command (from a command line) instead. Or, splitting the schema.sql into smaller chunks to isolate the problem.

UniTime should work on any machine capable of running Java, Tomcat, and MySQL, including Windows 10. For production, a Linux-based system is recommended.

Thank you for your patient help with this.

When I run the line that says use mysql; it gives this error:

Error during «Vertical Output»

error calling Pyhton module function
SQLIDEUtils.verticalOutput

That is odd, the use mysql command only changes which database is going to be used by the following commands. The mysql database is where the users and their roles reside.

I am not very familiar with the MySQLWorkbench. I have tried to reproduce the issue using MySQLWorkbench 6.3 connecting to a local instance of MySQL 5.6.12 on my Mac. I did not have any problems with either using File > Run SQL Script or with File > Open SQL Script followed by Query > Execute (All or Selection).

You can try to create the timetable user and the timetable database manually, using the workbench and only use the schema.sql to create all the tables.

Or you can try to use the mysql command from a command line as indicated in the UniTime installation manual (using the The MySQL Command-Line Tool).

Источник

Way to abort execution of MySQL scripts (raising error perhaps)?

I need to write setup scripts for MySQL (usually run using ‘source [file]’ from mysql console) that depend partly on existing data, and there are differences in environments, meaning that sometimes script does fail. A common case is that a ‘SET’ statement with a select (to locate an id) fails to find anything; console sets value to NULL. In this case I would like the script to fail; I have heard this would be done by raising an error (with other DBs). However it appears like MySQL didn’t have a way to do this.

Are there good ways to force failure under such conditions? As things are now updates will fail when insert tries to use null, but even that does not terminate script itself. Ideally it would just fail and terminate as soon as a problem is encountered.

7 Answers 7

I had the same problem and the GUI isn’t an option for me. Here’s how I solved it:

It’s a function instead of a procedure so it can be called in a script like this:

You’ll probably need to start the mysql client with the —disable-reconnect option.

I think what you’re encountering is a limitation of the MySQL console. Given a list of statements, the MySQL console executes each one regardless of any errors generated. Even if you implemented some of the error-raising suggestions that previous comments have mentioned, the MySQL console won’t stop executing when such an error is encountered.

I’ll assume that you don’t have the resources to apply a scripting language to the problem that could execute your SQL for you and handle the errors. I think in this case, you just need a more robust tool than the MySQL console.

MySQL Administrator does what you need, if I understand your problem correctly. If you set up your MySQL connection and connect to the database, you have two tools available from the Tools menu. The normal MySQL console is there, but you also have the MySQL Query Browser.

If you open the Query Browser, you get a decent GUI view of your MySQL databases. File -> Open Script to open your SQL script, then use the Execute button.

You get a nice progress bar, and more importantly from the sounds of it, if a query fails, the script execution halts and highlights the failed query. You can choose to skip it and keep going, or even manually modify your data and start up from someplace else farther down the script.

I abandoned the MySQL console almost immediately once I found out about and tried Administrator.

Источник

We use cookies on our website to give you the most relevant experience by remembering your preferences and repeat visits. By clicking “Accept All”, you consent to the use of ALL the cookies. However, you may visit «Cookie Settings» to provide a controlled consent. Read More