Error renaming analysis services project

After renaming an analysis services project in bi development studio I receive the following error when deploying the project to SQL2005 AS (SP1):

Error 1 The 'Database' with 'ID' = 'AS UPC Chain Sales ' doesn't exist in the collection. 0 0

However the database is available on the server and can be processed and used. Any ideas how to fix this error?

Try to rename your live database on the Analysis Server using SQL Management Studio.

Then create a new project in BI Dev Studio. Select a project type as "Import Analysis Services 9.0 Database...". Follow the steps and get your project re-created based on the live version of the database.

Edward.
--
This posting is provided "AS IS" with no warranties, and confers no rights.

|||Thanks, Edward. Worked like a charm!

error Pumping data from ODBC

Hi, there;

I created a package that pump data from ODBC to SQL2005.

When I run my package, I got error:

SSIS package "Package.dtsx" starting.

Information: 0x4004300A at Data Flow Task, DTS.Pipeline: Validation phase is beginning.

Information: 0x40043006 at Data Flow Task, DTS.Pipeline: Prepare for Execute phase is beginning.

Information: 0x40043007 at Data Flow Task, DTS.Pipeline: Pre-Execute phase is beginning.

Information: 0x4004300C at Data Flow Task, DTS.Pipeline: Execute phase is beginning.

Error: 0xC02090F5 at Data Flow Task, DataReader Source [1350]: The component "DataReader Source" (1350) was unable to process the data.

Error: 0xC0047038 at Data Flow Task, DTS.Pipeline: The PrimeOutput method on component "DataReader Source" (1350) returned error code 0xC02090F5. The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure code is defined by the component, but the error is fatal and the pipeline stopped executing.

Error: 0xC0047021 at Data Flow Task, DTS.Pipeline: Thread "SourceThread0" has exited with error code 0xC0047038.

Error: 0xC0047039 at Data Flow Task, DTS.Pipeline: Thread "WorkThread0" received a shutdown signal and is terminating. The user requested a shutdown, or an error in another thread is causing the pipeline to shutdown.

Error: 0xC0047021 at Data Flow Task, DTS.Pipeline: Thread "WorkThread0" has exited with error code 0xC0047039.

Information: 0x40043008 at Data Flow Task, DTS.Pipeline: Post Execute phase is beginning.

Information: 0x402090DF at Data Flow Task, OLE DB Destination [1527]: The final commit for the data insertion has started.

Information: 0x402090E0 at Data Flow Task, OLE DB Destination [1527]: The final commit for the data insertion has ended.

Information: 0x40043009 at Data Flow Task, DTS.Pipeline: Cleanup phase is beginning.

Information: 0x4004300B at Data Flow Task, DTS.Pipeline: "component "OLE DB Destination" (1527)" wrote 0 rows.

Task failed: Data Flow Task

SSIS package "Package.dtsx" finished: Success.

Did I do something wrong when I created this package?

Thanks.

Did you use the ADO.NET connection manager to connect to your ODBC source? Can you use the ODBC source in other applications, outside of SSIS?|||

Yes, I am using ADO.NET. It works for other other tables. I just imported data from two other tables with same connection.

Haven't tried to use this ODBC source yet. But I will use it with C# application out of SSIS.

Thanks.

|||Try your ODBC connection against this table with an outside application. Sounds like you've set these up successfully before, so I would think you've got it setup correctly this time.

What ODBC driver are you using? (Against what database)|||Yes, I will.
It shows "D3 ODBC Driver".

Strange thing is that I can pump data for other tables with same connection.

Cheers.|||

Qiuwei wrote:

Yes, I will.
It shows "D3 ODBC Driver".

Strange thing is that I can pump data for other tables with same connection.

Cheers.

Maybe you don't have permission to select against this table.|||

Qiuwei wrote:

Yes, I will.
It shows "D3 ODBC Driver".

Strange thing is that I can pump data for other tables with same connection.

Cheers.

Trying Incresing the TimeOut property in the datareader. I was able to fix a similar issue before, in my case I had many packages running against the same ODBC source; and I was receiving *I belive* the same error in the 2 packages extracting the biggest set of data. Just a thought....

|||

Thanks.

Phil, yes, I have permission to select data from that ODBC source.

Rafael, I set to timeout to 600. It still doesn't want to work. It only has about 9,000 rows.

The problem SSIS users are facing is that the error message is almost useless and very easy to be crashed!

Does anybody know if MS has a web resource for those error code?

Cheers.

sql

Error on using VB in calculated members AFTER stepping up to Enterprise version ?

I have "succesfully upgraded" (?) our SQL2005 from standard to Enterprise version.
Before, following set worked like a charm:

CREATE SET CURRENTCUBE.[Now CY]
AS strtomember("[00 - Time].[00 - H - Calendar].[Day Name].&[" + format(now(),"yyyyMMdd") + "]");

But when I process the cube now, I get this error:

Error 1 MdxScript(Sales) (58, 74) The '[now]' function does not exist. 0 0

It seems like the reference to Visual Basic has been lost somehow
Curiously following calculated member works, even it also uses now() ?

CREATE MEMBER CURRENTCUBE.[MEASURES].[Now]
AS now(),
FORMAT_STRING = "yyyyMMdd",
VISIBLE = 1;

Any suggestions ?
please ;-)

/ geert larsen

denmark

Can you reproduce this problem in Adventure Works Enterprise Edition? Another thing to try is the qualified name: VBA![Now]()|||

Hello Deepak
Thanks for your reply
unfortunately the VBA![Now]() did not work
(And I have not installed the AdventureWorks )

BUT I have investigated a little further in the Assemblies and found that ie. the VBAMDX
is registred in C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\bin\msmdvbanet.dll
But this directory is empty ?
Now the file(s) are situated in C:\Program Files\Microsoft SQL Server\MSSQL.6\OLAP\bin\

I have tried to copy the files and re-register (regsvr32 msmdvbanet.dll)
but I get this error:
C:\Program Files\Microsoft SQL Server\MSSQL.2\OLAP\bin\msmdvbanet.dll was loaded, but the DllRegisterServer entry point was not found.
This file can not be registered.

I hope this may give you (and then me) a hint

tia
/ geert larsen
denmark

|||Well, msmdvbanet.dll is not a COM server, therefore you cannot register it with regsvr32. There is something that went wrong during setup or upgrade, and the problem with VBA might not be the only one. I recommend reinstalling from scratch.|||

Complete un- and reinstall solved the problems *NOT FUNNY*

Thanks for advice

/ geert larsen

denmark

Error message when trying to do a maintenance plan

Hi all,

As far as I can tell I have installed all features of SQL2005 but when I try to setup a maintenance plan I am receiving this message:

TITLE: Microsoft SQL Server Management Studio

The action you attempted to perform on a remote instance of SQL Server has failed because the action requires a SQL Server component that is not installed on the remote computer. To proceed, install SQL Server 2005 Management Tools on the remote computer, and then try again. For more information, see "How to: Install SQL Server 2005 (Setup)" in SQL Server 2005 Books Online, or find the article on MSDN at http://go.microsoft.com/fwlink/?LinkID=57083 . (ObjectExplorer)

For help, click: http://go.microsoft.com/fwlink/?LinkID=57083

BUTTONS:

OK

Any ideas on why this is happening?

first of all you must apply sp2 of Mar

http://www.sql-server-performance.com/forum/topic.asp?TOPIC_ID=19624

There are many problems related to MP solved in this version. Check whether you have installed Integration services and the services is running

Madhu

|||

First things first, have you applied any service pack after you have installed the SQL 2005 components on thsi machine?

If not try as suggested to take care of such issues with maintenance plans.