this is my second post on this issue, and I'm hoping to solve it now.
I got this error msg: DTS_E_PRODUCTLEVELTOLOW
when tring to run SSIs package with load data from File source (simple one) to DB on SQL2005 and the package is stored and exec on the SSIS server.
We installed the SSIS server with the Database engine on the same machine.
when running from my workstation it work fine, but when the package was uploaded to the MSDB and executed from there - it failed.
help, anyone.
Oh, by the way - microsoft issues on that problems didnt helpd - i got the enteprise edition installed and there is a match between the versions of all the components: BIDS, Server SSIS and SQL2005
I just upgraded my development machine from SQL Server 2005 Express edition to Standard edition. I can still execute my packages in Business Intelligence Development Studio, and when I use SQL Server Management Studio to connect to SSIS on our server I can import them into the database and run them (I understand the package is actually running locally, using SSIS on my desktop).
But when I RDP to the server, bring up SSMS, and try to run the package from the MSDB folder, I now get:
SSIS Error Code: DTS_E_PRODUCTLEVELTOLOW. The product level is insufficient for component "Task 1"
Before the upgrade, that worked fine.
So which product level is too low? I upgraded SQL Server on my desktop, so SSIS, SSMS, and BIDS there cannot be any lower than they were before. That seems to leave SQL Server and/or SSIS on the server, but that doesn't make any sense at all.
All BIDS is doing is generating XML (the .dtsx file) that represents the SSIS package, and as far as I know SSIS as a language is the same everywhere so how can there be run-time discrepancies between the development host and the deployment host?
I have a simple SSIS packae dataflow importing data from FileSource to SQL2005 table.
From my local machine it works fine but after deployment to MSDB db on the target server i got the error above.
The FileSource is located in a remotlly FileServer
my Server data: Microsoft SQL Server Enterprise Edition (64-bit) Microsoft Windows NT 5.2 (3790) version: 9.00.3042.00
my workstation data:
Microsoft SQL Server Management Studio 9.00.3042.00 Microsoft Analysis Services Client Tools 2005.090.3042.00 Microsoft Data Access Components (MDAC) 2000.085.1117.00 (xpsp_sp2_rtm.040803-2158) Microsoft MSXML 2.6 3.0 4.0 5.0 6.0 Microsoft Internet Explorer 7.0.5730.11 Microsoft .NET Framework 2.0.50727.42 Operating System 5.1.2600
I am moving all of our SSIS packages from a stand alone server to a clustered environment. The old server ran Enterprise Edition, the new server runs Enterprise Edition 64 bit.
One package on the new server is giving me the error messaage DTS_PRODUCTLEVELTOLOW when run from a job. The package is stored in MSDB
I went back to the server and ran the following with the following results.
- Connected to SSIS from Management Studio on my desktop and ran the package and got the same error message.
- Did the same as above but was connected to the server through Remote Desktop and it ran fine
- Ran the job, which just runs the package and it ran fine
When I design package under ssis, I always use execute sql task to replace OLE DB Command. Normally, I use staging tables to get all data from data source,then modify or generate some columns on the staging tables according to bussiness rules using execute sql task, Finally,transfer to data destination. And execute sql task is more effiecient than OLE DB Command. I suppose there's reason for using OLE DB Command. But I don't know. So what's the reason to use OLE DB Command?
I am having difficulty in identify my deadlock reason. So, please give me some hints.
In my application, I have 2 standard functions. One for transaction creation and one for reporting. The strange problem is I seldom / never got any deadlock witht the transaction creation. Instead, I got deadlock problem with the reporting.
In the reporting function, I only use select and aggregate function. Why will deadlock be raised? Can someone give me an example why such deadlock happened?
Hello everyone, I need your help. I have SQL*Server 2000 in a Windows 2000 advanced server service pack 4. My SQL*Server has the path 4. Yesterday I had this message and then my database was down. SQL Server is terminating due to 'stop' request from Service Control Manager. Any help?
To test the problem, I created a very simple package. All it does is load a simple text file to a table on the local server.
I set protection level to "encrypt sensitive with password", and set the password. I changed the creator name to the SQL Server Agent Account. (don't know how to change the GUID?)
It runs fine from BIDS and msdb storage. But if I run it from the job, it fails with: Executed as user: DOMAINUSERNAME. The package execution failed. The step failed.
No logging occurs, even though I have set the package to log, which seems to indicate it's not even getting as far as starting the package. I've restarted all the services.
I tried running this package from a job on ANOTHER server and it works, no problem. There's just something going on with this other server where it won't run from the job... both servers use the same SQL Server Agent account.
I've consulted http://support.microsoft.com/kb/918760 and it talks about this problem but I have everything set correctly... never had this problem before... seriously.
and the file php.sqlsrv.dll is located in the PHPext directory
I've restarted the IIS server with php running and working just fine. Is there anything else I could still check ?
Code Snippet
if (!extension_loaded('sqlsrv')) { echo("NOT LOADED"); }
Produces: not loaded.
EDIT: Dug up some logs: The description for Event ID ( 2 ) in Source ( PHP-5.2.5 ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: php[2144]; PHP Warning: PHP Startup: Unable to load dynamic library 'C:PHPextphp_sqlsrv.dll' - The specified module could not be found. in Unknown on line 0.
Dear All, I have some user databases that go into single user mode for no apparent reason. Is there any reason that SQL Server 7 would set a database in single user mode by itself? NB They are not being set single user by anyone else here, they would not know how.
Hi, I hava a JAVA application that updates a SQL2000 (SP3a)database. The application handles different types of "jobs" which effectively update the DB.
One job in particular appears to block all subsequent jobs. It comprises of a large amount of inserts/updates in a single transaction. This is necessary as it is an "all or nothing" scenario - so we cannot break the transaction into smaller ones. The transaction appears to succeed as it reaches the COMMIT TRAN statement without error. However the records do not get written to the database. EM indicates a large number of locks held on the tables accessed by the transaction and these do not get released.
Using the SP sp_blocker_pss80, the blocking SPID has a waittime of 0 and a waittype of 0x0000 - the lastwaittype is WRITELOG and its status is AWAITING COMMAND
I am using MS SQLSERVER JDBC Driver SP2 (considering using jTDS)
I have tried - increasing Transaction Log size - Moving Transaction Log to a separate Disk - Reducing Isolation Mode to Read Uncommitted - Set AutoCOMMIT to true - set Close Cursor on COMMIT - set SelectMethod to Direct - (we use Cursor by default)
None of these have succeeded in fixing the issue.
The job will succeed if it is the first/only job to access the database. But if another job precedes it - then the blocking occurs. I have verified that the preceding job only holds shared dataabase locks before the blocking job is run.
Each job will use its own JDBC connections to access the database for reading purposes, but all of the writing goes through the blocking SPID.
...and it is because... when i drag and drop my script file into query window unlike query analyzer which selects the current database, new MSSMS selects the users 'default' database.
we maintain 1 script file for each sp/function and ddl/views groupe related stuff in 1 or more files
in query analyzer I just have to select DB where i want to deploy scripts and drag and drop the files from explorer and then then 1) press F5 (to run) 2) press CTL + F4 (to close window) 3) repeat till all scripts are deployed
and now in MSSMS
1) select db (this step is really painful especially when i have to deploy more than 1 script/file) 2) press F5 3) press CTL + F4 4) repeat
is there any settings that could change the behavior of SMS2K5 like old QA2K?
well what i cant do here is change default db to the tartget db before deploying and switch back after deploying (but not a true solution)
Hi folks,Hopefully this is a simple fix, but I keep getting Syntax error withthis statement in an MS SQL DTS statement and in Query Analyzer:Update A Set A.deptcode = A.deptcode,A.type = A.Type,a.TotalExpenseUnit = (a.LaborExpenseUnit + a.OtherExpenseUnit)Where a.Type in ('FYTD04', 'Prior Year','Budget')From Data_Unsorted A Join Data_Unsorted B OnA.deptcode = B.deptcode and A.type = B.TypeBelow is the error from Query Analyzer:Server: Msg 156, Level 15, State 1, Line 5Incorrect syntax near the keyword 'From'.Where do I place my Where..In statement since I only want to limit theUpdate to run for items where a.type is FYTD04, Prior Year, or Budget?Thanks,Alex.
At one of our SQL2005 servers we've got a really strange problem. The transaction logfile of one of our databases is suddenly disappearing without a reason. From that moment on the event log (application) is being filled up with SQLserver event 9001
Event Type: Error Event Source: MSSQL$SQLEXPRESS Event Category: (2) Event ID: 9001 Date: 16/04/2007 Time: 12:31:40 User: N/A Computer: PBVSRV Description: The log for database 'Putboringen' is not available. Check the event log for related error messages. Resolve any errors and restart the database.
BACKUP MASTER KEY TO FILE = 'c:TestEncryptionMasterKey.key'
ENCRYPTION BY PASSWORD = '23'
but why would I need to do it as the DBMK is stored in the databases itself ( in sys.symmetric_keys) and we dump all databases nightly. Just "in case"?
I use MSDE in my system, and sometimes the following error occurs in MSDE. After that, I can not even access MSDE with the osql command.
Can anyone give some advice as how to deal with this kind of error or how to find the real reason? I have checked MS homepage, but I can not get the details of it.
Error: 17883, Severity: 1, State: 0 The Scheduler 0 appears to be hung. SPID 0, ECID 0, UMS Context 0x003B70F8
I can log in to a database with administrator account, but not with an user account. I am getting "Invalid login information" error message. What will be the likely cause for this? I am using Winodws authentication.
I have been working on an app for several weeks. My database size went from 9MB to about 12MB. Sometime in the last 2 days it jumped up to 242 MB. I don't know why. Now I cannot open it with management Studio Express. It says another process is using it. Usually this means I have a aspnet_wp.exe process running (from Visual Studio) and I just end the process, but Wndows Task Manager will not end the process. It does knock its size way down to 2.9 MB but won't kill it. Rebooting won't kill it either.Are these two symptoms related? How do I recover?Thank you.
Hello, I am having problems inserting information into my DB.
First is the code for the insert
Sub AddCollector(Sender As Object, E As EventArgs) Message.InnerHtml = ""
If (Page.IsValid)
Dim ConnectionString As String = "server='(local)'; trusted_connection=true; database='MyCollection'" Dim myConnection As New SqlConnection(ConnectionString) Dim myCommand As SqlCommand Dim InsertCmd As String = "insert into Collectors (CollectorID, Name, EmailAddress, Password, Information) values (@CollectorID, @Name, @Email, @Password, @Information)"
myCommand = New SqlCommand(InsertCmd, myConnection)
Try myCommand.ExecuteNonQuery() Message.InnerHtml = "Record Added<br>" Catch Exp As SQLException If Exp.Number = 2627 Message.InnerHtml = "ERROR: A record already exists with the same primary key" Else Message.InnerHtml = "ERROR: Could not add record" End If Message.Style("color") = "red" End Try
myCommand.Connection.Close()
End If
End Sub
No matter what I get a "Could not add record" message
Even substituting the insert command string with my stored procedure I would get the same thing
Stored Procedure:
CREATE Procedure CollectorAdd ( @Name nvarchar(50), @Email nvarchar(50), @Password nvarchar(50), @Information nvarchar(3000), @CustomerID int OUTPUT ) AS
INSERT Collectors ( Name, EMailAddress, Password, Information )
VALUES ( @Name, @Email, @Password, @Information ) GO
Can anyone see any problems with this code? It looks good to me but I get the same message always.
Does any one know what could be making the size of a backup get so big in SQL server?
I noticed if you back-up the same database in Enterprise Manager over and over (without making any changes to the database), the size of the backup gets bigger and bigger. To get around this I simply erase the backup and create a new one.
Now I'm experiencing the same kind of problem, different situation. I decided to make very few changes to my database. If anything, I shrunk the size of the tables and stored procedures.... Now all of a sudden my database backup is 7 times larger.
What could be increasing the size so much, if I haven't increased the amount of tables or stored procedures?
What is the log file about? Mine is huge? Is there a way to reset it or clear it?
Hope someone can help me with this because its driving me potty!
I have a .NET script that sends really simple queries to SQL server that works perfectly 50% of the time but for the other 50% it takes ages (2-3 minutes) and then fails, I'm assuming because it times out. I then check the SQL by excecuting it via query analyzer and it again takes ages but will work eventually (I'm assuming because this bypasses the timeout settings, but changing these isn't on).
This happens randomly, the scripts will be working fine and then fail a few times before magically working again!
Any ideas? Perhaps some database features that commonly cause this problem? The problem only occurs with one database, all our others are fine but we can't spot any differences!
In the master database for a SQL Server instance I noticed the dt... objects (procedures, etc.) in create date of today about 7 minutes before I looked in sysobjects. No changes have been made to that instance for months. Also in other cases I noticed the same thing just different dates for each instance. Any ideas on why the dates would change?
Hi all, could someone be kind enough to provide me some help into why the following IF statement is not working? Basically, I am trying to find out whether a field in my database has a CONSTRAINT attached to it with a particular name... IF it does have one then drop it and re-create it ELSE simply create one.
I have used SELECT * FROM SYSOBJECTS to find whether it exists which according to the results it does EXIST, however my IF statement is not detecting it and I get an error which states: Msg 1781, Level 16, State 1, Line 30Column already has a DEFAULT bound to it.Msg 1750, Level 16, State 0, Line 30Could not create constraint. See previous errors.
However, surely my IF statement is suppose to be handling this problem and therefore if it does EXIST THEN it should ideally drop the CONSTRAINT and then re-create it but this is not the case... instead the ELSE is always being triggered. After using SYSOBJECTS I copied it directly from the results view into my SQL but still for some reason if my constraint does exist it jumps to the ELSE.
Code SnippetIF EXISTS (SELECT * FROM SYSOBJECTS WHERE NAME = '[DF_TBL_SyncTable_OB-DEVUK]') BEGIN ALTER TABLE TBL_SyncTable DROP CONSTRAINT [DF_TBL_SyncTable_OB-DEVUK] ALTER TABLE TBL_SyncTable ADD CONSTRAINT [DF_TBL_SyncTable_OB-DEVUK] DEFAULT 2 FOR [OB-DEVUK] ALTER TABLE TBL_SyncTable ADD [OB-DEV6] TINYINT DEFAULT 2 END ELSE BEGIN ALTER TABLE TBL_SyncTable ADD CONSTRAINT [DF_TBL_SyncTable_OB-DEVUK] DEFAULT 2 FOR [OB-DEVUK] ALTER TABLE TBL_SyncTable ADD [OB-DEV6] TINYINT DEFAULT 2 END
I am having a problem with sql server 2005. I would like to access the database but unfortunately I disabled the account I am using to login. Can somebody tell me how can I enable it if possible?
I have a job that runs an SSIS package. The job seems to be able to run through the package successfully, but at the end it errors out saying "The binary code for the script is not found. ...". The script referred to is at the beginning part (not the very first step) and should already be run.
The thing is, I can manually run this package on the server or visual studio without any problem. Also this job has been run on a regular basis without any issues on our old SQL 2008. I'm migrating this to Amazon Cloud SQL 2014.
Together with this package are other two very similar ones. They all work fine. I just can't figure out what can be wrong with this one.
I have searched extensively and not been able to find a solution to this problem.
The problem: We have one SSIS package will sometimes 'finish' executing (or crash from a .NET exception) when it certainly has not made its way through all of the data flow components. There are no SSIS error messages, no warnings, and it never happens at the same location in the package's pipeline. The only thing that is instantly visible is a command window that flashes on the screen and disappears too quickly to see anything,.
Sometimes the package does actually complete without any problem, but most of the time, it does not.
What we see: If the packages is being run through the "Execute Package Utility" (by double clicking the dtsx file), after a bit, a command window flashes on the screen and instantly disappears (no text is visible), then the €œExecute Package Utility€? disappears. The event viewer of the machine then shows:
If the package is running within visual studio, again the command window flashes on the screen, then the "Execution has completed" prompt appears, but any "running" component remains Yellow (no red), both within the data flow and control flow (we do not have any event handlers set up). Neither our SQL Log provider, nor the "Execution Results" tab in visual studio show any type of error message... all SSIS messages just stop right in the middle of the many OnPipelineRowsSent log events (so there is no PackageEnd log event when this happens). The event viewer on the machine contains no useful messages when running within visual studio.
And other packages: Are fine. This is only the case for this one package... we have nearly a dozen other packages, all very similar in design, that complete without issue.
We have also tried re-creating this troublesome package from scratch with no avail. <!--[if !supportLineBreakNewLine]--> About the package: The Data Flow is pulling rows from 3 different external SQL data sources (400k-500k rows total), sorting and merging the rows, performing some basic lookups, then SCD'ing the results. This Data Flow is executed multiple times within 2 nested for loops (these nested loops give us particular dates, i.e. years 2000 through 2008, then months 1 through 12 for each year). There is not a single script task in the package. The problem seems to happen most as the data is being pulled from the sources and merged together, but it is not limited to this area.
<!--[if !supportLineBreakNewLine]--><!--[endif]--> The environment: We€™ve tried to use multiple machines with the same result. The current machine specs are as follows: SQL Server 9.0.3042 (SP2) Windows Server 2003 R2, Enterprise x64 Edition, SP2 3.00GHz x 16 processors, all 64 bit 63.5 GB of RAM Over 1 terabyte of hard disk space .NET 2.0.50727.42
The package was designed using: Visual Studio 2005 with SP1 Microsoft SQL Server Integration Services Designer - Version 9.00.3042.00
I have some problem here. I have a sql server installed on one machine and I have another development machine for my asp application. How could I actually access the asp application and sql server at the same time from another machine within the network. I kept on getting the error message above.
Hi, I am trying to create a maintenance plan on an MSX server and push it out to a TSX server. When I try to run the job on the TSX server it goes into suspended status.
If I look in the SQLAGENT log I see the following error
2008-04-30 15:04:11 - + [125] Subsystem 'SSIS' could not be loaded (reason: This function is not supported on this system) 2008-04-30 15:08:19 - + [125] Subsystem 'SSIS' could not be loaded (reason: This function is not supported on this system) 2008-04-30 15:09:28 - + [125] Subsystem 'SSIS' could not be loaded (reason: This function is not supported on this system) 2008-04-30 15:27:36 - ! [LOG] Step 1 of job 'SystemDatabases.Back Up Database (Full) (Multi-Server)' (0x97394B08F6599040A18D93367FBDB5F7) cannot be run because the SSIS subsystem failed to load. The job has been suspended 2008-04-30 15:35:13 - + [125] Subsystem 'SSIS' could not be loaded (reason: This function is not supported on this system) 2008-04-30 15:50:27 - ! [LOG] Step 1 of job 'SystemDatabases.Back Up Database (Full) (Multi-Server)' (0x97394B08F6599040A18D93367FBDB5F7) cannot be run because the SSIS subsystem failed to load. The job has been suspended
my sql info is Microsoft SQL Server 2005 - 9.00.3239.00 (X64) Copyright (c) 1988-2005 Microsoft Corporation Enterprise Edition (64-bit) on Windows NT 5.2 (Build 3790: Service Pack 2)
