Error 14266 - Is 11:59:59 PM not a valid time?

Hi,
I created a DTS package and wanted to schedule it to run at 11:59:59 PM. I
could not save the schedule.
An error "Error 14266: The specified '@.active_end_time' is invalid (valid
values are: before or after @.active_start_time). The job was not saved."
I tried 11:59:58 PM and 12:00:00 AM, both schedules can be saved. Why
11:59:59 PM not ?
Please help,
It sounds like this is from what you are selecting in the
daily frequency section when you schedule the job.
Without the details of this, I'd guess you are selecting
something like "occurs every 24 hours" with "starting at
11:59:59 PM" and "ending at 11:59:59 PM". That will give the
error you have.
If you want the job to run daily at 11:59:59 PM, select the
"occurs once at " option (the first one in the daily
frequency section). It will run once a day (or at whatever
interval you have set or want set in the Occurs section) at
11:59:59 PM.
-Sue
On Thu, 20 Jan 2005 09:03:09 -0800, "Julia"
<Julia@.discussions.microsoft.com> wrote:

>Hi,
>I created a DTS package and wanted to schedule it to run at 11:59:59 PM. I
>could not save the schedule.
>An error "Error 14266: The specified '@.active_end_time' is invalid (valid
>values are: before or after @.active_start_time). The job was not saved."
>I tried 11:59:58 PM and 12:00:00 AM, both schedules can be saved. Why
>11:59:59 PM not ?
>Please help,
|||Selecting "Occurrs Once At:" with a time of 11:59:59 PM will not work.
The scheduling wizard assumes that the end time is 11:59:59 PM. This is
why you get the error 14266. Enter any other time and it will work.
You can easily verify this by entering a different time and saving it.
Then right click on the associated job. Select "All Tasks > Generate
SQL Script...
A dialog box will appear "Generate SQL Script - SERVER NAME/JOB NAME"
Click on the preview button. Click on the copy button and paste into a
text editor. Search for "@.active_end_time"
you will see that it is set to 235959.
Sue Hoegemeier Wrote:[vbcol=seagreen]
> It sounds like this is from what you are selecting in the
> daily frequency section when you schedule the job.
> Without the details of this, I'd guess you are selecting
> something like "occurs every 24 hours" with "starting at
> 11:59:59 PM" and "ending at 11:59:59 PM". That will give the
> error you have.
> If you want the job to run daily at 11:59:59 PM, select the
> "occurs once at " option (the first one in the daily
> frequency section). It will run once a day (or at whatever
> interval you have set or want set in the Occurs section) at
> 11:59:59 PM.
> -Sue
> On Thu, 20 Jan 2005 09:03:09 -0800, "Julia"
> <Julia@.discussions.microsoft.com> wrote:
> PM. I
> (valid
> saved."
bdatch
bdatch's Profile: http://www.msusenet.com/member.php?userid=675
View this thread: http://www.msusenet.com/t-3298150

Error 14266 - Is 11:59:59 PM not a valid time?

Hi,
I created a DTS package and wanted to schedule it to run at 11:59:59 PM. I
could not save the schedule.
An error "Error 14266: The specified '@.active_end_time' is invalid (valid
values are: before or after @.active_start_time). The job was not saved."
I tried 11:59:58 PM and 12:00:00 AM, both schedules can be saved. Why
11:59:59 PM not ?
Please help,It sounds like this is from what you are selecting in the
daily frequency section when you schedule the job.
Without the details of this, I'd guess you are selecting
something like "occurs every 24 hours" with "starting at
11:59:59 PM" and "ending at 11:59:59 PM". That will give the
error you have.
If you want the job to run daily at 11:59:59 PM, select the
"occurs once at " option (the first one in the daily
frequency section). It will run once a day (or at whatever
interval you have set or want set in the Occurs section) at
11:59:59 PM.
-Sue
On Thu, 20 Jan 2005 09:03:09 -0800, "Julia"
<Julia@.discussions.microsoft.com> wrote:

>Hi,
>I created a DTS package and wanted to schedule it to run at 11:59:59 PM. I
>could not save the schedule.
>An error "Error 14266: The specified '@.active_end_time' is invalid (valid
>values are: before or after @.active_start_time). The job was not saved."
>I tried 11:59:58 PM and 12:00:00 AM, both schedules can be saved. Why
>11:59:59 PM not ?
>Please help,|||Selecting "Occurrs Once At:" with a time of 11:59:59 PM will not work.
The scheduling wizard assumes that the end time is 11:59:59 PM. This is
why you get the error 14266. Enter any other time and it will work.
You can easily verify this by entering a different time and saving it.
Then right click on the associated job. Select "All Tasks > Generate
SQL Script...
A dialog box will appear "Generate SQL Script - SERVER NAME/JOB NAME"
Click on the preview button. Click on the copy button and paste into a
text editor. Search for "@.active_end_time"
you will see that it is set to 235959.
Sue Hoegemeier Wrote:[vbcol=seagreen]
> It sounds like this is from what you are selecting in the
> daily frequency section when you schedule the job.
> Without the details of this, I'd guess you are selecting
> something like "occurs every 24 hours" with "starting at
> 11:59:59 PM" and "ending at 11:59:59 PM". That will give the
> error you have.
> If you want the job to run daily at 11:59:59 PM, select the
> "occurs once at " option (the first one in the daily
> frequency section). It will run once a day (or at whatever
> interval you have set or want set in the Occurs section) at
> 11:59:59 PM.
> -Sue
> On Thu, 20 Jan 2005 09:03:09 -0800, "Julia"
> <Julia@.discussions.microsoft.com> wrote:
>
> PM. I
> (valid
> saved."
bdatch
---
bdatch's Profile: http://www.msmcse.ms/member.php?userid=675
View this thread: http://www.msmcse.ms/t-3298150

Error 14266 - Is 11:59:59 PM not a valid time?

Hi,
I created a DTS package and wanted to schedule it to run at 11:59:59 PM. I
could not save the schedule.
An error "Error 14266: The specified '@.active_end_time' is invalid (valid
values are: before or after @.active_start_time). The job was not saved."
I tried 11:59:58 PM and 12:00:00 AM, both schedules can be saved. Why
11:59:59 PM not ?
Please help,It sounds like this is from what you are selecting in the
daily frequency section when you schedule the job.
Without the details of this, I'd guess you are selecting
something like "occurs every 24 hours" with "starting at
11:59:59 PM" and "ending at 11:59:59 PM". That will give the
error you have.
If you want the job to run daily at 11:59:59 PM, select the
"occurs once at " option (the first one in the daily
frequency section). It will run once a day (or at whatever
interval you have set or want set in the Occurs section) at
11:59:59 PM.
-Sue
On Thu, 20 Jan 2005 09:03:09 -0800, "Julia"
<Julia@.discussions.microsoft.com> wrote:
>Hi,
>I created a DTS package and wanted to schedule it to run at 11:59:59 PM. I
>could not save the schedule.
>An error "Error 14266: The specified '@.active_end_time' is invalid (valid
>values are: before or after @.active_start_time). The job was not saved."
>I tried 11:59:58 PM and 12:00:00 AM, both schedules can be saved. Why
>11:59:59 PM not ?
>Please help,|||Selecting "Occurrs Once At:" with a time of 11:59:59 PM will not work
The scheduling wizard assumes that the end time is 11:59:59 PM. This i
why you get the error 14266. Enter any other time and it will work.
You can easily verify this by entering a different time and saving it
Then right click on the associated job. Select "All Tasks > Generat
SQL Script...
A dialog box will appear "Generate SQL Script - SERVER NAME/JOB NAME"
Click on the preview button. Click on the copy button and paste into
text editor. Search for "@.active_end_time"
you will see that it is set to 235959.
Sue Hoegemeier Wrote:
> It sounds like this is from what you are selecting in the
> daily frequency section when you schedule the job.
> Without the details of this, I'd guess you are selecting
> something like "occurs every 24 hours" with "starting at
> 11:59:59 PM" and "ending at 11:59:59 PM". That will give the
> error you have.
> If you want the job to run daily at 11:59:59 PM, select the
> "occurs once at " option (the first one in the daily
> frequency section). It will run once a day (or at whatever
> interval you have set or want set in the Occurs section) at
> 11:59:59 PM.
> -Sue
> On Thu, 20 Jan 2005 09:03:09 -0800, "Julia"
> <Julia@.discussions.microsoft.com> wrote:
> >Hi,
> >
> >I created a DTS package and wanted to schedule it to run at 11:59:5
> PM. I
> >could not save the schedule.
> >
> >An error "Error 14266: The specified '@.active_end_time' is invali
> (valid
> >values are: before or after @.active_start_time). The job was no
> saved."
> >
> >I tried 11:59:58 PM and 12:00:00 AM, both schedules can be saved. Why
> >11:59:59 PM not ?
> >
> >Please help
--
bdatc
----
bdatch's Profile: http://www.msusenet.com/member.php?userid=67
View this thread: http://www.msusenet.com/t-329815sql

Error 0xC0202009 while preparing to load the package

I have an SSIS project that is deployed to a sql server.

The setup of the project is a parent dtsx package, and many child packages.

The parent executes each of the chid packages.

If I run the parent from BIDS, calling the children that are on the SQL Server, it works fine.

If I execute it from SQL Management Console running on my laptop, connected to the SQL Server, It works.

If I remote into the SQL Server and run it from SQL Agent or SQL Management Console, the job fails with the error:

Error 0xC0202009 while preparing to load the package. SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x%1!8.8X!.

for each of the children.

This has quite suddenly stopped working, and I cannot figure out why it will work being executed from my laptop, but not on the server.

Any ideas?

Thanks

BobP

When you remote in, are you logging in with the same user/password that you use on your laptop? If not, it is probably a problem with security.|||

Yes I am. That's what is stumping me. Since I am running it from SQL Management Studio logged in as the same user, it should run from both machines.

Thanks

BobP

|||The difference is that for the first two scenarios you listed above, you are likely executing them from your machine. That is, dtexec.exe on your machine is executing the packages. When you remote in, you are using the dtexec.exe on the server. This means that things like network connectivity/firewalls/etc... come into play that might not be on your local machine.

What version of SQL Server do you have installed on your local workstation? Do you have the full SSIS client installed?|||

Hey Phil!

I didn't realize that if i run a sql package, logged into SSIS in SQL Management Console that it ran with the DTExec on my machine. Thanks for that bit of info.

However... Yes, I have the full SSIS installed on my machine, and the versions are:

Server 9.0.3042

Workstation: 9.0.3042

The irritating thing about this is that it started happening after it had been working for 2 months.

And as far as I know, nothing has changed on the server.

BobP

|||

BobP - BIM wrote:

However... Yes, I have the full SSIS installed on my machine, and the versions are:

Server 9.0.3042

Workstation: 9.0.3042

More specifically, Standard, Developer, or Enterprise versions? Also, which is installed on the server?|||

Sever is running enterprise 64 bit

Workstation is running developer.

Thanks!

|||

BobP - BIM wrote:

Sever is running enterprise 64 bit

Workstation is running developer.

Thanks!

Okay, so using this arrangement, when connected to Integration Services, through SSMS, you should be executing the copy on the server. That's my understanding.

Has this package run successfully before on a 64-bit machine? Do you have package logging turned on?|||

Nevermind... After a server re-boot, it is working fine now.

Thanks for all the help!

BobP

Error 0xC0011008 while preparing to load the package

Hello all-

This post is for informational purposes only, as I have solved the issue. However, it was such a sneaky issue that I thought I would share.

I was working from home on a working SSIS package. I deployed via dtutil, and then ran it.

It failed immediatly with the error:

"Error 0xC0011008 while preparing to load the package. Error loading from XML. No further detailed error information can be specified for this problem because no Events object was passed where detailed error information can be stored."

Nothing on the web helped me.

Well, after about 10 hours of working with it I figured it out.

The first package loaded in SSIS is my parent package, which executes other packages stored in SQL Server.

When I first loaded up the package, my VPN was still connecting. Since I was not on the VPN when this package loaded, it could not validate.

Without any indication, my connection to the SQL Server storing the packages was invalid. All I had to do was open it, and click on OK.

So be aware... If the validation cannot take place, bad things can happen ;-)

Hope this saves someone some time.

BobP

Closing Post.

Error 0x80070003 while loading package file

Hello,
I deployed an SSIS project to my SQL Server. The project I deployed contained two packages. One called the other. After deployment I notice that both packages are indeed in the SQL Server. However when I try to run it I get the error below. This error happens during the "Execute Package Task" and the path the error is pointing at is my local development path, not the one it was deployed to. Is there any way to fix the path? And how can I get it to deploy both packages so it knows where they are when I run it from the server?

Error 0x80070003 while loading package file "C:\VS Projects\Testing\Run Codes to DB\Run Codes to DB\SofAid_DBRefresh.dtsx". The system cannot find the path specified.

Thank You
Jaime
You should use a Package Configuration to populate a variable that specifies where the child package is located. Then use an expression on the connection manager to set the appropriate property from this variable.

You could have a configuration file on your workstation and one on the server, each specifying the appropriate path for that environment. Unless you want to hard-code the location of the file, you might want to specify it's location with an environment variable. Or you could just use an environment variable to hold to package location directly if that's the only configuration information you have.
|||That seems pretty round-about. Is there a way of telling it that the package is in the same folder, or a relative path?
|||No, there's no concept of relative paths in SSIS. Remember that a package may never even exist as a file.
|||You need to use package configuration to set the path and any other property value, dinamically at run time. Serach by package configurations in BOL and this forum.|||Thank you, that was very helpful

Error 0x80070002 while preparing to load the package. The system cannot find the file specified

Hi,

I have a package which calls another package. It had been working fine for a while. Recently I changed the connection managers' names. Everything in the parent package works fine. Database has been updated correctly. But when it comes to calling the child package it generates :

OnError,CRPRCHMSQCZ,,Execute AMSClientAgentMaintenance,,,3/8/2007 5:49:38 PM,3/8/2007 5:49:38 PM,-1073602332,0x,Error 0x80070002 while preparing to load the package. The system cannot find the file specified.
. (there is a period here instead of a file name)

I tested the child package on the server. It works fine. I connected the child package to the Execute Package Task by selecting from the packages on the server. So it is there for sure. Connection manager's name is read from the .dtsConfig. Child package is executed from my development machine but not on the server. I made a small test package just to call this child package, it generates the same error...

Any help is appreciated

Gulden

Renaming the connection managers must have corrupted the package.

I restored from the backup and left the connection manager's names as they are.

Error 0x80070002 while preparing to load the package. The system cannot find the file specified

Hi,

I have a package which calls another package. It had been working fine for a while. Recently I changed the connection managers' names. Everything in the parent package works fine. Database has been updated correctly. But when it comes to calling the child package it generates :

OnError,CRPRCHMSQCZ,,Execute AMSClientAgentMaintenance,,,3/8/2007 5:49:38 PM,3/8/2007 5:49:38 PM,-1073602332,0x,Error 0x80070002 while preparing to load the package. The system cannot find the file specified.
. (there is a period here instead of a file name)

I tested the child package on the server. It works fine. I connected the child package to the Execute Package Task by selecting from the packages on the server. So it is there for sure. Connection manager's name is read from the .dtsConfig. Child package is executed from my development machine but not on the server. I made a small test package just to call this child package, it generates the same error...

Any help is appreciated

Gulden

Renaming the connection managers must have corrupted the package.

I restored from the backup and left the connection manager's names as they are.

Error 0x80040E37

Has anyone ever run into this error? I have an SSIS package that works fine on our test server, but when I move it to production it's giving this error. The error is on the step that is using a variable/expression to connect to a "dynamic" database and server. It's a execute SQL command returning xml. I watched the variables in the locals and was lucky enough to find the the xml was getting this error. The exact error is:

<ROOT><?MSSQLError HResult=\"0x80040e37\" Source=\"Microsoft SQL Native Client\" Description=\"Invalid object name 'exp_a_client_vw'.\"?></ROOT>\r\n

Thanks,

Phil

The error message indicates that it can't find the 'exp_a_client_vw' object. Since you are using a dynamic connection, are you sure it is pointing to the correct database?|||

I'm pretty sure it is. Like I said, it's the same package that worked on dev and it found it's way to the correct database/server. I'm watching the variables in the locals as it gets to that step/container and they are correct. I'm trying to figure out now how I can write the entire connection string to a variable and watch it.

Phil

|||Use a script task to copy the value of the expression based variable to a regular variable immediately before the Exec SQL step.|||

Ok, I follow you so far. But how exactly can I tell the script task to grab the "ConnectionString" property of the my "Transform XML (SP) connection" which is the connections' exact name?

Thanks,

Phil

|||You're setting the connect string on the connection manager via an expression, right? Something like:

Code Snippet

"Data Source=" + User::DataSource + ";Initial Catalog=" + User::Catalog" + ";Provider=SQLNCLI.1;Integrated Security=SSPI;Auto Translate=False;"

Move that value to a new expression based variable. Then, in the connection manager, set the expression for the connection string to the new variable you created.

|||

Thanks. I got it. Turns out that the SP I was running doesn't have that object. I appreciate your help.

Phil

error 0x80040155 not interface

Hi

I got the following error message when I make a new integration service project

Failed to save package file "C:\Documents and Settings\Administrator\Local Settings\Temp\1\tmp2B.tmp" with error 0x80040155 "Interface not registered".
Can someone help

MeHi there,

This looks like a setup issue. Did you have a prior build of SQL/VS 2005 on the machine? If so, likely the machine wasn't cleaned up prior to setting up.

regards,
ash|||I also am getting this error.
I upgraded from VS 2005 Beta 2 to VS 2005 RC, but I followed all recommended uninstallation steps prior to installing VS 2005 RC.
So what can I do about this?
Will it help at all to completely uninstall VS 2005 RC and then reinstall it?
I've already tried repairing VS 2005 RC, but it didn't make any difference.
Thanks,
Dyvim|||Try registering MSXML:

regsvr32 msxml3.dll
regsvr32 msxml6.dll|||Thanks, this worked also for me|||Thanks but how do I do this, how do I register MSXML?|||

Just run these two commands from the command prompt:

regsvr32 msxml3.dll
regsvr32 msxml6.dll

|||yes it works for me too. Thanks.|||

I got the same issue, it also works for me.

Thank you so much!

|||

Hi-Thank you for the info. When I ran the 1st command regsvr32 msxml3.dll, it went fine. The 2nd command regsvr32 msxml6.dll told me "The specific module could not be found" I am getting errors like: Interface not registered (when I try to print), No such interface supported (when I tried to contact NoAdware for online support). Also, get same message when I try to go into a game room on Yahoo games. Please note: I just did a scan to remove adware and spyware.

Thanks in advance for any help you can give me,

Corinne

|||

It looks like the software you used to "remove adware and spyware" removed much more - apparently it deleted msxml6.dll (which is installed with SQL Server 2005) and probably some interface registrations.

I would recommend reformatting and reinstalling this machine and avoiding this antispyware program in the future.

|||

Hi, I have the exact same problem but it is when I try to burn a cd using Win Media Player 10. I tried registering the .dll's, but since I don't have the SQL 2005 installed in my machine, the regsvr32 msxml6.dll gives me the same error message. I see that this forum is mainly for SQL but if anybody knows what I can do, it would be appreciated.

Thanks,

Jason

|||

Hi there, di you get a reply to your query as I am experiencing the same problem. Please e-mail me & let me know. Many thanks

|||

Guys, there are thousands of interfaces registered on a typical Windows box. The error can be caused by missing registration of any of them.

We've found that particular problem ("Interface not registered" error when creating new SSIS project) is usually caused by incorrectly registered msxml dlls - my reply above describes how to fix it.

Regarding other applications - like media player, etc - there is no common answer, and you should be looking at the support forums for particular application.

|||

Quote 'I would recommend reformatting and reinstalling this machine and avoiding this antispyware program in the future.'

If I had to re-format every time something is not registering in Windows - that would be all I would be doing -Re-formatting...

Would re-installing SQL fix the problem.

Dan.

Error : Difference of two datetime columns caused overflow at runtime.

At my job is a dts package that is failing in SQL 2005. I am not a SQL
expert. I am just trying to fix. I put the query in Query Analyzer
and get this error:

(4322 row(s) affected)

Server: Msg 535, Level 16, State 1, Line 1
Difference of two datetime columns caused overflow at runtime.

I am just trying to understand what this means, what I should be
looking for and what could be wrong. Here is the query:

SELECT i.SerialNumber, '' AS mac_number, DATEDIFF([second], 'Jan 1,
1970', s.DateOrdered) AS Support_StartDt, DATEDIFF([second], 'Jan 1,
1970',
s.Warranty_Enddate) AS Support_EndDt,
DATEDIFF([second], 'Jan 1, 1970', c.Registration_Date) AS
Registration_Date, c.FirstName AS enduser_fname,
c.LastName AS enduser_lname, c.CompanyName AS
enduser_companyname, c.ContactEmail AS enduser_email, c.Address AS
enduser_address1,
c.Address2 AS enduser_address2, c.City AS
enduser_city, c.State AS enduser_state, c.Zip AS enduser_zip,
c.WorkPhone AS enduser_phone,
c.Fax AS enduser_fax, d.DealerName AS
dealer_companyname, d.ContactFirstName AS dealer_fname,
d.ContactLastName AS dealer_name,
d.Address1 AS dealer_address, d.City AS
dealer_city, d.State AS dealer_state, d.Zip AS dealer_zip,
d.ContactPhone AS dealer_phone,
d.ContactFax AS dealer_fax,
ISNULL(SUBSTRING(p.ProductName, 11, LEN(p.ProductName) - 10), 'unknown
IWP product') AS product_type, '' AS extra1,
'' AS extra2, '' AS extra3, '' AS extra4, '' AS
extra5, '' AS extra6, '' AS extra7
FROM tblInventory i full outer JOIN
tblDealers d ON i.DealerID = d.DealerID full
OUTER JOIN
tblSupport s ON i.InventoryID = s.InventoryID
full outer JOIN
tblCustomers c ON s.InventoryID = c.InventoryID
LEFT OUTER JOIN
tblProducts p ON LEFT(i.SerialNumber,
PATINDEX('%-%', i.SerialNumber)) = p.SerialPrefix
WHERE i.SerialNumber <> ''

Any ideas would be greatly appreciated.geekwagon@.gmail.com (geekwagon@.gmail.com) writes:
> At my job is a dts package that is failing in SQL 2005. I am not a SQL
> expert. I am just trying to fix. I put the query in Query Analyzer
> and get this error:
>
> (4322 row(s) affected)
> Server: Msg 535, Level 16, State 1, Line 1
> Difference of two datetime columns caused overflow at runtime.
>
> I am just trying to understand what this means, what I should be
> looking for and what could be wrong. Here is the query:
>
> SELECT i.SerialNumber, '' AS mac_number, DATEDIFF([second], 'Jan 1,
> 1970', s.DateOrdered) AS Support_StartDt, DATEDIFF([second], 'Jan 1,
> 1970',
> s.Warranty_Enddate) AS Support_EndDt,
> DATEDIFF([second], 'Jan 1, 1970', c.Registration_Date) AS

One or of the rows has a value that is in 2038 or later in one of the
columns. My bets are on Warranty_Enddate and somehas put in 99991231
for an infinite warranty.

(2038-01-19 03:14:07.000 is the time when the number of seconds since
1970-01-01 exceeds the range of an un integer.)

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||>From Transact-SQL Reference:

DATEDIFF produces an error if the result is out of range for integer
values. For milliseconds, the maximum number is 24 days, 20 hours, 31
minutes and 23.647 seconds. For seconds, the maximum number is 68 years.

Error - Cannot open the datafile

Hi there,

I have written a program that loads a package (SomePackage.dtsx) from the physical drive and executes that. The package does nothing but imports data from a csv file to the Sql server 2005. But I can see that the package is failing continuously. I meant the package.Execute() method is returning a DTSExecResult.Failure. I investigated the Package.Errors property that contains the error collection and found that there are two DTSError objects into the collection.

The first one’s description says that

Cannot open the datafile "D:\SOME.csv".

And the later one’s is

component "SOURCE FLAT FILE COMPONENT" (1) failed the pre-execute phase and returned error code 0xC020200E.

But the most interesting thing is if I execute the package through the Execute package Utility (double clicking onto the SomePackage.dtsx file) ships with Sql server 2005 then it executes fine and works as expected. I have checked the permission of the csv file and it has everyone’s full access.

Can anyone help me on this?

I will appreciate all kind of suggestions.

Thanks

Moim

Hi,

"right click" the "flatfile connection manager"

click on "Edit". there are several properties here that needs to be configured

one of which is the "format".. make sure its "delimited" or something that suits your need.

if it didn't solve your problem try other properties

in this area.

regards,

joey

|||

What is different about when you use your tool vs dtexecui?

Is this the same machine?

Is this the same user running both tools?

|||

Darren,

Basically I can see the only difference is when I am running through the code it is failing and when I am running from the windows explorer it is working.

Nothing more. It is same machine, same user.

Any Idea?

Thanks

Moim

|||

joeydj,

Im afraid, I have created that package programmatically so I dont have a scope to edit that inside the Sql Server BI editor. anyway, I checked out and these properties are set.

Any Idea?

Thanks

Moim

|||Is your file on a mapped drive, by chance?|||

Brammer,

No its on a local drive (drive D: ).

Any other idea?

THanks

Moim

|||

Ok, so same package, same machine, same user, same execution parameters, just a different execution host... does not make much sense.

Try adding logging to the package, something simple like log all warnings and errors to a text file. Any other errors? There must be some difference but that error is not very clear as to what.

Error - Analysis Services Processing Task

We have an Integration services package that executes a few TSQL tasks, then processes an Analsys Services database. This has been in production for about three weeks now and twice the package has failed with this error from the event log:

Event Type: Error

Event Source: MSSQLServerOLAPService

Event Category: (289)

Event ID: 3

Date: 7/11/2007

Time: 1:48:59 AM

User: N/A

Computer:

Description:

OLE DB error: OLE DB or ODBC error: An error has occurred while establishing a connection to the server.

When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server

does not allow remote connections.; 08001;

Communication link failure; 08S01;

TCP Provider: An existing connection was forcibly closed by the remote host.

; 08S01.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

I don't think that this error is accurate because the package and Analysis Services are on the same server.

Also, this does not happen in our development environment. Any help is appreciated.

Thanks,

Brian

Sorry to side track a bit, but processing cube using SSIS is not the most effiecent way of prcoessing a cube. Can't remember the specifics, but if you can I would get the sql agent to process the cube.

Cheers

Matt