ERROR: Subreport: created

Showing posts with label created. Show all posts

Wednesday, March 21, 2012

errors while running ssis packages from the command prompt.

I have created ssis package. It has been successfully running at UI level.

But when i am trying to execute it from the command prompt by using dtexec utility it is showing the following error messages.

Error: 2005-12-23 17:01:57.67
Code: 0xC00470FE
Source: Data Flow Task DTS.Pipeline
Description: The product level is insufficient for component "Flat File Source" (1).
End Error
Error: 2005-12-23 17:01:57.67
Code: 0xC00470FE
Source: Data Flow Task DTS.Pipeline
Description: The product level is insufficient for component "Script Component" (9).
End Error

i have entered the command as follows.

dtexec /f "c:\somefolder\package1.dtsx"

Any points regarding this issue would be helpful.

Take a look here:

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

Same problem is being discussed.

HTH,
Ovidiu

|||

I am receiving a similar error. We are running SS2005 Enterprise Edition. We can connect to SSIS with SS Management Studio so that verifies that it's installed. Here is our error log. Did you solve your probelm, and if so, how?

*************************************Run GPS_EXTRACT_QA.dtsx*********************************************
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: 5:14:34 PM
Progress: 2006-01-26 17:14:36.01
Source: Data Flow Task
Validating: 0% complete
End Progress
Progress: 2006-01-26 17:14:36.03
Source: Data Flow Task
Validating: 50% complete
End Progress
Progress: 2006-01-26 17:14:36.21
Source: Data Flow Task
Validating: 100% complete
End Progress
Progress: 2006-01-26 17:14:36.53
Source: Execute SQL Task
Executing query "truncate table sap_extract_staging
delete from sap".: 100% complete
End Progress
Progress: 2006-01-26 17:14:36.54
Source: Data Flow Task
Validating: 0% complete
End Progress
Progress: 2006-01-26 17:14:36.56
Source: Data Flow Task
Validating: 50% complete
End Progress
Progress: 2006-01-26 17:14:36.60
Source: Data Flow Task
Validating: 100% complete
End Progress
Error: 2006-01-26 17:14:36.60
Code: 0xC00470FE
Source: Data Flow Task DTS.Pipeline
Description: The product level is insufficient for component "Flat File Source" (749).
End Error
Warning: 2006-01-26 17:14:36.60
Code: 0x80019002
Source: GPS_EXTRACT_QA
Description: The Execution method succeeded, but the number of errors raised (1) 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.
End Warning
DTExec: The package execution returned DTSER_FAILURE (1).
Started: 5:14:34 PM
Finished: 5:14:36 PM
Elapsed: 2.562 seconds

|||

I am also getting same error.

any sugessions regarding this issue

sql

errors while running ssis packages from the command prompt.

I have created ssis package. It has been successfully running at UI level.

But when i am trying to execute it from the command prompt by using dtexec utility it is showing the following error messages.

i have entered the command as follows.

dtexec /f "c:\somefolder\package1.dtsx"

Any points regarding this issue would be helpful.

Take a look here:

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

Same problem is being discussed.

HTH,
Ovidiu

|||

I am also getting same error.

any sugessions regarding this issue

errors while running ssis packages from the command prompt.

I have created ssis package. It has been successfully running at UI level.

But when i am trying to execute it from the command prompt by using dtexec utility it is showing the following error messages.

i have entered the command as follows.

dtexec /f "c:\somefolder\package1.dtsx"

Any points regarding this issue would be helpful.

Take a look here:

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

Same problem is being discussed.

HTH,
Ovidiu

|||

I am also getting same error.

any sugessions regarding this issue

Errors while Deploying Analysis services projects in server

Hi,

I am using Sql server Business Intelligence Development Studio 2005 and SQL server Management studio.

I created a Analysis services project in the BI Dev Studio, and set the correct server attributes in the project properties -> deployment tab.

I have created a data source , then a datasource view and then cube and dimensions.

1) When I tried deploying with the database name as 'xyz'. (again set in the project properties -> database ,target attribute),

and the database 'xyz' is previously created and thus present in the Analysis server 2005. I get the following error:

"The database , 'xyz', contains an ImpersonationMode that is reserved for server administrators."

2.) When i tried deploying with the database name as 'abc'. (again set in the project properties -> database ,target attribute),

but NOTE now there is no analysis server database with the name 'abc' already existing in the analysis server. now I get the following error:

"Either the 'myUserName' user does not have permission to create a new object in 'myServerName', or the object does not exist."

I checked the Sql server management studio and under the 'xyz' analysis database in the 'Roles' Folder my username is a member of the Administrators who have full priliviges.

Please do tell me as to where I am going wrong.

Thanks and regards

Vijay R

Hi Vijay,

I had the same problem as you and found the following on http://www.eggheadcafe.com/forumarchives/SQLServerdatamining/Jun2005/post23396286.asp. Changing the impersonation mode to the service account sorted things out straight away for me, hopefully it'll do the same for you.

"The impersonation mode tells Anaylsis Server what credentials to use when connecting to the database specified in the datasource object. When you create the datasource using the Data Source Wizard, there's an "Impersonation Information" page where you can set this information. If the data source is used for processing (i.e. you are training mining structures/models from that data source), you are not allowed to set the ImpersonationMode to "Use the credentials of the current user" due to security considerations - you must either use the service account or use a specific username/password. You can change the impersonation mode by opening the data source in BI Dev Studio and selecting one of the allowed options above on the "Impersonation Information" tab."

Errors when uploading DDL and Data file created by Database Publishing Wizard

Hi,

I needed to recreate/publish a DDL and data file(of a database) that was produced using Database Publishing Wizard. The size of the file is 4G. I receive the following error when I try to open it up in the new query window of sql server 2005 (sp2)for execution.

"The operation could not be completed. Not enough storage is available to complete this operation."

I know my server has 829G of free storage space available. i receive no errors when I open up a smaller file also created by database publishing wizard.

What possibly is causing this?

Thanks in advance

Hi Hamdaweh,

When you attempt to open this in QA, it is attempting to load the entire 4GB+ into system RAM, that's why you are receiving this error. Try opening it with a specialist text editior and chunking it down into smaller files, and then run each via QA.

Cheers,

Rob

|||Thanks. So can i say the database publishing wizard is good for only DDLs and small data?

Errors using sp_refreshview

Hi ... I hope someone can explain this. Some time ago we created a stored
procedure that loops through all SPs and Views and refreshes them. Yesterday
we noticed a problem where two specific views would not refresh (don't seem
to have the problem with SPs and sp_recompile). After manually dropping and
recreating the view and then rerunning the proc then worked without error.
Of course it wasn't necessary but we wanted to retest the main SP running th
e
refresh process.
Of course, nothing else (that we can see) changed. In addition, we have
several deployments of the same database structure, and this did NOT happen
in all databases ... in fact, in most deployments worked without error. On
our dev server there are several databases, all (supposedly) the same
structure and since on the same DB server it is of course the same version o
f
SQLServer. Yet we had the failure on two separate tables in two separate
databases (unknown if it was the same tables in the two databases).
We're still evaluating of course, but in the meanwhile ... any ideas'
Thanks in advance ...
--
Brad AshforthHi,
Did u checked the log why it happend like this as u explained .
Have u scheduled a job to execute ur SP.
From
Doller
Brad Ashforth wrote:
> Hi ... I hope someone can explain this. Some time ago we created a stored
> procedure that loops through all SPs and Views and refreshes them. Yesterd
ay
> we noticed a problem where two specific views would not refresh (don't see
m
> to have the problem with SPs and sp_recompile). After manually dropping an
d
> recreating the view and then rerunning the proc then worked without error.
> Of course it wasn't necessary but we wanted to retest the main SP running
the
> refresh process.
> Of course, nothing else (that we can see) changed. In addition, we have
> several deployments of the same database structure, and this did NOT happe
n
> in all databases ... in fact, in most deployments worked without error. On
> our dev server there are several databases, all (supposedly) the same
> structure and since on the same DB server it is of course the same version
of
> SQLServer. Yet we had the failure on two separate tables in two separate
> databases (unknown if it was the same tables in the two databases).
> We're still evaluating of course, but in the meanwhile ... any ideas'
> Thanks in advance ...
> --
> Brad Ashforth|||Hi Brad,
Welcome to use MSDN Managed Newsgroup!
From your descriptions, I understood it happened to failed refreshing for
two of your views via sp_refreshview. If I have misunderstood your
concern, please feel free to point it out.
It seems strange and it seems you have fixed this by dropping and
recreating the Views. Could you find any more related information in Error
Log?
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Michael ... by Error Log I'm assuming you mean the SQL Server Error Log,
under the Management folder in Enterprise Manager. There is no entry in the
error log for this (at least no entry that mentions the databases in
question). Is it possible that the server is not configured to report errors
at this level? If so, how can I configure it to report these types of errors
should they occur again? We are concerned because we have seen this error no
t
only on our Dev server but on two different client production servers.
Thank you for your assistance ...
--
Brad Ashforth
"Michael Cheng [MSFT]" wrote:

> Hi Brad,
> Welcome to use MSDN Managed Newsgroup!
> From your descriptions, I understood it happened to failed refreshing for
> two of your views via sp_refreshview. If I have misunderstood your
> concern, please feel free to point it out.
> It seems strange and it seems you have fixed this by dropping and
> recreating the Views. Could you find any more related information in Error
> Log?
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ========================================
=============
> This posting is provided "AS IS" with no warranties, and confers no rights
.
>|||Hi Brad,
This seems to be related to a known issue of us when the views are updated
in not dependent order. Please use sp_refreshview to update views in
dependent order.
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Michael ... Thank you for your input. The next time it occurs, we will tr
y
to determine if the view is dependent on other views and if so will try to
refresh again (assuming the view that it was dependent on was refreshed late
r
in the 1st attempt).
--
Brad Ashforth
"Michael Cheng [MSFT]" wrote:

> Hi Brad,
> This seems to be related to a known issue of us when the views are updated
> in not dependent order. Please use sp_refreshview to update views in
> dependent order.
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ========================================
=============
> This posting is provided "AS IS" with no warranties, and confers no rights
.
>|||Hi Brad,
You are welcome to reply here whenever it occurs again. Thank you for your
patience and cooperation.
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.

Errors using sp_refreshview

Hi ... I hope someone can explain this. Some time ago we created a stored
procedure that loops through all SPs and Views and refreshes them. Yesterday
we noticed a problem where two specific views would not refresh (don't seem
to have the problem with SPs and sp_recompile). After manually dropping and
recreating the view and then rerunning the proc then worked without error.
Of course it wasn't necessary but we wanted to retest the main SP running the
refresh process.
Of course, nothing else (that we can see) changed. In addition, we have
several deployments of the same database structure, and this did NOT happen
in all databases ... in fact, in most deployments worked without error. On
our dev server there are several databases, all (supposedly) the same
structure and since on the same DB server it is of course the same version of
SQLServer. Yet we had the failure on two separate tables in two separate
databases (unknown if it was the same tables in the two databases).
We're still evaluating of course, but in the meanwhile ... any ideas?
Thanks in advance ...
Brad Ashforth
Hi,
Did u checked the log why it happend like this as u explained .
Have u scheduled a job to execute ur SP.
From
Doller
Brad Ashforth wrote:
> Hi ... I hope someone can explain this. Some time ago we created a stored
> procedure that loops through all SPs and Views and refreshes them. Yesterday
> we noticed a problem where two specific views would not refresh (don't seem
> to have the problem with SPs and sp_recompile). After manually dropping and
> recreating the view and then rerunning the proc then worked without error.
> Of course it wasn't necessary but we wanted to retest the main SP running the
> refresh process.
> Of course, nothing else (that we can see) changed. In addition, we have
> several deployments of the same database structure, and this did NOT happen
> in all databases ... in fact, in most deployments worked without error. On
> our dev server there are several databases, all (supposedly) the same
> structure and since on the same DB server it is of course the same version of
> SQLServer. Yet we had the failure on two separate tables in two separate
> databases (unknown if it was the same tables in the two databases).
> We're still evaluating of course, but in the meanwhile ... any ideas?
> Thanks in advance ...
> --
> Brad Ashforth
|||Hi Brad,
Welcome to use MSDN Managed Newsgroup!
From your descriptions, I understood it happened to failed refreshing for
two of your views via sp_refreshview. If I have misunderstood your
concern, please feel free to point it out.
It seems strange and it seems you have fixed this by dropping and
recreating the Views. Could you find any more related information in Error
Log?
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
|||Hi Michael ... by Error Log I'm assuming you mean the SQL Server Error Log,
under the Management folder in Enterprise Manager. There is no entry in the
error log for this (at least no entry that mentions the databases in
question). Is it possible that the server is not configured to report errors
at this level? If so, how can I configure it to report these types of errors
should they occur again? We are concerned because we have seen this error not
only on our Dev server but on two different client production servers.
Thank you for your assistance ...
Brad Ashforth
"Michael Cheng [MSFT]" wrote:

> Hi Brad,
> Welcome to use MSDN Managed Newsgroup!
> From your descriptions, I understood it happened to failed refreshing for
> two of your views via sp_refreshview. If I have misunderstood your
> concern, please feel free to point it out.
> It seems strange and it seems you have fixed this by dropping and
> recreating the Views. Could you find any more related information in Error
> Log?
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
|||Hi Brad,
This seems to be related to a known issue of us when the views are updated
in not dependent order. Please use sp_refreshview to update views in
dependent order.
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
|||Hi Michael ... Thank you for your input. The next time it occurs, we will try
to determine if the view is dependent on other views and if so will try to
refresh again (assuming the view that it was dependent on was refreshed later
in the 1st attempt).
Brad Ashforth
"Michael Cheng [MSFT]" wrote:

> Hi Brad,
> This seems to be related to a known issue of us when the views are updated
> in not dependent order. Please use sp_refreshview to update views in
> dependent order.
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> ================================================== ===
> This posting is provided "AS IS" with no warranties, and confers no rights.
>
|||Hi Brad,
You are welcome to reply here whenever it occurs again. Thank you for your
patience and cooperation.
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.

Errors using sp_refreshview

Hi ... I hope someone can explain this. Some time ago we created a stored
procedure that loops through all SPs and Views and refreshes them. Yesterday
we noticed a problem where two specific views would not refresh (don't seem
to have the problem with SPs and sp_recompile). After manually dropping and
recreating the view and then rerunning the proc then worked without error.
Of course it wasn't necessary but we wanted to retest the main SP running the
refresh process.
Of course, nothing else (that we can see) changed. In addition, we have
several deployments of the same database structure, and this did NOT happen
in all databases ... in fact, in most deployments worked without error. On
our dev server there are several databases, all (supposedly) the same
structure and since on the same DB server it is of course the same version of
SQLServer. Yet we had the failure on two separate tables in two separate
databases (unknown if it was the same tables in the two databases).
We're still evaluating of course, but in the meanwhile ... any ideas'
Thanks in advance ...
--
Brad AshforthHi,
Did u checked the log why it happend like this as u explained .
Have u scheduled a job to execute ur SP.
From
Doller
Brad Ashforth wrote:
> Hi ... I hope someone can explain this. Some time ago we created a stored
> procedure that loops through all SPs and Views and refreshes them. Yesterday
> we noticed a problem where two specific views would not refresh (don't seem
> to have the problem with SPs and sp_recompile). After manually dropping and
> recreating the view and then rerunning the proc then worked without error.
> Of course it wasn't necessary but we wanted to retest the main SP running the
> refresh process.
> Of course, nothing else (that we can see) changed. In addition, we have
> several deployments of the same database structure, and this did NOT happen
> in all databases ... in fact, in most deployments worked without error. On
> our dev server there are several databases, all (supposedly) the same
> structure and since on the same DB server it is of course the same version of
> SQLServer. Yet we had the failure on two separate tables in two separate
> databases (unknown if it was the same tables in the two databases).
> We're still evaluating of course, but in the meanwhile ... any ideas'
> Thanks in advance ...
> --
> Brad Ashforth|||Hi Brad,
Welcome to use MSDN Managed Newsgroup!
From your descriptions, I understood it happened to failed refreshing for
two of your views via sp_refreshview. If I have misunderstood your
concern, please feel free to point it out.
It seems strange and it seems you have fixed this by dropping and
recreating the Views. Could you find any more related information in Error
Log?
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Michael ... by Error Log I'm assuming you mean the SQL Server Error Log,
under the Management folder in Enterprise Manager. There is no entry in the
error log for this (at least no entry that mentions the databases in
question). Is it possible that the server is not configured to report errors
at this level? If so, how can I configure it to report these types of errors
should they occur again? We are concerned because we have seen this error not
only on our Dev server but on two different client production servers.
Thank you for your assistance ...
--
Brad Ashforth
"Michael Cheng [MSFT]" wrote:
> Hi Brad,
> Welcome to use MSDN Managed Newsgroup!
> From your descriptions, I understood it happened to failed refreshing for
> two of your views via sp_refreshview. If I have misunderstood your
> concern, please feel free to point it out.
> It seems strange and it seems you have fixed this by dropping and
> recreating the Views. Could you find any more related information in Error
> Log?
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>|||Hi Brad,
This seems to be related to a known issue of us when the views are updated
in not dependent order. Please use sp_refreshview to update views in
dependent order.
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.|||Hi Michael ... Thank you for your input. The next time it occurs, we will try
to determine if the view is dependent on other views and if so will try to
refresh again (assuming the view that it was dependent on was refreshed later
in the 1st attempt).
--
Brad Ashforth
"Michael Cheng [MSFT]" wrote:
> Hi Brad,
> This seems to be related to a known issue of us when the views are updated
> in not dependent order. Please use sp_refreshview to update views in
> dependent order.
>
> Sincerely yours,
> Michael Cheng
> Microsoft Online Partner Support
> When responding to posts, please "Reply to Group" via your newsreader so
> that others may learn and benefit from your issue.
> =====================================================> This posting is provided "AS IS" with no warranties, and confers no rights.
>|||Hi Brad,
You are welcome to reply here whenever it occurs again. Thank you for your
patience and cooperation.
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.

Errors using report designer with ssas based report model

I have created a report model based on an SSAS database. It is usable without
errors with Report Builder as far as I can tell. However with Report
Designer, the layout displays the cube elements but errors on preview as
follows:
"The 'PerspectiveId' custom property for the 'query' perspective is either
not set or is not set to the string data type."
This is an error that has cropped up before but I'm not aware of a bug
report for it. The forum and blog guidance I have for fixing it is to:
- Create a report builder report and save it to file
- Copy the customproperties xml subtree and paste it into the Report
Designer report
I have done this but unfortunately this also errors on reopening the report
as follows:
"A connection cannot be made to the database. Set and test the connection
string. Additional information: TODO - change code to use RsProxy object
(Microsoft.ReportingServices.QueryDesigners)"
Notwithstanding the slightly disconcerting TODO comment lingering in the
code, can anyone advise cause and resolution/workaround?
Thanks in advance
David
using:
- SQL Server 2005 Analysis Services 9.0.3042
- Windows XP Pro SP2
- Visual Studio 2005 SP1
-- report designer rdl follows
--
<?xml version="1.0" encoding="utf-8"?>
<Report
xmlns="http://schemas.microsoft.com/sqlserver/reporting/2005/01/reportdefinition"
xmlns:rd="http://schemas.microsoft.com/SQLServer/reporting/reportdesigner">
<DataSources>
<DataSource Name="dataSource1">
<DataSourceReference>dataSource1</DataSourceReference>
<rd:DataSourceID>6d24178d-90d5-486e-a311-a4d939b769ea</rd:DataSourceID>
</DataSource>
</DataSources>
<BottomMargin>2.5cm</BottomMargin>
<RightMargin>2.5cm</RightMargin>
<PageWidth>21cm</PageWidth>
<rd:DrawGrid>true</rd:DrawGrid>
<InteractiveWidth>21cm</InteractiveWidth>
<rd:GridSpacing>0.25cm</rd:GridSpacing>
<rd:SnapToGrid>true</rd:SnapToGrid>
<Body>
<ColumnSpacing>1cm</ColumnSpacing>
<Height>5cm</Height>
</Body>
<rd:ReportID>cdfcad95-4a03-4a8d-82a6-048cac98eb26</rd:ReportID>
<LeftMargin>2.5cm</LeftMargin>
<DataSets>
<DataSet Name="DataSet1">
<Query>
<CommandText><SemanticQuery
xmlns="http://schemas.microsoft.com/sqlserver/2004/10/semanticmodeling"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:qd="http://schemas.microsoft.com/sqlserver/2004/11/semanticquerydesign"
xmlns:rb="http://schemas.microsoft.com/sqlserver/2004/11/reportbuilder">
<Hierarchies>
<Hierarchy>
<BaseEntity>

<EntityID
xmlns:np="http://schemas.microsoft.com/sqlserver/2004/10/semanticmodeling/udmmodeling">np:Entity_Dimension_DimGeneric</EntityID>
</BaseEntity>
<Groupings>
<Grouping Name="Generic Description">
<Expression Name="Generic Description">
<AttributeRef>

<AttributeID
xmlns:np="http://schemas.microsoft.com/sqlserver/2004/10/semanticmodeling/udmmodeling">np:Attribute_Hierarchy_Generic.Generic_Description</AttributeID>
</AttributeRef>
</Expression>
</Grouping>
</Groupings>
</Hierarchy>
</Hierarchies>
--start of report builder sourced subtree
<CustomProperties>
<CustomProperty Name="qd:PerspectiveID">
<Value
xsi:type="xsd:string">http://schemas.microsoft.com/sqlserver/2004/10/semanticmodeling/udmmodeling:Perspective_Cube_CubeGeneric</Value>
</CustomProperty>
</CustomProperties>
--end of report builder sourced subtree
</SemanticQuery></CommandText>
<DataSourceName>dataSource1</DataSourceName>
</Query>
<Fields>
<Field Name="Generic_Description">
<rd:TypeName>System.String</rd:TypeName>
<DataField>Generic Description</DataField>
</Field>
</Fields>
</DataSet>
</DataSets>
<Width>16cm</Width>
<InteractiveHeight>29.7cm</InteractiveHeight>
<Language>en-US</Language>
<TopMargin>2.5cm</TopMargin>
<PageHeight>29.7cm</PageHeight>
</Report>I have also noticed that if I open a Report Builder report in Report Designer
and change the data source guid to match the data source in the report server
project, the preview displays the expected results and the generic query
designer view also works as expected, but the "query could not be loaded"
message still appears when attempting to use the data tab without the query
designer.
"David Norman" wrote:
> I have created a report model based on an SSAS database. It is usable without
> errors with Report Builder as far as I can tell. However with Report
> Designer, the layout displays the cube elements but errors on preview as
> follows:
> "The 'PerspectiveId' custom property for the 'query' perspective is either
> not set or is not set to the string data type."
> This is an error that has cropped up before but I'm not aware of a bug
> report for it. The forum and blog guidance I have for fixing it is to:
> - Create a report builder report and save it to file
> - Copy the customproperties xml subtree and paste it into the Report
> Designer report
> I have done this but unfortunately this also errors on reopening the report
> as follows:
> "A connection cannot be made to the database. Set and test the connection
> string. Additional information: TODO - change code to use RsProxy object
> (Microsoft.ReportingServices.QueryDesigners)"
> Notwithstanding the slightly disconcerting TODO comment lingering in the
> code, can anyone advise cause and resolution/workaround?
> Thanks in advance
> David
> using:
> - SQL Server 2005 Analysis Services 9.0.3042
> - Windows XP Pro SP2
> - Visual Studio 2005 SP1
> -- report designer rdl follows
> --
> <?xml version="1.0" encoding="utf-8"?>
> <Report
> xmlns="http://schemas.microsoft.com/sqlserver/reporting/2005/01/reportdefinition"
> xmlns:rd="">http://schemas.microsoft.com/SQLServer/reporting/reportdesigner">
> <DataSources>
> <DataSource Name="dataSource1">
> <DataSourceReference>dataSource1</DataSourceReference>
> <rd:DataSourceID>6d24178d-90d5-486e-a311-a4d939b769ea</rd:DataSourceID>
> </DataSource>
> </DataSources>
> <BottomMargin>2.5cm</BottomMargin>
> <RightMargin>2.5cm</RightMargin>
> <PageWidth>21cm</PageWidth>
> <rd:DrawGrid>true</rd:DrawGrid>
> <InteractiveWidth>21cm</InteractiveWidth>
> <rd:GridSpacing>0.25cm</rd:GridSpacing>
> <rd:SnapToGrid>true</rd:SnapToGrid>
> <Body>
> <ColumnSpacing>1cm</ColumnSpacing>
> <Height>5cm</Height>
> </Body>
> <rd:ReportID>cdfcad95-4a03-4a8d-82a6-048cac98eb26</rd:ReportID>
> <LeftMargin>2.5cm</LeftMargin>
> <DataSets>
> <DataSet Name="DataSet1">
> <Query>
> <CommandText><SemanticQuery
> xmlns="http://schemas.microsoft.com/sqlserver/2004/10/semanticmodeling"
> xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> xmlns:qd="http://schemas.microsoft.com/sqlserver/2004/11/semanticquerydesign"
> xmlns:rb="">http://schemas.microsoft.com/sqlserver/2004/11/reportbuilder">
> <Hierarchies>
> <Hierarchy>
> <BaseEntity>
> 
> <EntityID
> xmlns:np="np:Entity_Dimension_DimGeneric</EntityID>">http://schemas.microsoft.com/sqlserver/2004/10/semanticmodeling/udmmodeling">np:Entity_Dimension_DimGeneric</EntityID>
> </BaseEntity>
> <Groupings>
> <Grouping Name="Generic Description">
> <Expression Name="Generic Description">
> <AttributeRef>
> 
> <AttributeID
> xmlns:np="np:Attribute_Hierarchy_Generic.Generic_Description</AttributeID>">http://schemas.microsoft.com/sqlserver/2004/10/semanticmodeling/udmmodeling">np:Attribute_Hierarchy_Generic.Generic_Description</AttributeID>
> </AttributeRef>
> </Expression>
> </Grouping>
> </Groupings>
> </Hierarchy>
> </Hierarchies>
> --start of report builder sourced subtree
> <CustomProperties>
> <CustomProperty Name="qd:PerspectiveID">
> <Value
> xsi:type="xsd:string">http://schemas.microsoft.com/sqlserver/2004/10/semanticmodeling/udmmodeling:Perspective_Cube_CubeGeneric</Value>
> </CustomProperty>
> </CustomProperties>
> --end of report builder sourced subtree
> </SemanticQuery></CommandText>
> <DataSourceName>dataSource1</DataSourceName>
> </Query>
> <Fields>
> <Field Name="Generic_Description">
> <rd:TypeName>System.String</rd:TypeName>
> <DataField>Generic Description</DataField>
> </Field>
> </Fields>
> </DataSet>
> </DataSets>
> <Width>16cm</Width>
> <InteractiveHeight>29.7cm</InteractiveHeight>
> <Language>en-US</Language>
> <TopMargin>2.5cm</TopMargin>
> <PageHeight>29.7cm</PageHeight>
> </Report>|||It appears this error does not occur for the same report model on a PC which
doesn't have VS2005 SP1 installed!
"David Norman" wrote:
> I have also noticed that if I open a Report Builder report in Report Designer
> and change the data source guid to match the data source in the report server
> project, the preview displays the expected results and the generic query
> designer view also works as expected, but the "query could not be loaded"
> message still appears when attempting to use the data tab without the query
> designer.
> "David Norman" wrote:
> > I have created a report model based on an SSAS database. It is usable without
> > errors with Report Builder as far as I can tell. However with Report
> > Designer, the layout displays the cube elements but errors on preview as
> > follows:
> >
> > "The 'PerspectiveId' custom property for the 'query' perspective is either
> > not set or is not set to the string data type."
> >
> > This is an error that has cropped up before but I'm not aware of a bug
> > report for it. The forum and blog guidance I have for fixing it is to:
> >
> > - Create a report builder report and save it to file
> > - Copy the customproperties xml subtree and paste it into the Report
> > Designer report
> >
> > I have done this but unfortunately this also errors on reopening the report
> > as follows:
> >
> > "A connection cannot be made to the database. Set and test the connection
> > string. Additional information: TODO - change code to use RsProxy object
> > (Microsoft.ReportingServices.QueryDesigners)"
> >
> > Notwithstanding the slightly disconcerting TODO comment lingering in the
> > code, can anyone advise cause and resolution/workaround?
> >
> > Thanks in advance
> > David
> >
> > using:
> > - SQL Server 2005 Analysis Services 9.0.3042
> > - Windows XP Pro SP2
> > - Visual Studio 2005 SP1
> >
> > -- report designer rdl follows
> > --
> >
> > <?xml version="1.0" encoding="utf-8"?>
> > <Report
> > xmlns="http://schemas.microsoft.com/sqlserver/reporting/2005/01/reportdefinition"
> > xmlns:rd="">http://schemas.microsoft.com/SQLServer/reporting/reportdesigner">
> > <DataSources>
> > <DataSource Name="dataSource1">
> > <DataSourceReference>dataSource1</DataSourceReference>
> > <rd:DataSourceID>6d24178d-90d5-486e-a311-a4d939b769ea</rd:DataSourceID>
> > </DataSource>
> > </DataSources>
> > <BottomMargin>2.5cm</BottomMargin>
> > <RightMargin>2.5cm</RightMargin>
> > <PageWidth>21cm</PageWidth>
> > <rd:DrawGrid>true</rd:DrawGrid>
> > <InteractiveWidth>21cm</InteractiveWidth>
> > <rd:GridSpacing>0.25cm</rd:GridSpacing>
> > <rd:SnapToGrid>true</rd:SnapToGrid>
> > <Body>
> > <ColumnSpacing>1cm</ColumnSpacing>
> > <Height>5cm</Height>
> > </Body>
> > <rd:ReportID>cdfcad95-4a03-4a8d-82a6-048cac98eb26</rd:ReportID>
> > <LeftMargin>2.5cm</LeftMargin>
> > <DataSets>
> > <DataSet Name="DataSet1">
> > <Query>
> > <CommandText><SemanticQuery
> > xmlns="http://schemas.microsoft.com/sqlserver/2004/10/semanticmodeling"
> > xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> > xmlns:qd="http://schemas.microsoft.com/sqlserver/2004/11/semanticquerydesign"
> > xmlns:rb="">http://schemas.microsoft.com/sqlserver/2004/11/reportbuilder">
> > <Hierarchies>
> > <Hierarchy>
> > <BaseEntity>
> > 
> > <EntityID
> > xmlns:np="np:Entity_Dimension_DimGeneric</EntityID>">http://schemas.microsoft.com/sqlserver/2004/10/semanticmodeling/udmmodeling">np:Entity_Dimension_DimGeneric</EntityID>
> > </BaseEntity>
> > <Groupings>
> > <Grouping Name="Generic Description">
> > <Expression Name="Generic Description">
> > <AttributeRef>
> > 
> > <AttributeID
> > xmlns:np="np:Attribute_Hierarchy_Generic.Generic_Description</AttributeID>">http://schemas.microsoft.com/sqlserver/2004/10/semanticmodeling/udmmodeling">np:Attribute_Hierarchy_Generic.Generic_Description</AttributeID>
> > </AttributeRef>
> > </Expression>
> > </Grouping>
> > </Groupings>
> > </Hierarchy>
> > </Hierarchies>
> >
> > --start of report builder sourced subtree
> >
> > <CustomProperties>
> > <CustomProperty Name="qd:PerspectiveID">
> > <Value
> > xsi:type="xsd:string">http://schemas.microsoft.com/sqlserver/2004/10/semanticmodeling/udmmodeling:Perspective_Cube_CubeGeneric</Value>
> > </CustomProperty>
> > </CustomProperties>
> >
> > --end of report builder sourced subtree
> >
> > </SemanticQuery></CommandText>
> > <DataSourceName>dataSource1</DataSourceName>
> > </Query>
> > <Fields>
> > <Field Name="Generic_Description">
> > <rd:TypeName>System.String</rd:TypeName>
> > <DataField>Generic Description</DataField>
> > </Field>
> > </Fields>
> > </DataSet>
> > </DataSets>
> > <Width>16cm</Width>
> > <InteractiveHeight>29.7cm</InteractiveHeight>
> > <Language>en-US</Language>
> > <TopMargin>2.5cm</TopMargin>
> > <PageHeight>29.7cm</PageHeight>
> > </Report>|||I finally found a bug report on Connect for SQL Server 2005 SP2 (Client Tools)
http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=260746
Microsoft will "consider fixing it in a future release". There is no
workaround listed, and I have found nothing better than selectively removing
and adding the customproperties subtree to enable different parts of the
report designer (which of course is a big nuisance).
BTW thanks world for not replying to my posts!
"David Norman" wrote:
> It appears this error does not occur for the same report model on a PC which
> doesn't have VS2005 SP1 installed!
> "David Norman" wrote:
> > I have also noticed that if I open a Report Builder report in Report Designer
> > and change the data source guid to match the data source in the report server
> > project, the preview displays the expected results and the generic query
> > designer view also works as expected, but the "query could not be loaded"
> > message still appears when attempting to use the data tab without the query
> > designer.
> >
> > "David Norman" wrote:
> >
> > > I have created a report model based on an SSAS database. It is usable without
> > > errors with Report Builder as far as I can tell. However with Report
> > > Designer, the layout displays the cube elements but errors on preview as
> > > follows:
> > >
> > > "The 'PerspectiveId' custom property for the 'query' perspective is either
> > > not set or is not set to the string data type."
> > >
> > > This is an error that has cropped up before but I'm not aware of a bug
> > > report for it. The forum and blog guidance I have for fixing it is to:
> > >
> > > - Create a report builder report and save it to file
> > > - Copy the customproperties xml subtree and paste it into the Report
> > > Designer report
> > >
> > > I have done this but unfortunately this also errors on reopening the report
> > > as follows:
> > >
> > > "A connection cannot be made to the database. Set and test the connection
> > > string. Additional information: TODO - change code to use RsProxy object
> > > (Microsoft.ReportingServices.QueryDesigners)"
> > >
> > > Notwithstanding the slightly disconcerting TODO comment lingering in the
> > > code, can anyone advise cause and resolution/workaround?
> > >
> > > Thanks in advance
> > > David
> > >
> > > using:
> > > - SQL Server 2005 Analysis Services 9.0.3042
> > > - Windows XP Pro SP2
> > > - Visual Studio 2005 SP1
> > >
> > > -- report designer rdl follows
> > > --
> > >
> > > <?xml version="1.0" encoding="utf-8"?>
> > > <Report
> > > xmlns="http://schemas.microsoft.com/sqlserver/reporting/2005/01/reportdefinition"
> > > xmlns:rd="">http://schemas.microsoft.com/SQLServer/reporting/reportdesigner">
> > > <DataSources>
> > > <DataSource Name="dataSource1">
> > > <DataSourceReference>dataSource1</DataSourceReference>
> > > <rd:DataSourceID>6d24178d-90d5-486e-a311-a4d939b769ea</rd:DataSourceID>
> > > </DataSource>
> > > </DataSources>
> > > <BottomMargin>2.5cm</BottomMargin>
> > > <RightMargin>2.5cm</RightMargin>
> > > <PageWidth>21cm</PageWidth>
> > > <rd:DrawGrid>true</rd:DrawGrid>
> > > <InteractiveWidth>21cm</InteractiveWidth>
> > > <rd:GridSpacing>0.25cm</rd:GridSpacing>
> > > <rd:SnapToGrid>true</rd:SnapToGrid>
> > > <Body>
> > > <ColumnSpacing>1cm</ColumnSpacing>
> > > <Height>5cm</Height>
> > > </Body>
> > > <rd:ReportID>cdfcad95-4a03-4a8d-82a6-048cac98eb26</rd:ReportID>
> > > <LeftMargin>2.5cm</LeftMargin>
> > > <DataSets>
> > > <DataSet Name="DataSet1">
> > > <Query>
> > > <CommandText><SemanticQuery
> > > xmlns="http://schemas.microsoft.com/sqlserver/2004/10/semanticmodeling"
> > > xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> > > xmlns:qd="http://schemas.microsoft.com/sqlserver/2004/11/semanticquerydesign"
> > > xmlns:rb="">http://schemas.microsoft.com/sqlserver/2004/11/reportbuilder">
> > > <Hierarchies>
> > > <Hierarchy>
> > > <BaseEntity>
> > > 
> > > <EntityID
> > > xmlns:np="np:Entity_Dimension_DimGeneric</EntityID>">http://schemas.microsoft.com/sqlserver/2004/10/semanticmodeling/udmmodeling">np:Entity_Dimension_DimGeneric</EntityID>
> > > </BaseEntity>
> > > <Groupings>
> > > <Grouping Name="Generic Description">
> > > <Expression Name="Generic Description">
> > > <AttributeRef>
> > > 
> > > <AttributeID
> > > xmlns:np="np:Attribute_Hierarchy_Generic.Generic_Description</AttributeID>">http://schemas.microsoft.com/sqlserver/2004/10/semanticmodeling/udmmodeling">np:Attribute_Hierarchy_Generic.Generic_Description</AttributeID>
> > > </AttributeRef>
> > > </Expression>
> > > </Grouping>
> > > </Groupings>
> > > </Hierarchy>
> > > </Hierarchies>
> > >
> > > --start of report builder sourced subtree
> > >
> > > <CustomProperties>
> > > <CustomProperty Name="qd:PerspectiveID">
> > > <Value
> > > xsi:type="xsd:string">http://schemas.microsoft.com/sqlserver/2004/10/semanticmodeling/udmmodeling:Perspective_Cube_CubeGeneric</Value>
> > > </CustomProperty>
> > > </CustomProperties>
> > >
> > > --end of report builder sourced subtree
> > >
> > > </SemanticQuery></CommandText>
> > > <DataSourceName>dataSource1</DataSourceName>
> > > </Query>
> > > <Fields>
> > > <Field Name="Generic_Description">
> > > <rd:TypeName>System.String</rd:TypeName>
> > > <DataField>Generic Description</DataField>
> > > </Field>
> > > </Fields>
> > > </DataSet>
> > > </DataSets>
> > > <Width>16cm</Width>
> > > <InteractiveHeight>29.7cm</InteractiveHeight>
> > > <Language>en-US</Language>
> > > <TopMargin>2.5cm</TopMargin>
> > > <PageHeight>29.7cm</PageHeight>
> > > </Report>|||This is peer supported. Plus, MS people do not tend to be here. Although if
you have MSDN subscription you can do a managed newsgroup where you register
an alias and they guarantee I believe an answer in two days.
The fact no one answered means that people doing this for no pay and just
because they want to help did not jump in because they did not know an
answer.
In the future if you do not get an answer here you might try the web forums.
Different people hang out there and also more MS people hang out there.
http://forums.microsoft.com/msdn/showforum.aspx?forumid=82&siteid=1
Oh, by the way. I assume at some point you might want help in the future.
Being hostile is a great way to get someone to help.
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"David Norman" <DavidNorman@.discussions.microsoft.com> wrote in message
news:EEE6DAE4-46BB-4D6F-9E98-790176EBC0F9@.microsoft.com...
>I finally found a bug report on Connect for SQL Server 2005 SP2 (Client
>Tools)
> http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=260746
> Microsoft will "consider fixing it in a future release". There is no
> workaround listed, and I have found nothing better than selectively
> removing
> and adding the customproperties subtree to enable different parts of the
> report designer (which of course is a big nuisance).
> BTW thanks world for not replying to my posts!
> "David Norman" wrote:
>> It appears this error does not occur for the same report model on a PC
>> which
>> doesn't have VS2005 SP1 installed!
>> "David Norman" wrote:
>> > I have also noticed that if I open a Report Builder report in Report
>> > Designer
>> > and change the data source guid to match the data source in the report
>> > server
>> > project, the preview displays the expected results and the generic
>> > query
>> > designer view also works as expected, but the "query could not be
>> > loaded"
>> > message still appears when attempting to use the data tab without the
>> > query
>> > designer.
>> >
>> > "David Norman" wrote:
>> >
>> > > I have created a report model based on an SSAS database. It is usable
>> > > without
>> > > errors with Report Builder as far as I can tell. However with Report
>> > > Designer, the layout displays the cube elements but errors on preview
>> > > as
>> > > follows:
>> > >
>> > > "The 'PerspectiveId' custom property for the 'query' perspective is
>> > > either
>> > > not set or is not set to the string data type."
>> > >
>> > > This is an error that has cropped up before but I'm not aware of a
>> > > bug
>> > > report for it. The forum and blog guidance I have for fixing it is
>> > > to:
>> > >
>> > > - Create a report builder report and save it to file
>> > > - Copy the customproperties xml subtree and paste it into the Report
>> > > Designer report
>> > >
>> > > I have done this but unfortunately this also errors on reopening the
>> > > report
>> > > as follows:
>> > >
>> > > "A connection cannot be made to the database. Set and test the
>> > > connection
>> > > string. Additional information: TODO - change code to use RsProxy
>> > > object
>> > > (Microsoft.ReportingServices.QueryDesigners)"
>> > >
>> > > Notwithstanding the slightly disconcerting TODO comment lingering in
>> > > the
>> > > code, can anyone advise cause and resolution/workaround?
>> > >
>> > > Thanks in advance
>> > > David
>> > >
>> > > using:
>> > > - SQL Server 2005 Analysis Services 9.0.3042
>> > > - Windows XP Pro SP2
>> > > - Visual Studio 2005 SP1
>> > >
>> > > -- report designer rdl follows
>> > > --
>> > >
>> > > <?xml version="1.0" encoding="utf-8"?>
>> > > <Report
>> > > xmlns="http://schemas.microsoft.com/sqlserver/reporting/2005/01/reportdefinition"
>> > > xmlns:rd="">http://schemas.microsoft.com/SQLServer/reporting/reportdesigner">
>> > > <DataSources>
>> > > <DataSource Name="dataSource1">
>> > > <DataSourceReference>dataSource1</DataSourceReference>
>> > >
>> > > <rd:DataSourceID>6d24178d-90d5-486e-a311-a4d939b769ea</rd:DataSourceID>
>> > > </DataSource>
>> > > </DataSources>
>> > > <BottomMargin>2.5cm</BottomMargin>
>> > > <RightMargin>2.5cm</RightMargin>
>> > > <PageWidth>21cm</PageWidth>
>> > > <rd:DrawGrid>true</rd:DrawGrid>
>> > > <InteractiveWidth>21cm</InteractiveWidth>
>> > > <rd:GridSpacing>0.25cm</rd:GridSpacing>
>> > > <rd:SnapToGrid>true</rd:SnapToGrid>
>> > > <Body>
>> > > <ColumnSpacing>1cm</ColumnSpacing>
>> > > <Height>5cm</Height>
>> > > </Body>
>> > > <rd:ReportID>cdfcad95-4a03-4a8d-82a6-048cac98eb26</rd:ReportID>
>> > > <LeftMargin>2.5cm</LeftMargin>
>> > > <DataSets>
>> > > <DataSet Name="DataSet1">
>> > > <Query>
>> > > <CommandText><SemanticQuery
>> > > xmlns="http://schemas.microsoft.com/sqlserver/2004/10/semanticmodeling"
>> > > xmlns:xsd="http://www.w3.org/2001/XMLSchema"
>> > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
>> > > xmlns:qd="http://schemas.microsoft.com/sqlserver/2004/11/semanticquerydesign"
>> > > xmlns:rb="">http://schemas.microsoft.com/sqlserver/2004/11/reportbuilder">
>> > > <Hierarchies>
>> > > <Hierarchy>
>> > > <BaseEntity>
>> > > 
>> > > <EntityID
>> > > xmlns:np="np:Entity_Dimension_DimGeneric</EntityID>">http://schemas.microsoft.com/sqlserver/2004/10/semanticmodeling/udmmodeling">np:Entity_Dimension_DimGeneric</EntityID>
>> > > </BaseEntity>
>> > > <Groupings>
>> > > <Grouping Name="Generic Description">
>> > > <Expression Name="Generic Description">
>> > > <AttributeRef>
>> > > 
>> > > <AttributeID
>> > > xmlns:np="np:Attribute_Hierarchy_Generic.Generic_Description</AttributeID>">http://schemas.microsoft.com/sqlserver/2004/10/semanticmodeling/udmmodeling">np:Attribute_Hierarchy_Generic.Generic_Description</AttributeID>
>> > > </AttributeRef>
>> > > </Expression>
>> > > </Grouping>
>> > > </Groupings>
>> > > </Hierarchy>
>> > > </Hierarchies>
>> > >
>> > > --start of report builder sourced subtree
>> > >
>> > > <CustomProperties>
>> > > <CustomProperty Name="qd:PerspectiveID">
>> > > <Value
>> > > xsi:type="xsd:string">http://schemas.microsoft.com/sqlserver/2004/10/semanticmodeling/udmmodeling:Perspective_Cube_CubeGeneric</Value>
>> > > </CustomProperty>
>> > > </CustomProperties>
>> > >
>> > > --end of report builder sourced subtree
>> > >
>> > > </SemanticQuery></CommandText>
>> > > <DataSourceName>dataSource1</DataSourceName>
>> > > </Query>
>> > > <Fields>
>> > > <Field Name="Generic_Description">
>> > > <rd:TypeName>System.String</rd:TypeName>
>> > > <DataField>Generic Description</DataField>
>> > > </Field>
>> > > </Fields>
>> > > </DataSet>
>> > > </DataSets>
>> > > <Width>16cm</Width>
>> > > <InteractiveHeight>29.7cm</InteractiveHeight>
>> > > <Language>en-US</Language>
>> > > <TopMargin>2.5cm</TopMargin>
>> > > <PageHeight>29.7cm</PageHeight>
>> > > </Report>|||Didn't intend to be hostile, sorry it came across that way. Hope someone gets
some benefit from my investigations.
"Bruce L-C [MVP]" wrote:
> This is peer supported. Plus, MS people do not tend to be here. Although if
> you have MSDN subscription you can do a managed newsgroup where you register
> an alias and they guarantee I believe an answer in two days.
> The fact no one answered means that people doing this for no pay and just
> because they want to help did not jump in because they did not know an
> answer.
> In the future if you do not get an answer here you might try the web forums.
> Different people hang out there and also more MS people hang out there.
> http://forums.microsoft.com/msdn/showforum.aspx?forumid=82&siteid=1
> Oh, by the way. I assume at some point you might want help in the future.
> Being hostile is a great way to get someone to help.
>
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
>
> "David Norman" <DavidNorman@.discussions.microsoft.com> wrote in message
> news:EEE6DAE4-46BB-4D6F-9E98-790176EBC0F9@.microsoft.com...
> >I finally found a bug report on Connect for SQL Server 2005 SP2 (Client
> >Tools)
> >
> > http://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=260746
> >
> > Microsoft will "consider fixing it in a future release". There is no
> > workaround listed, and I have found nothing better than selectively
> > removing
> > and adding the customproperties subtree to enable different parts of the
> > report designer (which of course is a big nuisance).
> >
> > BTW thanks world for not replying to my posts!
> >
> > "David Norman" wrote:
> >
> >> It appears this error does not occur for the same report model on a PC
> >> which
> >> doesn't have VS2005 SP1 installed!
> >>
> >> "David Norman" wrote:
> >>
> >> > I have also noticed that if I open a Report Builder report in Report
> >> > Designer
> >> > and change the data source guid to match the data source in the report
> >> > server
> >> > project, the preview displays the expected results and the generic
> >> > query
> >> > designer view also works as expected, but the "query could not be
> >> > loaded"
> >> > message still appears when attempting to use the data tab without the
> >> > query
> >> > designer.
> >> >
> >> > "David Norman" wrote:
> >> >
> >> > > I have created a report model based on an SSAS database. It is usable
> >> > > without
> >> > > errors with Report Builder as far as I can tell. However with Report
> >> > > Designer, the layout displays the cube elements but errors on preview
> >> > > as
> >> > > follows:
> >> > >
> >> > > "The 'PerspectiveId' custom property for the 'query' perspective is
> >> > > either
> >> > > not set or is not set to the string data type."
> >> > >
> >> > > This is an error that has cropped up before but I'm not aware of a
> >> > > bug
> >> > > report for it. The forum and blog guidance I have for fixing it is
> >> > > to:
> >> > >
> >> > > - Create a report builder report and save it to file
> >> > > - Copy the customproperties xml subtree and paste it into the Report
> >> > > Designer report
> >> > >
> >> > > I have done this but unfortunately this also errors on reopening the
> >> > > report
> >> > > as follows:
> >> > >
> >> > > "A connection cannot be made to the database. Set and test the
> >> > > connection
> >> > > string. Additional information: TODO - change code to use RsProxy
> >> > > object
> >> > > (Microsoft.ReportingServices.QueryDesigners)"
> >> > >
> >> > > Notwithstanding the slightly disconcerting TODO comment lingering in
> >> > > the
> >> > > code, can anyone advise cause and resolution/workaround?
> >> > >
> >> > > Thanks in advance
> >> > > David
> >> > >
> >> > > using:
> >> > > - SQL Server 2005 Analysis Services 9.0.3042
> >> > > - Windows XP Pro SP2
> >> > > - Visual Studio 2005 SP1
> >> > >
> >> > > -- report designer rdl follows
> >> > > --
> >> > >
> >> > > <?xml version="1.0" encoding="utf-8"?>
> >> > > <Report
> >> > > xmlns="http://schemas.microsoft.com/sqlserver/reporting/2005/01/reportdefinition"
> >> > > xmlns:rd="">http://schemas.microsoft.com/SQLServer/reporting/reportdesigner">
> >> > > <DataSources>
> >> > > <DataSource Name="dataSource1">
> >> > > <DataSourceReference>dataSource1</DataSourceReference>
> >> > >
> >> > > <rd:DataSourceID>6d24178d-90d5-486e-a311-a4d939b769ea</rd:DataSourceID>
> >> > > </DataSource>
> >> > > </DataSources>
> >> > > <BottomMargin>2.5cm</BottomMargin>
> >> > > <RightMargin>2.5cm</RightMargin>
> >> > > <PageWidth>21cm</PageWidth>
> >> > > <rd:DrawGrid>true</rd:DrawGrid>
> >> > > <InteractiveWidth>21cm</InteractiveWidth>
> >> > > <rd:GridSpacing>0.25cm</rd:GridSpacing>
> >> > > <rd:SnapToGrid>true</rd:SnapToGrid>
> >> > > <Body>
> >> > > <ColumnSpacing>1cm</ColumnSpacing>
> >> > > <Height>5cm</Height>
> >> > > </Body>
> >> > > <rd:ReportID>cdfcad95-4a03-4a8d-82a6-048cac98eb26</rd:ReportID>
> >> > > <LeftMargin>2.5cm</LeftMargin>
> >> > > <DataSets>
> >> > > <DataSet Name="DataSet1">
> >> > > <Query>
> >> > > <CommandText><SemanticQuery
> >> > > xmlns="http://schemas.microsoft.com/sqlserver/2004/10/semanticmodeling"
> >> > > xmlns:xsd="http://www.w3.org/2001/XMLSchema"
> >> > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
> >> > > xmlns:qd="http://schemas.microsoft.com/sqlserver/2004/11/semanticquerydesign"
> >> > > xmlns:rb="">http://schemas.microsoft.com/sqlserver/2004/11/reportbuilder">
> >> > > <Hierarchies>
> >> > > <Hierarchy>
> >> > > <BaseEntity>
> >> > > 
> >> > > <EntityID
> >> > > xmlns:np="np:Entity_Dimension_DimGeneric</EntityID>">http://schemas.microsoft.com/sqlserver/2004/10/semanticmodeling/udmmodeling">np:Entity_Dimension_DimGeneric</EntityID>
> >> > > </BaseEntity>
> >> > > <Groupings>
> >> > > <Grouping Name="Generic Description">
> >> > > <Expression Name="Generic Description">
> >> > > <AttributeRef>
> >> > > 
> >> > > <AttributeID
> >> > > xmlns:np="np:Attribute_Hierarchy_Generic.Generic_Description</AttributeID>">http://schemas.microsoft.com/sqlserver/2004/10/semanticmodeling/udmmodeling">np:Attribute_Hierarchy_Generic.Generic_Description</AttributeID>
> >> > > </AttributeRef>
> >> > > </Expression>
> >> > > </Grouping>
> >> > > </Groupings>
> >> > > </Hierarchy>
> >> > > </Hierarchies>
> >> > >
> >> > > --start of report builder sourced subtree
> >> > >
> >> > > <CustomProperties>
> >> > > <CustomProperty Name="qd:PerspectiveID">
> >> > > <Value
> >> > > xsi:type="xsd:string">http://schemas.microsoft.com/sqlserver/2004/10/semanticmodeling/udmmodeling:Perspective_Cube_CubeGeneric</Value>
> >> > > </CustomProperty>
> >> > > </CustomProperties>
> >> > >
> >> > > --end of report builder sourced subtree
> >> > >
> >> > > </SemanticQuery></CommandText>
> >> > > <DataSourceName>dataSource1</DataSourceName>
> >> > > </Query>
> >> > > <Fields>
> >> > > <Field Name="Generic_Description">
> >> > > <rd:TypeName>System.String</rd:TypeName>
> >> > > <DataField>Generic Description</DataField>
> >> > > </Field>
> >> > > </Fields>
> >> > > </DataSet>
> >> > > </DataSets>
> >> > > <Width>16cm</Width>
> >> > > <InteractiveHeight>29.7cm</InteractiveHeight>
> >> > > <Language>en-US</Language>
> >> > > <TopMargin>2.5cm</TopMargin>
> >> > > <PageHeight>29.7cm</PageHeight>
> >> > > </Report>
>
>sql

Monday, March 19, 2012

Errors processing data from Oracle to SQL

hi here′s a new one.....
i′ve created a dts that is using an odbc source to connect to an oracle server, the conexion works just fine and i have no problems with it, then, i run this package from mi computer and the data transfer ends succesfully, when i upload it to my server in SQL 2005 and set it into a job.. i get errors like these:

Event Name: OnError
Message: Thread "WorkThread0" has exited with error code 0xC0047039.

Event Name: OnError
Message: 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.

Event Name: OnError
Message: The PrimeOutput method on component "table" (1) 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.

Event Name: OnError
Message: The component "faccomitecedidos" (1) was unable to process the data.

Event Name: OnError
Message: The "component "table" (1)" failed because error code 0x80131541 occurred, and the error row disposition on "output column "diasperm" (1707)" specifies failure on error. An error occurred on the specified object of the specified component.

why is this happening , any solutions or ideas? the data i want to extract comes from an sql command not a table
this is the query:

SELECT
FCNSS ,
FITIPOSOLICITUD ,
FIFOLIO ,
RTRIM(FCNOMBRE)||' '||RTRIM(FCAPPATERNO)||' '||RTRIM(FCAPMATERNO) AS NOMBREAFILIADO,
fdfinicta as FAFIL ,
fdFecCedido as FCED ,
(fdFecCedido-fdfinicta) AS diasperm ,
FNSALARIOACTUAL AS SALAFIL ,
(SELECT DISTINCT FISDI FROM gentec_own.AFILCEDIDOS WHERE
FIFOLIO = gentec_own.faccomite.FIFOLIO AND FITIPOSOLICITUD = gentec_own.faccomite.FITIPOSOLICITUD AND FCNSS = gentec_own.faccomite.FCNSS AND ROWNUM = 1) AS salCED ,
(SELECT DISTINCT (FISDI/48.60) FROM gentec_own.AFILCEDIDOS WHERE
FIFOLIO = gentec_own.faccomite.FIFOLIO AND FITIPOSOLICITUD = gentec_own.faccomite.FITIPOSOLICITUD AND FCNSS = gentec_own.faccomite.FCNSS AND ROWNUM = 1) AS CalSalCED ,
FCNUMPROMOTOR AS cod_promotor,
(SELECT RTRIM(FCNOMBRES)||' '||RTRIM(FCAPEPATERNO)||' '||RTRIM(FCAPEMATERNO)
FROM gentec_own.prommaestro where FCNUMPROMOTOR = gentec_own.faccomite.FCNUMPROMOTOR AND ROWNUM = 1) AS NOMPROMOTOR,
FICVEENTCED as aforeorig ,
FCAFORECEDIDO as aforeced ,
FNINGCOMT ,
FNCTOPROMOCION ,
FNCTOADMON ,
FNCONTRIBUCION ,
fcCanal as Canal ,
FCDIVISION as Division ,
FCREGION as Gerencia
FROM gentec_own.FACCOMITE
WHERE FCCEDIDO = 1
and (to_char(fdFecCedido,'yyyymmdd')>=to_char(sysdate-8,'yyyymmdd') and to_char(fdFecCedido,'yyyymmdd')< to_char(sysdate,'yyyymmdd'))
order by fdFecCedido;

please!!!1 somebody

maybe the problem is here:

(fdFecCedido-fdfinicta) AS diasperm

|||

hi unfortunately this wasn′t the error, i tried changing the query for a view in the oracle server but the error is stil the same

Event Name: OnError

Message: The "component "DataReader Source" (1)" failed because error code 0x80131541 occurred, and the error row disposition on "output column "DIASPERM" (404)" specifies failure on error. An error occurred on the specified object of the specified component.

and the query is just :

select * from db.view

and that′s it.... any posible solutions? is there any complications if the server where i′m running the job is under 64 bits and the dts ′s been created under 32 bits? if so. where can i find a 32 bits odbc driver for oracle that i may install in the target server!!!! please!!!!!!!!!!

|||

It looks like a SQL syntax problem. If you try to issue your entire original statement DIRECTLY against your oracle database, do you not get an error?

It seems to me that you need to tie back your results to the main query as you did here:

(SELECT DISTINCT FISDI FROM gentec_own.AFILCEDIDOS WHERE
FIFOLIO = gentec_own.faccomite.FIFOLIO AND FITIPOSOLICITUD = gentec_own.faccomite.FITIPOSOLICITUD AND FCNSS = gentec_own.faccomite.FCNSS AND ROWNUM = 1) AS salCED ,

|||

i don′t think this is a problem of syntax cause i run the query directly on the oracle db and it works, it seems more like a problem of windows version, since i run this dts on my 32 bits pc i get the results without problems.. the problem comes when uploading the package to the target server that is running under 64 bits, to do this i'm using an 32bits odbc oracle driver but the odbc that is used in the target server seems to be under 64 bits , because of this, i'd like to try using the same kind of odbc so, where can i get
one?

a 32 bits odbc driver for oracle that works in a server running in 64 bits mode

pleaseee

Errors not logged

Hi :

I have created the followign ddl trigger to log all the ddl activities. It is workign fine for all the sucessfully created objects.

The problem is, how do i log errors also. Like if i am trying to create a table with same name twice then the trigger should log a stmt saying that the table already exists in the database. or while creating synonyms twice with same name, etc

I want to log all the failed DDL stmts also.

Any solution will be of good help to me.

CREATE TRIGGER [DDLLogging] ON DATABASE
FOR DDL_DATABASE_LEVEL_EVENTS AS
BEGIN
SET NOCOUNT ON;

DECLARE @.data XML;
DECLARE @.schema sysname;
DECLARE @.object sysname;
DECLARE @.eventType sysname;

DECLARE @.logstmt varchar(500);

DECLARE @.query VARCHAR(255)
DECLARE @.file VARCHAR(255)

SET @.data = EVENTDATA();
SET @.eventType = @.data.value('(/EVENT_INSTANCE/EventType)[1]', 'sysname');
SET @.schema = @.data.value('(/EVENT_INSTANCE/SchemaName)[1]', 'sysname');
SET @.object = @.data.value('(/EVENT_INSTANCE/ObjectName)[1]', 'sysname')
SET @.file = 'c:\xzy\'+REPLACE(CONVERT(char(10),GETDATE(),111),'/','_')+'.log'

IF @.object IS NOT NULL
BEGIN
SET @.logstmt = CONVERT(varchar(20),GETDATE(),9) + ', ' + @.eventType + ' ' + @.object + ' successful';
SET @.query = RTRIM('echo ' + COALESCE(LTRIM(@.logstmt),'-') + ' >> ' + RTRIM(@.file))
EXEC master..xp_cmdshell @.query, NO_OUTPUT
END
ELSE
BEGIN
SET @.logstmt = CONVERT(varchar(20),GETDATE(),9) + ', ' + @.eventType + ' successful';
SET @.query = RTRIM('echo ' + COALESCE(LTRIM(@.logstmt),'-') + ' >> ' + RTRIM(@.file))
EXEC master..xp_cmdshell @.query, NO_OUTPUT
END

END;

i am using sql express.

|||DDL Triggers only fire for successfully completed DDL. If the DDL fails due to a error like a duplicate object, then the DDL trigger is never fired. If you want to audit error messages for failed DDL, you will have to use profiler or trace to observe the failures.|||

Hi:

Thank you for the reply.

I would like to know if there is any other mechnism to log unsucessfully executed DDL stmt.

All error while executing DDL stmts should be logged into log file.

By looking the log file, we should know which ddl stmts have executed and which have failed.

Please let me know of any solution.

i am using sqlcmd for executing .sql files. SQL Express is my database.

|||

Hi,

there is no builtin way to do this, you can temporary setup profiler to get the exception that come up while using false DDL statement, but using the profiler should only be a temporary solution as it it (in my opinion) very expensive.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

|||

Tracing is more expensive when capturing unneeded columns, when filtering rows (since events are generated no matter what is filtered), and (most importantly) when the trace consumer (i.e., the trace table or the trace file) cannot consume those traced events in an expedient manner. Traces will drive up logical reads. Your experience will depend upon the trace system you design/choose (in geometric addition to load upon the client/server system).

For failed DDL, one should hope that (say) 1000 such events per second (or minute) is never seen , or, you may need to throttle the client (if the rate of DDL failures gets "excessive"). IMO, good development includes scalability testing from about day one (of any project), thus improper tracing should be detectable from about day one .

You can fire up SQL Server Profiler (the GUI) to create a server-side script (best to forbid the GUI in production and strive to avoid the GUI in development), remove the "profiler" filter (if present), and (for that scalability testing) profile the impact of profiler. Just make sure you don't ever overload the consumer's I/O (the consumer must consume quickly), otherwise life will suck.

Keep it short, sweet, and simple. And remember that you cannot squeeze an elephant through the eye of a needle.

Errors in the OLAP storage engine:

Errors in the OLAP storage engine: I am new to Analysis Services. I created a cube using Analysis Services 2005 with 3 fact tables and five dimensions. All the dimensions processed successfully apart from one dimension table which gave the following error. The attribute key cannot be found: Table:
dbo_Severity, Column:
SeverityCode, Value: 6

When i try to deploy the cube, I also fail. Is it because of this dimension table in which the attribute key can not be found.

<Batch xmlns="http://schemas.microsoft.com/analysisservices/2003/engine">
<Parallel>
<Process xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<Object>
<DatabaseID>AnalysisServices</DatabaseID>
<CubeID>MSCPROJECTDSV</CubeID>
</Object>
<Type>ProcessFull</Type>
<WriteBackTableCreation>UseExisting</WriteBackTableCreation>
</Process>
</Parallel>
</Batch>
Processing Dimension 'Allergy' failed.
Start time: 6/14/2006 6:04:32 PM; End time: 6/14/2006 6:05:00 PM; Duration: 0:00:28
Processing Dimension Attribute '(All)' completed successfully.
Start time: 6/14/2006 6:04:32 PM; End time: 6/14/2006 6:04:32 PM; Duration: 0:00:00
Processing Dimension Attribute 'Allergy Name' completed successfully. 7 rows have been read.
Start time: 6/14/2006 6:04:32 PM; End time: 6/14/2006 6:04:41 PM; Duration: 0:00:09
SQL queries 1
SELECT
DISTINCT
[dbo_Allergy].[AllergyName] AS [dbo_AllergyAllergyName0_0]
FROM [dbo].[Allergy] AS [dbo_Allergy]
Processing Dimension Attribute 'Severity Name' completed successfully. 6 rows have been read.
Start time: 6/14/2006 6:04:32 PM; End time: 6/14/2006 6:04:41 PM; Duration: 0:00:09
SQL queries 1
SELECT
DISTINCT
[dbo_Severity].[SeverityName] AS [dbo_SeveritySeverityName0_0]
FROM [dbo].[Severity] AS [dbo_Severity]
Processing Dimension Attribute 'Severity' completed successfully. 6 rows have been read.
Start time: 6/14/2006 6:04:41 PM; End time: 6/14/2006 6:04:51 PM; Duration: 0:00:10
SQL queries 1
SELECT
DISTINCT
[dbo_Severity].[SeverityCode] AS [dbo_SeveritySeverityCode0_0],[dbo_Severity].[SeverityName] AS [dbo_SeveritySeverityName0_1]
FROM [dbo].[Severity] AS [dbo_Severity]
Processing Dimension Attribute 'Allergy' failed. 1 rows have been read.
Start time: 6/14/2006 6:04:51 PM; End time: 6/14/2006 6:05:00 PM; Duration: 0:00:09
SQL queries 1
SELECT
DISTINCT
[dbo_Allergy].[AllergyCode] AS [dbo_AllergyAllergyCode0_0],[dbo_Allergy].[AllergyName] AS [dbo_AllergyAllergyName0_1],[dbo_Allergy].[SeverityCode] AS [dbo_AllergySeverityCode0_2]
FROM [dbo].[Allergy] AS [dbo_Allergy]
Error Messages 2
Errors in the OLAP storage engine: The attribute key cannot be found: Table: dbo_Severity, Column: SeverityCode, Value: 6. Errors in the OLAP storage engine: The record was skipped because the attribute key was not found. Attribute: Allergy of Dimension: Allergy from Database: AnalysisServices, Record: 7.
Errors in the OLAP storage engine: The attribute key cannot be found: Table: dbo_Severity, Column: SeverityCode, Value: 6. Errors in the OLAP storage engine: The record was skipped because the attribute key was not found. Attribute: Allergy of Dimension: Allergy from Database: AnalysisServices, Record: 7. Errors in the OLAP storage engine: The process operation ended because the number of errors encountered during processing reached the defined limit of allowable errors for the operation. Errors in the OLAP storage engine: An error occurred while the 'Allergy' attribute of the 'Allergy' dimension from the 'AnalysisServices' database was being processed.
Errors and Warnings from Response
Errors in the OLAP storage engine: The process operation ended because the number of errors encountered during processing reached the defined limit of allowable errors for the operation.
Errors in the OLAP storage engine: An error occurred while the 'Allergy' attribute of the 'Allergy' dimension from the 'AnalysisServices' database was being processed.
Errors in the OLAP storage engine: The process operation ended because the number of errors encountered during processing reached the defined limit of allowable errors for the operation.
Errors in the OLAP storage engine: The attribute key cannot be found: Table: dbo_Severity, Column: SeverityCode, Value: 6.
Errors in the OLAP storage engine: The record was skipped because the attribute key was not found. Attribute: Allergy of Dimension: Allergy from Database: AnalysisServices, Record: 7.

Please help me out.

Regards,

Ronaldlee

Looks like the problem is in the relational database.

Looks like you have a record in the Allergy table with a value in the SeverirtyCode column that does not exist in the Severity table.

Try first sending a SQL query AS sends for the Severity attribute

Then send a SQL query for the Allergy attribute and see which value appears in the SeverityCode column and does not appear in the Severity table.

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

|||

Thanx a Lot.

You are the man.

Ronald

|||

I have made all the necassary changes,

I have three fact tables in Cube, two of them process successfully, but one doesnot execute successfully.

SELECT 1 AS [dbo_MedicationAllergy0_0],[MedicineCode] AS [dbo_MedicationAllergyMedicineCode0_1]
FROM [dbo].[MedicationAllergy]
)
AS [dbo_MedicationAllergy]
Processing Measure Group 'Prescription' failed.
Start time: 6/15/2006 12:31:24 PM; End time: 6/15/2006 12:31:25 PM; Duration: 0:00:01
Processing Partition 'Prescription' failed.
Start time: 6/15/2006 12:31:25 PM; End time: 6/15/2006 12:31:25 PM; Duration: 0:00:00
SQL queries 1
SELECT [dbo_Prescription].[Quantity] AS [dbo_PrescriptionQuantity0_0],[dbo_Prescription].[Price] AS [dbo_PrescriptionPrice0_1],[dbo_Prescription].[MedicineCode] AS [dbo_PrescriptionMedicineCode0_2],[dbo_Prescription].[PatientId] AS [dbo_PrescriptionPatientId0_3],[dbo_Prescription].[Date] AS [dbo_PrescriptionDate0_4]
FROM [dbo].[Prescription] AS [dbo_Prescription]
Error Messages 2
Errors in the OLAP storage engine: The attribute key cannot be found: Table: dbo_Prescription, Column: PatientId, Value: 10001; Table: dbo_Prescription, Column: Date, Value: 2/9/2000. Errors in the OLAP storage engine: The record was skipped because the attribute key was not found. Attribute: PatientId - Date of Dimension: Return Visit from Database: AnalysisServices, Cube: MSCPROJECTDVS, Measure Group: Prescription, Partition: Prescription, Record: 1.
Errors in the OLAP storage engine: The attribute key cannot be found: Table: dbo_Prescription, Column: PatientId, Value: 10001; Table: dbo_Prescription, Column: Date, Value: 2/9/2000. Errors in the OLAP storage engine: The record was skipped because the attribute key was not found. Attribute: PatientId - Date of Dimension: Return Visit from Database: AnalysisServices, Cube: MSCPROJECTDVS, Measure Group: Prescription, Partition: Prescription, Record: 1. Errors in the OLAP storage engine: The process operation ended because the number of errors encountered during processing reached the defined limit of allowable errors for the operation. Errors in the OLAP storage engine: An error occurred while processing the 'Prescription' partition of the 'Prescription' measure group for the 'MSCPROJECTDVS' cube from the AnalysisServices database.
Processing Measure Group 'Patient Diagnosis' completed successfully.
Start time: 6/15/2006 12:31:24 PM; End time: 6/15/2006 12:31:25 PM; Duration: 0:00:01
Processing Partition 'Patient Diagnosis' completed successfully.
Start time: 6/15/2006 12:31:25 PM; End time: 6/15/2006 12:31:25 PM; Duration: 0:00:00
SQL queries 1
SELECT [dbo_PatientDiagnosis].[dbo_PatientDiagnosis0_0] AS [dbo_PatientDiagnosis0_0],[dbo_PatientDiagnosis].[dbo_PatientDiagnosisDiagnosisCode0_1] AS [dbo_PatientDiagnosisDiagnosisCode0_1],[dbo_PatientDiagnosis].[dbo_PatientDiagnosisPatientId0_2] AS [dbo_PatientDiagnosisPatientId0_2],[dbo_Diagnosis_3].[MedicineCode] AS [dbo_DiagnosisMedicineCode2_0]
FROM
(

SELECT 1 AS [dbo_PatientDiagnosis0_0],[DiagnosisCode] AS [dbo_PatientDiagnosisDiagnosisCode0_1],[PatientId] AS [dbo_PatientDiagnosisPatientId0_2]
FROM [dbo].[PatientDiagnosis]
)
AS [dbo_PatientDiagnosis],[dbo].[Diagnosis] AS [dbo_Diagnosis_3]
WHERE
(

(
[dbo_PatientDiagnosis].[dbo_PatientDiagnosisDiagnosisCode0_1] = [dbo_Diagnosis_3].[DiagnosisCode]
)
)
Errors and Warnings from Response
Errors in the OLAP storage engine: The process operation ended because the number of errors encountered during processing reached the defined limit of allowable errors for the operation.
Errors in the OLAP storage engine: An error occurred while processing the 'Prescription' partition of the 'Prescription' measure group for the 'MSCPROJECTDVS' cube from the AnalysisServices database.
Errors in the OLAP storage engine: The process operation ended because the number of errors encountered during processing reached the defined limit of allowable errors for the operation.
Errors in the OLAP storage engine: The attribute key cannot be found: Table: dbo_Prescription, Column: PatientId, Value: 10001; Table: dbo_Prescription, Column: Date, Value: 2/9/2000.
Errors in the OLAP storage engine: The record was skipped because the attribute key was not found. Attribute: PatientId - Date of Dimension: Return Visit from Database: AnalysisServices, Cube: MSCPROJECTDVS, Measure Group: Prescription, Partition: Prescription, Record: 1.

Is there any connected to my attributes in the relational data base tables

|||

I have solved the problem though i am still getting some error.

Now it is the MedicationAllergy Fact Table giving me errors.

SELECT 1 AS [dbo_MedicationAllergy0_0],[MedicineCode] AS [dbo_MedicationAllergyMedicineCode0_1]
FROM [dbo].[MedicationAllergy]
)
AS [dbo_MedicationAllergy]
Error Messages 2
Errors in the OLAP storage engine: The attribute key cannot be found: Table: dbo_MedicationAllergy, Column: MedicineCode, Value: 7. Errors in the OLAP storage engine: The record was skipped because the attribute key was not found. Attribute: Allergy of Dimension: Allergy from Database: AnalysisServices, Cube: MSCPROJECTDVS, Measure Group: Medication Allergy, Partition: Medication Allergy, Record: 6.
Errors in the OLAP storage engine: The attribute key cannot be found: Table: dbo_MedicationAllergy, Column: MedicineCode, Value: 7. Errors in the OLAP storage engine: The record was skipped because the attribute key was not found. Attribute: Allergy of Dimension: Allergy from Database: AnalysisServices, Cube: MSCPROJECTDVS, Measure Group: Medication Allergy, Partition: Medication Allergy, Record: 6. Errors in the OLAP storage engine: The process operation ended because the number of errors encountered during processing reached the defined limit of allowable errors for the operation. Errors in the OLAP storage engine: An error occurred while processing the 'Medication Allergy' partition of the 'Medication Allergy' measure group for the 'MSCPROJECTDVS' cube from the AnalysisServices database.
Processing Measure Group 'Patient Diagnosis' completed successfully.
Start time: 6/15/2006 12:51:08 PM; End time: 6/15/2006 12:51:18 PM; Duration: 0:00:10
Processing Partition 'Patient Diagnosis' completed successfully.
Start time: 6/15/2006 12:51:08 PM; End time: 6/15/2006 12:51:18 PM; Duration: 0:00:10
Errors and Warnings from Response
Errors in the OLAP storage engine: The process operation ended because the number of errors encountered during processing reached the defined limit of allowable errors for the operation.
Errors in the OLAP storage engine: An error occurred while processing the 'Medication Allergy' partition of the 'Medication Allergy' measure group for the 'MSCPROJECTDVS' cube from the AnalysisServices database.
Errors in the OLAP storage engine: The process operation ended because the number of errors encountered during processing reached the defined limit of allowable errors for the operation.
Errors in the high-level relational engine. The database operation was cancelled because of an earlier failure.
Errors in the OLAP storage engine: An error occurred while processing the 'Patient Diagnosis' partition of the 'Patient Diagnosis' measure group for the 'MSCPROJECTDVS' cube from the AnalysisServices database.
Errors in the OLAP storage engine: An error occurred while processing the 'Prescription' partition of the 'Prescription' measure group for the 'MSCPROJECTDVS' cube from the AnalysisServices database.
Errors in the OLAP storage engine: The attribute key cannot be found: Table: dbo_MedicationAllergy, Column: MedicineCode, Value: 7.
Errors in the OLAP storage engine: The record was skipped because the attribute key was not found. Attribute: Allergy of Dimension: Allergy from Database: AnalysisServices, Cube: MSCPROJECTDVS, Measure Group: Medication Allergy, Partition: Medication Allergy, Record: 6.

Ronald

|||

In your fact table you have keys that dont appear in the dimension table.

I think in the dbo_MedicationAllergy fact table, MedicineCode column in has more keys than the Allergy dimension.

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

Wednesday, March 21, 2012

errors while running ssis packages from the command prompt.

errors while running ssis packages from the command prompt.

errors while running ssis packages from the command prompt.

Errors while Deploying Analysis services projects in server

Errors when uploading DDL and Data file created by Database Publishing Wizard

Errors using sp_refreshview

Errors using sp_refreshview

Errors using sp_refreshview

Errors using report designer with ssas based report model

Monday, March 19, 2012

Errors processing data from Oracle to SQL

Errors not logged

Errors in the OLAP storage engine:

ERROR: Subreport

Blog Archive

About Me