Error loading value

I have been getting the error below from an SSIS Package that has been running successfully in production for 2 Months. Also, this started after we installed SP2. We had errors durring the SP2 installation durring the Notification Services and Workstation Tools install but the installation program reported that the installations were successfull so I am not sure if this is related.

Here is the error message:

Date 6/12/2007 4:53:12 PM
Log Job History (SchedulerEMailer)

Step ID 1
Server MISSRV7
Job Name SchedulerEMailer
Step Name new step
Duration 00:00:08
Sql Severity 0
Sql Message ID 0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted 0

Message
Executed as user: XSRV7\SYSTEM. Microsoft (R) SQL Server Execute Package Utility Version 9.00.3042.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 4:53:12 PM Error: 2007-06-12 16:53:19.90 Code: 0xC0010018 Source: Description: Error loading value "<DTS:LogProvider xmlnsTS="www.microsoft.com/SqlServer/Dts"><DTSroperty DTS:Name="ConfigString">MISSRV7.SSISConfig.ssisuser</DTSroperty><DTSroperty DTS:Name="DelayValidation">0</DTSroperty><DTSroperty DTS:Name="ObjectName">SSIS log provider for " from node "DTS:LogProvider". End Error Could not load package "\ApptEmailer" because of error 0xC0010014. Description: One or more error occurred. There should be more specific errors preceding this one that explains the details of the errors. This message is used as a return value from functions that encounter errors. Source: Started: 4:53:12 PM Finished: 4:53:19 PM Elapsed: 7 seconds. The package could not be loaded. The step failed.

Any help would be greatly appreciated!!!

One problem that can possibly lead to this error is described in this KB:

http://support.microsoft.com/default.aspx/kb/913817

Please check if it affects your installation.

|||Hi

I am receiving this same error. Did you ever resolve it?

Thanks in advance

error loading the report in the designer

Hi all,
I'm working on rs2005, and i cannot load any server report in the
designer.
i get the following error:
"One or more errors encountered while loading the designer. The errors
are listed below.
Exception has been thrown by the target of an invocation "
I can load local reports, and i can load the server reports on other
computers.
It just suddenly stopped working in my laptop, and no reinstallation
helps (at least not the visual studio, framework, or the report server)
Does anyone hav an idea?
Thanks,
EyalWell, i found the solution eventually,
After getting a message "font verdana does not support style regular"
while trying to load a winforms into the designer, i deleted all my
fonts from my computer, and copied them from another computer.
both the winform problem and the reporting services problem has gone
forever.
it seems that a corrupted font has crashed the visual studio designer.
Eyal
Eyal =EB=FA=E1:
> Hi all,
> I'm working on rs2005, and i cannot load any server report in the
> designer.
> i get the following error:
> "One or more errors encountered while loading the designer. The errors
> are listed below.
> Exception has been thrown by the target of an invocation "
> I can load local reports, and i can load the server reports on other
> computers.
> It just suddenly stopped working in my laptop, and no reinstallation
> helps (at least not the visual studio, framework, or the report server)
> > Does anyone hav an idea?
> Thanks,
> Eyal

Error loading tables of different file groups.

Hi All,

I am facing a peculier problem. Problem definition goes like this,

I have one staging DB in which all the tables resides in Primary file and one production DB in which tables resides in 2 secondary files.

Now when iam trying to load the data from the table A in staging which is on primary file to the table A1 in production DB which in secondary file, all the data are going to error log instead of table A1.

Can you please tell me, where am i going wrong.

Regards,

Chetan

No. Not without the error message. Can you provide it?

-Jamie

|||

HI Jamie,

Sorry for that, error code and error message is as follows.

Error code:-1071607685

Error Message: No status is available.

Regards,

Chetan

sql

Error loading resource string in SP2

After I installed the SP2 and reboot the server, when I try to print the a
report, it keep pop up the error message say"Error loading resource string",
after I click many times, I got the printer properties window, many text in
the button are disappear, but I still could print it out.
Any idea?
ThanksMy guess is that you had the beta of SP2. If so then you need to clear out
then per Brian Welcker (MS): You need to clean out any older versions of the
controls from your C:\WINDOWS\Downloaded Program Files directory.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"msnews.microsoft.com" <huangxiaohua@.hotmail.com> wrote in message
news:uYZWGkxSFHA.2304@.tk2msftngp13.phx.gbl...
> After I installed the SP2 and reboot the server, when I try to print the a
> report, it keep pop up the error message say"Error loading resource
string",
> after I click many times, I got the printer properties window, many text
in
> the button are disappear, but I still could print it out.
> Any idea?
> Thanks
>

Error loading report

I have created many crystal reports within VB.Net that are based upon an *.xsd file as the report source is dynamic. This works fine on the machine they were developed on. However I now wish to roll out the final solution and store the reports on a shared network drive whilst the VB app is on each desktop. I have tried copying the *.rpt file to the shared drive along with the *.xsd files. I even changed each report to now look at the *.xsd in the new location. However when I try to open a report I get the following error:

Error in file e:\directory\report.rpt.
Failed to load database information.

Any ideas.?

ThanksMake sure it is pointing the correct database|||Check if proper DSN is created and Verify the Database in the report at design time.|||With e:\ being the network drive my report e:\myreport.rpt is pointing to e:\myreport.xsd

which is correct as far as I know.|||Have ttried changing network paths to UNC, no joy.

Strangely, if I load the project within VB.Net, the app and the reports run fine. But when I run the installed package I get this error. This makes me think that maybe I need to package up some additional files with the app.?

Error loading Query Execution Plan

I am trying to tune a very long running query (18 minutes on an Axim X51, 8secs on my laptop), but I can't get the query plan file that is generated on the device to load in the Sql Server Management Studio. I am using the Sql Everywhere CTP on the device, and version 9.00.2047 of the management studio shell.

FWIW, when I try to create the execution plan by running the same query on a .sdf file local on my laptop, I get a similar error trying to view the query plan.

Apart from the query plan issues, it would appear (just from the query execution time) that the indexes defined on the sdf file are not being used when executing the query on the device, but are being used when executing the query on the laptop. This is pure SWAG on my part, though.

I can't figure out how to attach a file to the post, unfortunately.

Thanks for any help you can offer.

Matthew Belk, BizSpeed, Inc.

Matthew,

What is the error that you get when loading the query execution plan in Management Studio? My guess is that it would be an issue in rendering the graphical execution plan. However, you can still see the plan information from the plan file (xml format).

Also, the query plan usually does not differ on the laptop and the device.

|||

I was able to identify the query bottleneck by manually interpreting the plan file, but it was an arduous task sifting through all that XML. There was a similar issue posted to the Feedback section in the SQL Server area of the Microsoft Connect website (issue id 231137) that I validated and commented on. That issue was marked closed/fixed, but there were no additional comments.

Thanks, Matthew

Here is the text of the plan file:

===================================

Error loading execution plan XML file C:\Documents and Settings\mbelk\My Documents\batitem.sqlplan. (SQLEditors)

Program Location:

at Microsoft.SqlServer.Management.UI.VSIntegration.Editors.ShowPlan.ShowPlanControl.LoadXml(String xmlFile)
at Microsoft.SqlServer.Management.UI.VSIntegration.Editors.ShowPlan.Editor.Microsoft.VisualStudio.Shell.Interop.IPersistFileFormat.Load(String fileName, UInt32 grfMode, Int32 readOnly)

===================================

Exception has been thrown by the target of an invocation. (mscorlib)

Program Location:

at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
at System.RuntimeMethodHandle.InvokeMethodFast(Object target, Object[] arguments, Signature sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at Microsoft.SqlServer.Management.SqlMgmt.ShowPlan.ObjectWrapperTypeConverter.ConvertFrom(ITypeDescriptorContext context, CultureInfo culture, Object value)
at System.ComponentModel.TypeConverter.ConvertFrom(Object value)
at Microsoft.SqlServer.Management.SqlMgmt.ShowPlan.ObjectWrapperTypeConverter.ConvertToObjectWrapper(Object item)
at Microsoft.SqlServer.Management.SqlMgmt.ShowPlan.ObjectWrapperTypeConverter.ConvertFrom(ITypeDescriptorContext context, CultureInfo culture, Object value)
at System.ComponentModel.TypeConverter.ConvertFrom(Object value)
at Microsoft.SqlServer.Management.SqlMgmt.ShowPlan.PropertyFactory.CreateProperty(PropertyDescriptor property, Object value)
at Microsoft.SqlServer.Management.SqlMgmt.ShowPlan.ObjectParser.ParseProperties(Object parsedItem, PropertyDescriptorCollection targetPropertyBag, NodeBuilderContext context)
at Microsoft.SqlServer.Management.SqlMgmt.ShowPlan.XmlPlanParser.Parse(Object item, Object parentItem, Node parentNode, NodeBuilderContext context)
at Microsoft.SqlServer.Management.SqlMgmt.ShowPlan.XmlPlanParser.Parse(Object item, Object parentItem, Node parentNode, NodeBuilderContext context)
at Microsoft.SqlServer.Management.SqlMgmt.ShowPlan.XmlPlanParser.Parse(Object item, Object parentItem, Node parentNode, NodeBuilderContext context)
at Microsoft.SqlServer.Management.SqlMgmt.ShowPlan.XmlPlanParser.Parse(Object item, Object parentItem, Node parentNode, NodeBuilderContext context)
at Microsoft.SqlServer.Management.SqlMgmt.ShowPlan.XmlPlanParser.Parse(Object item, Object parentItem, Node parentNode, NodeBuilderContext context)
at Microsoft.SqlServer.Management.SqlMgmt.ShowPlan.XmlPlanParser.Parse(Object item, Object parentItem, Node parentNode, NodeBuilderContext context)
at Microsoft.SqlServer.Management.SqlMgmt.ShowPlan.XmlPlanParser.Parse(Object item, Object parentItem, Node parentNode, NodeBuilderContext context)
at Microsoft.SqlServer.Management.SqlMgmt.ShowPlan.XmlPlanParser.Parse(Object item, Object parentItem, Node parentNode, NodeBuilderContext context)
at Microsoft.SqlServer.Management.SqlMgmt.ShowPlan.XmlPlanParser.Parse(Object item, Object parentItem, Node parentNode, NodeBuilderContext context)
at Microsoft.SqlServer.Management.SqlMgmt.ShowPlan.XmlPlanParser.Parse(Object item, Object parentItem, Node parentNode, NodeBuilderContext context)
at Microsoft.SqlServer.Management.SqlMgmt.ShowPlan.XmlPlanParser.Parse(Object item, Object parentItem, Node parentNode, NodeBuilderContext context)
at Microsoft.SqlServer.Management.SqlMgmt.ShowPlan.XmlPlanParser.Parse(Object item, Object parentItem, Node parentNode, NodeBuilderContext context)
at Microsoft.SqlServer.Management.SqlMgmt.ShowPlan.XmlPlanParser.Parse(Object item, Object parentItem, Node parentNode, NodeBuilderContext context)
at Microsoft.SqlServer.Management.SqlMgmt.ShowPlan.XmlPlanParser.Parse(Object item, Object parentItem, Node parentNode, NodeBuilderContext context)
at Microsoft.SqlServer.Management.SqlMgmt.ShowPlan.XmlPlanNodeBuilder.Execute(Object dataSource)
at Microsoft.SqlServer.Management.UI.VSIntegration.Editors.ShowPlan.ShowPlanControl.LoadXml(String xmlFile)

===================================

Exception has been thrown by the target of an invocation. (mscorlib)

Program Location:

at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
at System.RuntimeMethodHandle.InvokeMethodFast(Object target, Object[] arguments, Signature sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks)
at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
at Microsoft.SqlServer.Management.SqlMgmt.ShowPlan.ObjectWrapperTypeConverter.ConvertFrom(ITypeDescriptorContext context, CultureInfo culture, Object value)
at System.ComponentModel.TypeConverter.ConvertFrom(Object value)
at Microsoft.SqlServer.Management.SqlMgmt.ShowPlan.PropertyFactory.CreateProperty(PropertyDescriptor property, Object value)
at Microsoft.SqlServer.Management.SqlMgmt.ShowPlan.ObjectParser.ParseProperties(Object parsedItem, PropertyDescriptorCollection targetPropertyBag, NodeBuilderContext context)
at Microsoft.SqlServer.Management.SqlMgmt.ShowPlan.ExpandableObjectWrapper..ctor(Object item, String defaultPropertyName, String displayName)
at Microsoft.SqlServer.Management.SqlMgmt.ShowPlan.ObjectWrapperTypeConverter.Convert(SeekPredicateType item)

===================================

Object reference not set to an instance of an object. (SqlMgmt)

Program Location:

at Microsoft.SqlServer.Management.SqlMgmt.ShowPlan.ExpandableArrayWrapper.PopulateProperties(ICollection collection)
at Microsoft.SqlServer.Management.SqlMgmt.ShowPlan.ObjectWrapperTypeConverter.ConvertToObjectWrapper(Object item)
at Microsoft.SqlServer.Management.SqlMgmt.ShowPlan.ObjectWrapperTypeConverter.ConvertFrom(ITypeDescriptorContext context, CultureInfo culture, Object value)
at System.ComponentModel.TypeConverter.ConvertFrom(Object value)
at Microsoft.SqlServer.Management.SqlMgmt.ShowPlan.PropertyFactory.CreateProperty(PropertyDescriptor property, Object value)
at Microsoft.SqlServer.Management.SqlMgmt.ShowPlan.ObjectParser.ParseProperties(Object parsedItem, PropertyDescriptorCollection targetPropertyBag, NodeBuilderContext context)
at Microsoft.SqlServer.Management.SqlMgmt.ShowPlan.ExpandableObjectWrapper..ctor(Object item, String defaultPropertyName, String displayName)
at Microsoft.SqlServer.Management.SqlMgmt.ShowPlan.ObjectWrapperTypeConverter.Convert(ScanRangeType item)

|||

Sorry about that. I checked out the details.

This error shows up whenever more than one column of a composite index is being used for a seek or scan.

e.g.

select * from
stores, sales where
sales.stor_id = stores.stor_id
and sales.ord_num = 'test'
- with a composite index on sales.stor_id and sales.ord_num.

For a work around, choose only one column from the index while tuning the query initially.

e.g.

select * from
stores, sales where
sales.stor_id = stores.stor_id

The plan that you get should be similar to the actual plan. For the final pass of tuning the query, use the full query!

Thanks

Pragya

sql

Error loading package

Hi there all...

We've just started using SSIS packages, and everything seems to be going ok.

I've recently set up a couple of jobs which just run an SSIS package every 5 minutes to collect data.
These run fine 90% of the time, but intermittantly produce an error.

When using a SSIS task in the job it simply reported
"Could not load Package."

I have changed these to use DTExec as I heard it gave more verbose execution results, and now I get an error like
"Executed as user: NZ\SQLAdmin. Microsoft (R) SQL Server Execute Package Utility Version 9.00.1399.06 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 8:25:00 a.m. Could not load package "\MSDB\RadiusBilling\Get_RADIUS_AuthLog" because of error 0x80040E37. Description: Table/view either does not exist or contains errors. Source: Microsoft SQL Native Client Started: 8:25:00 a.m. Finished: 8:25:00 a.m. Elapsed: 0.047 seconds. Process Exit Code 5. The step failed."

So far I have not been able to find anyone else with similar errors.
Whenever the package executes it seems to run fine, so this seems to be an error just getting the package to execute in the first place, and as I said it only happens internittantly.

The packages talk to a SQL2005 server using windows authentication (which I assume is inherited from the SQLAgent service user), as well as a MySQL server through an ODBC connection.
The package is saved in the MSDB SSIS Package Store and uses the "Rely on Server for Security" option

Does anyone know why this is happening and how I can fix it?

disenfranchised wrote:

Hi there all...

We've just started using SSIS packages, and everything seems to be going ok.

I've recently set up a couple of jobs which just run an SSIS package every 5 minutes to collect data.
These run fine 90% of the time, but intermittantly produce an error.

When using a SSIS task in the job it simply reported
"Could not load Package."

I have changed these to use DTExec as I heard it gave more verbose execution results, and now I get an error like
"Executed as user: NZ\SQLAdmin. Microsoft (R) SQL Server Execute Package Utility Version 9.00.1399.06 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 8:25:00 a.m. Could not load package "\MSDB\RadiusBilling\Get_RADIUS_AuthLog" because of error 0x80040E37. Description: Table/view either does not exist or contains errors. Source: Microsoft SQL Native Client Started: 8:25:00 a.m. Finished: 8:25:00 a.m. Elapsed: 0.047 seconds. Process Exit Code 5. The step failed."

So far I have not been able to find anyone else with similar errors.
Whenever the package executes it seems to run fine, so this seems to be an error just getting the package to execute in the first place, and as I said it only happens internittantly.

The packages talk to a SQL2005 server using windows authentication (which I assume is inherited from the SQLAgent service user), as well as a MySQL server through an ODBC connection.
The package is saved in the MSDB SSIS Package Store and uses the "Rely on Server for Security" option

Does anyone know why this is happening and how I can fix it?

So you say it fails intermittently? Well that's weird.

Its failing because it cannot validate one of its external data sources. The fact that its intermittent leads me to suggest that there is some outside influence that is causing this. network connectivity perhaps? I'm just speculating here.

-Jamie

|||

I have suspected that it might be something to do with the permissions on the domain account that the SQLAgent runs as.

Something like the account was getting locked perhaps.

However if that was the case I'd expect to see 5-6 failures as the job runs every 5 minutes, and the domain keeps accounts locked for 30 minutes. We only ever seem to get isolated failures, but about 6 times per day (which out of 288 executions isn't to bad)

|||

Hi

I have the same problem with my SSIS packages.

I'm still developing the package so it isn't finished yet. But on each step I put it into production to see, how it behaves.

In adtition to you, I noticed, that this error occurs more often, when the package is stored in MSDB store. Previously I have had packages stored in SQL's FileSystem store and error occurs maybe twice or three times per week. Now it occurs several times per day.

I use the domain user and id in Administators group on the server.

I execute the package on the server where the inserting database is.

I execute the package every minute.

BR

ZigaP

|||Again, it sounds like an intermittent connectivity issue.|||

I think the network connectivity is not an issue.

It cannot be, because I run packages on the server where the database is.

what about this: if I replace the name of the server with "(local)"... can this solve the problem?

|||My company develops SSIS components.
No matter what you think or what you are told, I can tell you that most parts of SSIS only run about 90% of the time when you execute packages from the 'Business Intelligence Development Studio' (VS2005 really)
We actually have a problem right now because we do not have any test cases which will run 100% of the time if you let them run for a day.
Most things seem to work if you keep testing to less than an hour, but anymore and you will eventually hit a failure.

Oddly, the problem only occurs at the package level. We have not seen a package or flow that dies in the middle, or in different places, or anything variable.
It either runs to success, dies upon startup (by any means, scheduled, manual, debug), or just plain does the wrong thing. Once a given package shows a particular problem, the problem is the same every time that package fails, and there is usually only one problem.

It is known to us and some big customers that you need to shut down dev studio and reload your project to get things to work again.

The size and/or complexity of the work does not seem to matter either.
We have simple flows with one src and one dest that moves 10000 rows, all the way to massive, multi-pronged flows with multiple sources, lookups, and millions of records.
They all eventually fail. Once you get the first failure, all others on that package will be of the same nature.

Its odd.
|||

FarmerChet wrote:

My company develops SSIS components.
No matter what you think or what you are told, I can tell you that most parts of SSIS only run about 90% of the time when you execute packages from the 'Business Intelligence Development Studio' (VS2005 really)
We actually have a problem right now because we do not have any test cases which will run 100% of the time if you let them run for a day.
Most things seem to work if you keep testing to less than an hour, but anymore and you will eventually hit a failure.

Oddly, the problem only occurs at the package level. We have not seen a package or flow that dies in the middle, or in different places, or anything variable.
It either runs to success, dies upon startup (by any means, scheduled, manual, debug), or just plain does the wrong thing. Once a given package shows a particular problem, the problem is the same every time that package fails, and there is usually only one problem.

It is known to us and some big customers that you need to shut down dev studio and reload your project to get things to work again.

The size and/or complexity of the work does not seem to matter either.
We have simple flows with one src and one dest that moves 10000 rows, all the way to massive, multi-pronged flows with multiple sources, lookups, and millions of records.
They all eventually fail. Once you get the first failure, all others on that package will be of the same nature.

Its odd.

I've not observed this in my packages. So are you here with a question, or just posting your experience? There are so many things that influence package execution, and until you are sure you have a perfect environment, I wouldn't take your post with too much credit.|||

Hm... After my last post error occured only once.

I didn't do anything from my last post. Also admins on server didn't do anything...

Is server has to get used to these packages to run well?

BR
ZigaP

Error loading package

Could some one please help me with this problem... After working with the Rational Guide To Scripting SSIS Beta Preview (Donald Farmer), chapter 6 Adv uses of the Script Task.. For some reason I cannot open or create any packages now... Here's a sample of the error message:

"There were errors while the package was being loaded. The package might be corrupted. Se the error-list for details" This came with an OK-button.

Error 1 - Error loading DataTransfer.dtsx: Unable to instantiate XML DOM document, please verify that MSML binaries are properly installed and registered.

Error 2 - Error loading DataTransfer.dtsx: Unable to load from XML

The Error-list has 6 errors and 2 warnings...

regards maggi

Please see this. I think it may be what you're seeing. RegSvr32 the xml dlls essentially fixes the problem.

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=74140&SiteID=1

Kirk Haselden
Author "SQL Server Integration Services"

Error loading package

Hi there all...

We've just started using SSIS packages, and everything seems to be going ok.

I've recently set up a couple of jobs which just run an SSIS package every 5 minutes to collect data.
These run fine 90% of the time, but intermittantly produce an error.

When using a SSIS task in the job it simply reported
"Could not load Package."

I have changed these to use DTExec as I heard it gave more verbose execution results, and now I get an error like
"Executed as user: NZ\SQLAdmin. Microsoft (R) SQL Server Execute Package Utility Version 9.00.1399.06 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 8:25:00 a.m. Could not load package "\MSDB\RadiusBilling\Get_RADIUS_AuthLog" because of error 0x80040E37. Description: Table/view either does not exist or contains errors. Source: Microsoft SQL Native Client Started: 8:25:00 a.m. Finished: 8:25:00 a.m. Elapsed: 0.047 seconds. Process Exit Code 5. The step failed."

So far I have not been able to find anyone else with similar errors.
Whenever the package executes it seems to run fine, so this seems to be an error just getting the package to execute in the first place, and as I said it only happens internittantly.

The packages talk to a SQL2005 server using windows authentication (which I assume is inherited from the SQLAgent service user), as well as a MySQL server through an ODBC connection.
The package is saved in the MSDB SSIS Package Store and uses the "Rely on Server for Security" option

Does anyone know why this is happening and how I can fix it?

disenfranchised wrote:

Hi there all...

We've just started using SSIS packages, and everything seems to be going ok.

I've recently set up a couple of jobs which just run an SSIS package every 5 minutes to collect data.
These run fine 90% of the time, but intermittantly produce an error.

When using a SSIS task in the job it simply reported
"Could not load Package."

I have changed these to use DTExec as I heard it gave more verbose execution results, and now I get an error like
"Executed as user: NZ\SQLAdmin. Microsoft (R) SQL Server Execute Package Utility Version 9.00.1399.06 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 8:25:00 a.m. Could not load package "\MSDB\RadiusBilling\Get_RADIUS_AuthLog" because of error 0x80040E37. Description: Table/view either does not exist or contains errors. Source: Microsoft SQL Native Client Started: 8:25:00 a.m. Finished: 8:25:00 a.m. Elapsed: 0.047 seconds. Process Exit Code 5. The step failed."

So far I have not been able to find anyone else with similar errors.
Whenever the package executes it seems to run fine, so this seems to be an error just getting the package to execute in the first place, and as I said it only happens internittantly.

The packages talk to a SQL2005 server using windows authentication (which I assume is inherited from the SQLAgent service user), as well as a MySQL server through an ODBC connection.
The package is saved in the MSDB SSIS Package Store and uses the "Rely on Server for Security" option

Does anyone know why this is happening and how I can fix it?

So you say it fails intermittently? Well that's weird.

Its failing because it cannot validate one of its external data sources. The fact that its intermittent leads me to suggest that there is some outside influence that is causing this. network connectivity perhaps? I'm just speculating here.

-Jamie

|||

I have suspected that it might be something to do with the permissions on the domain account that the SQLAgent runs as.

Something like the account was getting locked perhaps.

However if that was the case I'd expect to see 5-6 failures as the job runs every 5 minutes, and the domain keeps accounts locked for 30 minutes. We only ever seem to get isolated failures, but about 6 times per day (which out of 288 executions isn't to bad)

|||

Hi

I have the same problem with my SSIS packages.

I'm still developing the package so it isn't finished yet. But on each step I put it into production to see, how it behaves.

In adtition to you, I noticed, that this error occurs more often, when the package is stored in MSDB store. Previously I have had packages stored in SQL's FileSystem store and error occurs maybe twice or three times per week. Now it occurs several times per day.

I use the domain user and id in Administators group on the server.

I execute the package on the server where the inserting database is.

I execute the package every minute.

BR

ZigaP

|||Again, it sounds like an intermittent connectivity issue.|||

I think the network connectivity is not an issue.

It cannot be, because I run packages on the server where the database is.

what about this: if I replace the name of the server with "(local)"... can this solve the problem?

|||My company develops SSIS components.
No matter what you think or what you are told, I can tell you that most parts of SSIS only run about 90% of the time when you execute packages from the 'Business Intelligence Development Studio' (VS2005 really)
We actually have a problem right now because we do not have any test cases which will run 100% of the time if you let them run for a day.
Most things seem to work if you keep testing to less than an hour, but anymore and you will eventually hit a failure.

Oddly, the problem only occurs at the package level. We have not seen a package or flow that dies in the middle, or in different places, or anything variable.
It either runs to success, dies upon startup (by any means, scheduled, manual, debug), or just plain does the wrong thing. Once a given package shows a particular problem, the problem is the same every time that package fails, and there is usually only one problem.

It is known to us and some big customers that you need to shut down dev studio and reload your project to get things to work again.

The size and/or complexity of the work does not seem to matter either.
We have simple flows with one src and one dest that moves 10000 rows, all the way to massive, multi-pronged flows with multiple sources, lookups, and millions of records.
They all eventually fail. Once you get the first failure, all others on that package will be of the same nature.

Its odd.|||

FarmerChet wrote:

My company develops SSIS components.
No matter what you think or what you are told, I can tell you that most parts of SSIS only run about 90% of the time when you execute packages from the 'Business Intelligence Development Studio' (VS2005 really)
We actually have a problem right now because we do not have any test cases which will run 100% of the time if you let them run for a day.
Most things seem to work if you keep testing to less than an hour, but anymore and you will eventually hit a failure.

Oddly, the problem only occurs at the package level. We have not seen a package or flow that dies in the middle, or in different places, or anything variable.
It either runs to success, dies upon startup (by any means, scheduled, manual, debug), or just plain does the wrong thing. Once a given package shows a particular problem, the problem is the same every time that package fails, and there is usually only one problem.

It is known to us and some big customers that you need to shut down dev studio and reload your project to get things to work again.

The size and/or complexity of the work does not seem to matter either.
We have simple flows with one src and one dest that moves 10000 rows, all the way to massive, multi-pronged flows with multiple sources, lookups, and millions of records.
They all eventually fail. Once you get the first failure, all others on that package will be of the same nature.

Its odd.

I've not observed this in my packages. So are you here with a question, or just posting your experience? There are so many things that influence package execution, and until you are sure you have a perfect environment, I wouldn't take your post with too much credit.|||

Hm... After my last post error occured only once.

I didn't do anything from my last post. Also admins on server didn't do anything...

Is server has to get used to these packages to run well?

BR
ZigaP

Error loading package

Hi there all...

We've just started using SSIS packages, and everything seems to be going ok.

I've recently set up a couple of jobs which just run an SSIS package every 5 minutes to collect data.
These run fine 90% of the time, but intermittantly produce an error.

When using a SSIS task in the job it simply reported
"Could not load Package."

I have changed these to use DTExec as I heard it gave more verbose execution results, and now I get an error like
"Executed as user: NZ\SQLAdmin. Microsoft (R) SQL Server Execute Package Utility Version 9.00.1399.06 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 8:25:00 a.m. Could not load package "\MSDB\RadiusBilling\Get_RADIUS_AuthLog" because of error 0x80040E37. Description: Table/view either does not exist or contains errors. Source: Microsoft SQL Native Client Started: 8:25:00 a.m. Finished: 8:25:00 a.m. Elapsed: 0.047 seconds. Process Exit Code 5. The step failed."

So far I have not been able to find anyone else with similar errors.
Whenever the package executes it seems to run fine, so this seems to be an error just getting the package to execute in the first place, and as I said it only happens internittantly.

The packages talk to a SQL2005 server using windows authentication (which I assume is inherited from the SQLAgent service user), as well as a MySQL server through an ODBC connection.
The package is saved in the MSDB SSIS Package Store and uses the "Rely on Server for Security" option

Does anyone know why this is happening and how I can fix it?

disenfranchised wrote:

Hi there all...

We've just started using SSIS packages, and everything seems to be going ok.

I've recently set up a couple of jobs which just run an SSIS package every 5 minutes to collect data.
These run fine 90% of the time, but intermittantly produce an error.

When using a SSIS task in the job it simply reported
"Could not load Package."

I have changed these to use DTExec as I heard it gave more verbose execution results, and now I get an error like
"Executed as user: NZ\SQLAdmin. Microsoft (R) SQL Server Execute Package Utility Version 9.00.1399.06 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 8:25:00 a.m. Could not load package "\MSDB\RadiusBilling\Get_RADIUS_AuthLog" because of error 0x80040E37. Description: Table/view either does not exist or contains errors. Source: Microsoft SQL Native Client Started: 8:25:00 a.m. Finished: 8:25:00 a.m. Elapsed: 0.047 seconds. Process Exit Code 5. The step failed."

So far I have not been able to find anyone else with similar errors.
Whenever the package executes it seems to run fine, so this seems to be an error just getting the package to execute in the first place, and as I said it only happens internittantly.

The packages talk to a SQL2005 server using windows authentication (which I assume is inherited from the SQLAgent service user), as well as a MySQL server through an ODBC connection.
The package is saved in the MSDB SSIS Package Store and uses the "Rely on Server for Security" option

Does anyone know why this is happening and how I can fix it?

So you say it fails intermittently? Well that's weird.

Its failing because it cannot validate one of its external data sources. The fact that its intermittent leads me to suggest that there is some outside influence that is causing this. network connectivity perhaps? I'm just speculating here.

-Jamie

|||

I have suspected that it might be something to do with the permissions on the domain account that the SQLAgent runs as.

Something like the account was getting locked perhaps.

However if that was the case I'd expect to see 5-6 failures as the job runs every 5 minutes, and the domain keeps accounts locked for 30 minutes. We only ever seem to get isolated failures, but about 6 times per day (which out of 288 executions isn't to bad)

|||

Hi

I have the same problem with my SSIS packages.

I'm still developing the package so it isn't finished yet. But on each step I put it into production to see, how it behaves.

In adtition to you, I noticed, that this error occurs more often, when the package is stored in MSDB store. Previously I have had packages stored in SQL's FileSystem store and error occurs maybe twice or three times per week. Now it occurs several times per day.

I use the domain user and id in Administators group on the server.

I execute the package on the server where the inserting database is.

I execute the package every minute.

BR

ZigaP

|||Again, it sounds like an intermittent connectivity issue.|||

I think the network connectivity is not an issue.

It cannot be, because I run packages on the server where the database is.

what about this: if I replace the name of the server with "(local)"... can this solve the problem?

|||My company develops SSIS components.
No matter what you think or what you are told, I can tell you that most parts of SSIS only run about 90% of the time when you execute packages from the 'Business Intelligence Development Studio' (VS2005 really)
We actually have a problem right now because we do not have any test cases which will run 100% of the time if you let them run for a day.
Most things seem to work if you keep testing to less than an hour, but anymore and you will eventually hit a failure.

Oddly, the problem only occurs at the package level. We have not seen a package or flow that dies in the middle, or in different places, or anything variable.
It either runs to success, dies upon startup (by any means, scheduled, manual, debug), or just plain does the wrong thing. Once a given package shows a particular problem, the problem is the same every time that package fails, and there is usually only one problem.

It is known to us and some big customers that you need to shut down dev studio and reload your project to get things to work again.

The size and/or complexity of the work does not seem to matter either.
We have simple flows with one src and one dest that moves 10000 rows, all the way to massive, multi-pronged flows with multiple sources, lookups, and millions of records.
They all eventually fail. Once you get the first failure, all others on that package will be of the same nature.

Its odd.
|||

FarmerChet wrote:

My company develops SSIS components.
No matter what you think or what you are told, I can tell you that most parts of SSIS only run about 90% of the time when you execute packages from the 'Business Intelligence Development Studio' (VS2005 really)
We actually have a problem right now because we do not have any test cases which will run 100% of the time if you let them run for a day.
Most things seem to work if you keep testing to less than an hour, but anymore and you will eventually hit a failure.

Oddly, the problem only occurs at the package level. We have not seen a package or flow that dies in the middle, or in different places, or anything variable.
It either runs to success, dies upon startup (by any means, scheduled, manual, debug), or just plain does the wrong thing. Once a given package shows a particular problem, the problem is the same every time that package fails, and there is usually only one problem.

It is known to us and some big customers that you need to shut down dev studio and reload your project to get things to work again.

The size and/or complexity of the work does not seem to matter either.
We have simple flows with one src and one dest that moves 10000 rows, all the way to massive, multi-pronged flows with multiple sources, lookups, and millions of records.
They all eventually fail. Once you get the first failure, all others on that package will be of the same nature.

Its odd.

I've not observed this in my packages. So are you here with a question, or just posting your experience? There are so many things that influence package execution, and until you are sure you have a perfect environment, I wouldn't take your post with too much credit.|||

Hm... After my last post error occured only once.

I didn't do anything from my last post. Also admins on server didn't do anything...

Is server has to get used to these packages to run well?

BR
ZigaP

sql

Error loading Oracle DATE data

Hello.

I'm trying to put in an SQL server database some data extracted from Oracle Server 9i.

During the load process, the "OLE DB Destination" in the task chokes up when it finds a record containing the date '0197-01-01 00:00:00' (i got this by putting the error output to a column of type varchar(50)). I can't use the Condicional Split's date functions to filter this out because they also choke on the strange date.

Can anyone give a sugestion?

Thanks in advance,

Hugo Oliveira

SQL will not recognize that as a date. Valid ranges for a datetime column are January 1, 1753, through December 31, 9999. If you want to filter it out use the error output like you're doing.|||

Hello Brent.

I gess the error output is the only solution. Just wondering if there was another one.

Thanks,

Hugo Oliveira

|||

You could treat the value as a string, test it to see if its a valid date and if it is is, cast it as a date.

Those that are not a valid date - its up to you what you do with them. You could discard them or replace the value with a default.

-Jamie

Error loading metadata....PLZZ HELP!!

My Analysis Service has this strange errors....

My Calculation tabs, KPI tabs, Action tabs....all showing this error message at it's Calculation Tools metadata tab....

"Error loading metadata: The cube could not be retrieved from the server. Verify that the server is running and that cube is processed."

previously i even had the problem of running the script organizer for the Calculation tabs.....after installing the SP2, it's fixed, but the metadata error still there.....

i tried on my friends PC and it works fine and deploy successfully whereas mine cannot at all with all kind of errors.....

Hello. I would recommend you to uninstall BIDS on you machine and reinstall it again with SP2.

Since you have a deployed cube you can always reverse engineer it to a project in BIDS when it is working.

Regards

Thomas Ivarsson

Error loading 'IntegrationServicesRules' assembly in Best Practice Analyzer 2005 CTP

Hi,

I get the following error when trying to scan *.dtsx files in Best Practice Analyzer 2005 CTP:

15:47:02.609: Could not load file or assembly 'IntegrationServicesRules, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

Does a fix/workaround for this error exist?

Also, the BPA 2005 CTP seems to have problems with internet updating.

Thanks in advance,

Niels

What version of SQL Server are you running?
What version of Windows are you running?
Do you have the client tools installed on the same machine as SQL Server 2005 BPA?

Paul A. Mestemaker II
Program Manager
Microsoft SQL Server Manageability
http://blogs.msdn.com/sqlrem/

|||

SQL Server 2005 on XP SP2 - more version details below:

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 6.0.2900.2180
Microsoft .NET Framework 2.0.50727.42
Operating System 5.1.2600

The client tools are installed on the same machine as BPA 2005 CTP.

|||

We have confirmed this to be a bug in the CTP release. Thanks for reporting this. It has been fixed in the next release. We will be shipping the next version within the next 6 weeks.

Paul A. Mestemaker II
Program Manager
Microsoft SQL Server Manageability
http://blogs.msdn.com/sqlrem/

Error loading http://localhost/ReportServer

Hi!

I've installed the Report Server but when I try to go to http://localhost/ReportServer I get the following error:

Reporting Services Error

An internal error occurred on the report server. See the error log for more details. (rsInternalError)

And the log in the c:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\LogFiles\SQLDUMPER_ERRORLOG.log file is this:

12/01/06 12:51:40, ERROR , SQLDUMPER_UNKNOWN_APP.EXE, AdjustTokenPrivileges () failed (00000514)
12/01/06 12:51:40, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4 supplied
12/01/06 12:51:40, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ProcessID = 5344
12/01/06 12:51:40, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ThreadId = 0
12/01/06 12:51:40, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Flags = 0x0
12/01/06 12:51:40, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDumpFlags = 0x0
12/01/06 12:51:40, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, SqlInfoPtr = 0x0A0F2A04
12/01/06 12:51:40, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, DumpDir = <NULL>
12/01/06 12:51:40, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExceptionRecordPtr = 0x00000000
12/01/06 12:51:40, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ContextPtr = 0x00000000
12/01/06 12:51:40, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExtraFile = <NULL>
12/01/06 12:51:40, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, InstanceName = <NULL>
12/01/06 12:51:40, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ServiceName = <NULL>
12/01/06 12:51:40, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not used
12/01/06 12:51:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not used
12/01/06 12:51:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed: C:\Archivos de programa\Microsoft SQL Server\MSSQL.3\Reporting Services\LogFiles\SQLDmpr0058.mdmp
12/01/06 12:51:42, ACTION, aspnet_wp.exe, Watson Invoke: No

Does anybody have which could be the problem?

Thanks in advance! :)

Tomas,

I have the exact same problem. Did you ever solve your problem?

|||

Hi Chuck,

Yes, I solved this problem deleting from the web.config (folders ReportServer and/or ReportManaget) this:

xmlns=http://schemas.microsoft.com/.NetConfiguration/v2.0

If you have more problems (I had :) ) tell me and I'll try to help you: eltommy@.gmail.com

Good luck!!!

|||

Hi Tomás

I′m having the same problem

When I go to Initialization in Configure Reporting Server the error is :

There was an error while switching panels. The most likely cause is an error retrieving VMI properties. The exceptions details are:

An internal error occurred on the report server. See the error log for more details. (rsInternalError)

I didn′t found the line that you mentioned

Bellow is my web.config. I tried to erase :xmlns="urn:schemas-microsoft-com:asm.v1, but I haven′t success.

Thanks in advance

Consuelo

<?xml version="1.0" encoding="utf-8"?>
<configuration>
<configSections>
<section name="MicrosoftWebControls" type="System.Configuration.NameValueSectionHandler, System, Version=2.0.3600.0, Culture=neutral, PublicKeyToken=b77a5c561934e089, processorArchitecture=MSIL"/>
<section name="RStrace" type="Microsoft.ReportingServices.Diagnostics.RSTraceSectionHandler,Microsoft.ReportingServices.Diagnostics"/>
<section name="UIConfig" type="Microsoft.ReportingServices.UI.UIConfigSectionHandler,ReportingServicesWebUserInterface"/>
</configSections>
<system.net>
<defaultProxy enabled="false"/>
</system.net>
<system.web>
<pages validateRequest="false"/>
<compilation defaultLanguage="c#" debug="false"/>
<customErrors mode="Off"/>
<authentication mode="Windows"/>
<identity impersonate="true"/>
<trace enabled="false" requestLimit="10" pageOutput="false" traceMode="SortByTime" localOnly="true"/>
<sessionState mode="InProc" cookieless="false" timeout="20"/>
<globalization requestEncoding="utf-8" responseEncoding="utf-8"/>
<httpRuntime executionTimeout="9000"/>
<securityPolicy>
<trustLevel name="RosettaMgr" policyFile="rsmgrpolicy.config"/>
</securityPolicy>
<trust level="RosettaMgr" originUrl=""/>
<httpHandlers>
<add verb="*" path="Reserved.ReportViewerWebControl.axd" type="Microsoft.Reporting.WebForms.HttpHandler, ReportingServicesWebUserInterface, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91"/>
</httpHandlers>
</system.web>
<appSettings>
<add key="ReportViewerServerConnection" value="Microsoft.ReportingServices.UI.WebControlConnection, ReportingServicesWebUserInterface, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91"/>
<add key="ReportViewerTemporaryStorage" value="Microsoft.ReportingServices.UI.ReportViewerTemporaryStorage, ReportingServicesWebUserInterface, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91"/>
</appSettings>
<RStrace>
<add name="FileName" value="ReportServerWebApp_"/>
<add name="Prefix" value="tid, time"/>
<add name="TraceListeners" value="debugwindow, file"/>
<add name="TraceFileMode" value="unique"/>
<add name="Components" value="all"/>
</RStrace>
<system.diagnostics>
<switches>
<!-- 1 = error, 2 = warning, 3 = info, 4 = verbose -->
<add name="DefaultTraceSwitch" value="3"/>
</switches>
</system.diagnostics>
<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="Microsoft.ReportingServices.Interfaces" publicKeyToken="89845dcd8080cc91" culture="neutral"/>
<bindingRedirect oldVersion="8.0.242.0" newVersion="9.0.242.0"/>
</dependentAssembly>
</assemblyBinding>
</runtime>
</configuration>

|||

I found a solution

I was with SQL SERVER 2000 and 2005 installed. I desinstalled both and erased ReportServer and Reports folders in IIS, after that installed just SQL SERVER 2005. Now it′s ok.

|||I'm very happy about you Consuelo, this kind of issues are very stressing and in your case it was difficult to find the solution. Congratulations!!! :)sql

Error loading http://localhost/ReportServer

Hi!

I've installed the Report Server but when I try to go to http://localhost/ReportServer I get the following error:

Reporting Services Error

An internal error occurred on the report server. See the error log for more details. (rsInternalError)

And the log in the c:\Program Files\Microsoft SQL Server\MSSQL.3\Reporting Services\LogFiles\SQLDUMPER_ERRORLOG.log file is this:

12/01/06 12:51:40, ERROR , SQLDUMPER_UNKNOWN_APP.EXE, AdjustTokenPrivileges () failed (00000514)
12/01/06 12:51:40, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Input parameters: 4 supplied
12/01/06 12:51:40, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ProcessID = 5344
12/01/06 12:51:40, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ThreadId = 0
12/01/06 12:51:40, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Flags = 0x0
12/01/06 12:51:40, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDumpFlags = 0x0
12/01/06 12:51:40, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, SqlInfoPtr = 0x0A0F2A04
12/01/06 12:51:40, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, DumpDir = <NULL>
12/01/06 12:51:40, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExceptionRecordPtr = 0x00000000
12/01/06 12:51:40, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ContextPtr = 0x00000000
12/01/06 12:51:40, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ExtraFile = <NULL>
12/01/06 12:51:40, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, InstanceName = <NULL>
12/01/06 12:51:40, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, ServiceName = <NULL>
12/01/06 12:51:40, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 11 not used
12/01/06 12:51:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, Callback type 7 not used
12/01/06 12:51:42, ACTION, SQLDUMPER_UNKNOWN_APP.EXE, MiniDump completed: C:\Archivos de programa\Microsoft SQL Server\MSSQL.3\Reporting Services\LogFiles\SQLDmpr0058.mdmp
12/01/06 12:51:42, ACTION, aspnet_wp.exe, Watson Invoke: No

Does anybody have which could be the problem?

Thanks in advance! :)

Tomas,

I have the exact same problem. Did you ever solve your problem?

|||

Hi Chuck,

Yes, I solved this problem deleting from the web.config (folders ReportServer and/or ReportManaget) this:

xmlns=http://schemas.microsoft.com/.NetConfiguration/v2.0

If you have more problems (I had :) ) tell me and I'll try to help you: eltommy@.gmail.com

Good luck!!!

|||

Hi Tomás

I′m having the same problem

When I go to Initialization in Configure Reporting Server the error is :

There was an error while switching panels. The most likely cause is an error retrieving VMI properties. The exceptions details are:

An internal error occurred on the report server. See the error log for more details. (rsInternalError)

I didn′t found the line that you mentioned

Bellow is my web.config. I tried to erase :xmlns="urn:schemas-microsoft-com:asm.v1, but I haven′t success.

Thanks in advance

Consuelo

<?xml version="1.0" encoding="utf-8"?>
<configuration>
<configSections>
<section name="MicrosoftWebControls" type="System.Configuration.NameValueSectionHandler, System, Version=2.0.3600.0, Culture=neutral, PublicKeyToken=b77a5c561934e089, processorArchitecture=MSIL"/>
<section name="RStrace" type="Microsoft.ReportingServices.Diagnostics.RSTraceSectionHandler,Microsoft.ReportingServices.Diagnostics"/>
<section name="UIConfig" type="Microsoft.ReportingServices.UI.UIConfigSectionHandler,ReportingServicesWebUserInterface"/>
</configSections>
<system.net>
<defaultProxy enabled="false"/>
</system.net>
<system.web>
<pages validateRequest="false"/>
<compilation defaultLanguage="c#" debug="false"/>
<customErrors mode="Off"/>
<authentication mode="Windows"/>
<identity impersonate="true"/>
<trace enabled="false" requestLimit="10" pageOutput="false" traceMode="SortByTime" localOnly="true"/>
<sessionState mode="InProc" cookieless="false" timeout="20"/>
<globalization requestEncoding="utf-8" responseEncoding="utf-8"/>
<httpRuntime executionTimeout="9000"/>
<securityPolicy>
<trustLevel name="RosettaMgr" policyFile="rsmgrpolicy.config"/>
</securityPolicy>
<trust level="RosettaMgr" originUrl=""/>
<httpHandlers>
<add verb="*" path="Reserved.ReportViewerWebControl.axd" type="Microsoft.Reporting.WebForms.HttpHandler, ReportingServicesWebUserInterface, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91"/>
</httpHandlers>
</system.web>
<appSettings>
<add key="ReportViewerServerConnection" value="Microsoft.ReportingServices.UI.WebControlConnection, ReportingServicesWebUserInterface, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91"/>
<add key="ReportViewerTemporaryStorage" value="Microsoft.ReportingServices.UI.ReportViewerTemporaryStorage, ReportingServicesWebUserInterface, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91"/>
</appSettings>
<RStrace>
<add name="FileName" value="ReportServerWebApp_"/>
<add name="Prefix" value="tid, time"/>
<add name="TraceListeners" value="debugwindow, file"/>
<add name="TraceFileMode" value="unique"/>
<add name="Components" value="all"/>
</RStrace>
<system.diagnostics>
<switches>
<!-- 1 = error, 2 = warning, 3 = info, 4 = verbose -->
<add name="DefaultTraceSwitch" value="3"/>
</switches>
</system.diagnostics>
<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<dependentAssembly>
<assemblyIdentity name="Microsoft.ReportingServices.Interfaces" publicKeyToken="89845dcd8080cc91" culture="neutral"/>
<bindingRedirect oldVersion="8.0.242.0" newVersion="9.0.242.0"/>
</dependentAssembly>
</assemblyBinding>
</runtime>
</configuration>

|||

I found a solution

I was with SQL SERVER 2000 and 2005 installed. I desinstalled both and erased ReportServer and Reports folders in IIS, after that installed just SQL SERVER 2005. Now it′s ok.

|||I'm very happy about you Consuelo, this kind of issues are very stressing and in your case it was difficult to find the solution. Congratulations!!! :)

Error loading file to SQL Server 2005

I am trying to load a text file into SQL Server 2005 and I get the following
error messages at the validation stage:
Messages
?Error 0xc00470fe: Data Flow Task: The product level is insufficient for
component "Source - A00U3UNN_Y2006014_FAD_1_VDF" (1).
(SQL Server Import and Export Wizard)
?Error 0xc00470fe: Data Flow Task: The product level is insufficient for
component "Data Conversion 1" (31).
(SQL Server Import and Export Wizard)
Does anyone know what product level is insufficient?
Is the compatibility level of the database you are inserting into not at 90?
Are you using DTS or SSIS?
Andrew J. Kelly SQL MVP
"Robin" <Robin@.discussions.microsoft.com> wrote in message
news:E4E163EE-8A30-418B-8255-26A2EA155C1C@.microsoft.com...
>I am trying to load a text file into SQL Server 2005 and I get the
>following
> error messages at the validation stage:
> Messages
> . Error 0xc00470fe: Data Flow Task: The product level is insufficient for
> component "Source - A00U3UNN_Y2006014_FAD_1_VDF" (1).
> (SQL Server Import and Export Wizard)
> . Error 0xc00470fe: Data Flow Task: The product level is insufficient for
> component "Data Conversion 1" (31).
> (SQL Server Import and Export Wizard)
>
> Does anyone know what product level is insufficient?
>

Error Loading : sqlceme30.dll

Dear All,

Please let me know how I can overcome the following Error.

System.InvalidOperationException was unhandled
Message="An error occurred creating the form. See Exception.InnerException for details. The error is: Unable to load DLL 'sqlceme30.dll': The specified module could not be found. (Exception from HRESULT: 0x8007007E)"
Source="RDA_Dummy"
StackTrace:
at RDA_Dummy.My.MyProject.MyForms.Create__Instance__[T](T Instance) in 17d14f5c-a337-4978-8281-53493378c1071.vb:line 190
at RDA_Dummy.My.MyProject.MyForms.get_frmMain()
at RDA_Dummy.My.MyApplication.OnCreateMainForm() in C:\Test\My Project\Application.Designer.vb:line 35
at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.OnRun()
at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.DoApplicationModel()
at Microsoft.VisualBasic.ApplicationServices.WindowsFormsApplicationBase.Run(String[] commandLine)
at RDA_Dummy.My.MyApplication.Main(String[] Args) in 17d14f5c-a337-4978-8281-53493378c1071.vb:line 81
at System.AppDomain.nExecuteAssembly(Assembly assembly, String[] args)
at System.AppDomain.ExecuteAssembly(String assemblyFile, Evidence assemblySecurity, String[] args)
at Microsoft.VisualStudio.HostingProcess.HostProc.RunUsersAssembly()
at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()

Regards,

SEe this http://blogs.msdn.com/smartclientdata/archive/2005/07/15/439008.aspx blog is any help.|||

Hi,

Thank you for your respond... It was detailed enough.

However I am facing an issue on Deployment, so I submited this to Smart Device Forum. "Pls Refer below Link"

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1479438&SiteID=1

This gives me another answer, please assist me in this case.

THnakx

Error loading 'IntegrationServicesRules' assembly in Best Practice Analyzer 2005 CTP

Hi,

I get the following error when trying to scan *.dtsx files in Best Practice Analyzer 2005 CTP:

15:47:02.609: Could not load file or assembly 'IntegrationServicesRules, Version=1.0.0.0, Culture=neutral, PublicKeyToken=null' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)

Does a fix/workaround for this error exist?

Also, the BPA 2005 CTP seems to have problems with internet updating.

Thanks in advance,

Niels

What version of SQL Server are you running?
What version of Windows are you running?
Do you have the client tools installed on the same machine as SQL Server 2005 BPA?

Paul A. Mestemaker II
Program Manager
Microsoft SQL Server Manageability
http://blogs.msdn.com/sqlrem/

|||

SQL Server 2005 on XP SP2 - more version details below:

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 6.0.2900.2180
Microsoft .NET Framework 2.0.50727.42
Operating System 5.1.2600

The client tools are installed on the same machine as BPA 2005 CTP.

|||

We have confirmed this to be a bug in the CTP release. Thanks for reporting this. It has been fixed in the next release. We will be shipping the next version within the next 6 weeks.

Paul A. Mestemaker II
Program Manager
Microsoft SQL Server Manageability
http://blogs.msdn.com/sqlrem/

Error in loading RPT files

I need your help

Having these errors when my application is trying to load rpt files. On my workstation it works perfectly but after I create a setup and install it on another machine i get these errors.

VB6 + CR 9.2 + Visual studio Package and Deployment.

The instruction at "0x7c93426d" referenced memory at "0x00000000". The memory could not be "read".

The instruction at "0x3b48b401" referenced memory at "0x03d4b000". The memory could not be "written".

Dim Crapp As New CRAXDDRT.Application
Dim oReport As New CRAXDDRT.Report

Set Crapp = New CRAXDDRT.Application
Set oReport = New CRAXDDRT.Report

PFld = Trim(Text1.Text)

oReport.DiscardSavedData
oReport.EnableParameterPrompting = False

'Set oReport = crApp.OpenReport(App.Path & "\" & RptPath)
oReport.ParameterFields(1).AddCurrentValue PFld

oReport.ReadRecords

Me.MousePointer = vbHourglass
With Form2.CRViewer91

.ReportSource = oReport
.ViewReport
.Refresh
End With

set crapp = nothing
set oreport = nothing

Me.MousePointer = vbArrow
Unload Me
Form2.ShowAnyone Please I need your help.

Please.

ERROR in loading data to DB2 from AS400

Hi,

I have a problem loading data from a flat file into a DB2 Dtabase by using the OLE DB Provider for DB2.

I read the data from a flat file in the unicode format and as soon as the data is to be written in the DB2 database the following error occurs and the loading process is aborted:

Information: 0x402090DE at Data Flow Task, Flat File Source [813]: The total number of data rows processed for file "C:\Dokumente und Einstellungen\Administrator\Desktop\SSIS1.txt" is 2.
Error: 0xC0202009 at Data Flow Task, OLE DB Destination [842]: An OLE DB error has occurred. Error code: 0x80040E53.
Error: 0xC0047022 at Data Flow Task, DTS.Pipeline: The ProcessInput method on component "OLE DB Destination" (842) failed with error code 0xC0202009. The identified component returned an error from the ProcessInput method. The error is specific to the component, but the error is fatal and will cause the Data Flow task to stop running.
Error: 0xC0047021 at Data Flow Task, DTS.Pipeline: Thread "WorkThread0" has exited with error code 0xC0202009.
Information: 0x40043008 at Data Flow Task, DTS.Pipeline: Post Execute phase is beginning.......

......Warning: 0x80019002 at Package: The Execution method succeeded, but the number of errors raised (3) reached the maximum allowed (1); resulting in failure. This occurs when the number of errors reaches the number specified in MaximumErrorCount. Change the MaximumErrorCount or fix the errors.
SSIS package "Package 1.dtsx" finished: Failure.

I dont know waht those error codes meanand I tried so many things already. The tables in the database are created correctly and also, SSIS can read the data from the database if I use the preview function, but somehow, the program never starts to write data into the database for some reason. Can anyone help me?

Thx, andy

It looks like some other have had similar problems using the OLE DB Source with DB2.

One

user fixed the problem but using a DataReader source and an ODBC

connection to DB2 (see this post:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=250370&SiteID=1)

Another

user seems to have fixed it by restarting the Distributed Transaction

Coordinator service although he was using beta 2 of SQL Server. See

here: http://www.ureader.com/message/287061.aspx

Hope this helps.

Jason|||Hi,

I'm Facing almost similar kind of problem.
Got to load data to DB2 data base taken from AS400.

I'm using dataReader ( ADO .Net connection (ODBC connection did not work, its a work around to fetch data)) to fetch data from AS400 Server and trying to load it to a DB2 datbase ( OLEDB conection manager - using IBM OLEDB provider for DB2)

>> Is there a compatibility issue with DataReader Source and OLEDB destination ?
>> Any other alternative in that case?

PLZ help !!!!!!!!!!

Here is the ERROR Message i get on execution:

Error: 0xC0202009 at Data Reader to DB2, OLE DB Destination [12]: An OLE DB error has occurred. Error code: 0x80040E53.

Error: 0xC0047022 at Data Reader to

DB2, DTS.Pipeline: The ProcessInput method on component "OLE DB

Destination" (12) failed with error code 0xC0202009. The identified

component returned an error from the ProcessInput method. The error is

specific to the component, but the error is fatal and will cause the

Data Flow task to stop running.

Error: 0xC0047021 at Data Reader to DB2, DTS.Pipeline: Thread "WorkThread0" has exited with error code 0xC0202009.

Information: 0x4004300B at Data Reader to DB2, DTS.Pipeline: "component "OLE DB Destination" (12)" wrote 0 rows.

Task failed: Data Reader to DB2

SSIS package "Package.dtsx" finished: Success.