Showing posts with label preview. Show all posts
Showing posts with label preview. Show all posts

Tuesday, March 20, 2012

"too many fields defined" error when previewing xls

Anyone know why I am getting this?

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

There was an error displaying the preview. (Microsoft Visual Studio)

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

Too many fields defined. (Microsoft JET Database Engine)

Program Location:

at Microsoft.SqlServer.Dts.Tasks.ExecuteSQLTask.Connections.SQLTaskConnectionOleDbClass.ExecuteStatement(Int32 resultType, Boolean isStoredProc, UInt32 dwTimeOut)
at Microsoft.DataTransformationServices.Design.PipelineUtils.ShowDataPreview(String sqlStatement, ConnectionManager connectionManager, Control parentWindow, IServiceProvider serviceProvider, IDTSExternalMetadataColumnCollection90 externalColumns)
at Microsoft.DataTransformationServices.DataFlowUI.DataFlowConnectionPage.previewButton_Click(Object sender, EventArgs e)



A wild stab in the dark: You have to many fields? How many do you have? A clue would help determine if it is a problem of indeed a limitation..|||31 columns on the sheet that I am importing from.|||Obviously 31 is not to many. You have 31 columns with data in. Do you perhaps have any columns with a space or some other text in it right at the end of the document. Like at column ZZ?

I can create a sheet with 32 columns in it and it is fine. Adding spaces to columns after that causes the same error.

I suggest copying the columns you want out, pasting them in a new sheet and try that.|||the sheet has autofilter set on, could that be the cause?|||I don't know. Remove it and see.

Sunday, March 11, 2012

"One or more DataSources is missing credentials"

Get this when selecting parameter value in Report Manager

Report is working fine in preview

Up to me, it has nothing to do with credentials

I have some analysis server reports.

I have a single value report parameter, the report runs fine with the default value, when I select another value than the default one, I get above message immediately.

I got the error since I rebuild the report with SP2 CTP.

Strange thing is that the other single value parameter of the report works fine (year)

And that I get the error also with other reports, and on the same dimension (Organisation)

And that I do not have the error when I change the parameter to multi-value (but as the report is not written for multiple values...)

MDX queries are as follows:

SELECT NON EMPTY { KPIValue("KPINewBiz"), KPIGoal("KPINewBiz"), KPIStatus("KPINewBiz"), KPITrend("KPINewBiz") } ON COLUMNS,

NONEMPTY

([Reps].[Organisation].[Organisation].ALLMEMBERS

*[Reps].[Rep].[Rep].ALLMEMBERS

*[Date].[Year].[Year].ALLMEMBERS

*[Date].[Month].[Month].ALLMEMBERS

,[Measures].[Gross Sales]

)

DIMENSION PROPERTIES MEMBER_CAPTION, MEMBER_UNIQUE_NAME ON ROWS

FROM ( SELECT ( STRTOSET(@.ByYear, CONSTRAINED) ) ON COLUMNS FROM ( SELECT ( STRTOSET(@.ByOrganisation, CONSTRAINED) ) ON COLUMNS FROM [Sales])) CELL PROPERTIES VALUE, BACK_COLOR, FORE_COLOR, FORMATTED_VALUE, FORMAT_STRING, FONT_NAME, FONT_SIZE, FONT_FLAGS

WITH MEMBER [Measures].[ParameterCaption] AS '[Reps].[Organisation].CURRENTMEMBER.MEMBER_CAPTION' MEMBER [Measures].[ParameterValue] AS '[Reps].[Organisation].CURRENTMEMBER.UNIQUENAME' MEMBER [Measures].[ParameterLevel] AS '[Reps].[Organisation].CURRENTMEMBER.LEVEL.ORDINAL' SELECT {[Measures].[ParameterCaption], [Measures].[ParameterValue], [Measures].[ParameterLevel]} ON COLUMNS ,

NONEMPTY([Reps].[Organisation].[Organisation].ALLMEMBERS,[Measures].[Gross Sales]) ON ROWS FROM [Sales]

WITH MEMBER [Measures].[ParameterCaption] AS '[Date].[Year].CURRENTMEMBER.MEMBER_CAPTION' MEMBER [Measures].[ParameterValue] AS '[Date].[Year].CURRENTMEMBER.UNIQUENAME' MEMBER [Measures].[ParameterLevel] AS '[Date].[Year].CURRENTMEMBER.LEVEL.ORDINAL' SELECT {[Measures].[ParameterCaption], [Measures].[ParameterValue], [Measures].[ParameterLevel]} ON COLUMNS , NONEMPTY([Date].[Year].[Year].ALLMEMBERS,[Measures].[Gross Sales]) ON ROWS FROM [Sales]

Discovered something else that is very strange, you change the value of the parameter, you get the error, you hit the back button, and you can run the report with the new parameter

Did one more test, changed the order of the parameters, is now going wrong on the other parameter, Year.

So, it is always on the first parameter.

Correction, I have put a multi-value parameter as first, I still have the problem, it is always on the first single value parameter


I have the same problem.

Up to me, it has nothing to do with credentials

I have some analysis server reports.

I have a single value report parameter, the report runs fine with the default value, when I select another value than the default one, I get above message immediately.

I got the error since I rebuild the report with SP2 CTP.

Strange thing is that the other single value parameter of the report works fine (year)

And that I get the error also with other reports, and on the same dimension (Organisation)

And that I do not have the error when I change the parameter to multi-value (but as the report is not written for multiple values...)

MDX queries are as follows:

SELECT NON EMPTY { KPIValue("KPINewBiz"), KPIGoal("KPINewBiz"), KPIStatus("KPINewBiz"), KPITrend("KPINewBiz") } ON COLUMNS,

NONEMPTY

([Reps].[Organisation].[Organisation].ALLMEMBERS

*[Reps].[Rep].[Rep].ALLMEMBERS

*[Date].[Year].[Year].ALLMEMBERS

*[Date].[Month].[Month].ALLMEMBERS

,[Measures].[Gross Sales]

)

DIMENSION PROPERTIES MEMBER_CAPTION, MEMBER_UNIQUE_NAME ON ROWS

FROM ( SELECT ( STRTOSET(@.ByYear, CONSTRAINED) ) ON COLUMNS FROM ( SELECT ( STRTOSET(@.ByOrganisation, CONSTRAINED) ) ON COLUMNS FROM [Sales])) CELL PROPERTIES VALUE, BACK_COLOR, FORE_COLOR, FORMATTED_VALUE, FORMAT_STRING, FONT_NAME, FONT_SIZE, FONT_FLAGS

WITH MEMBER [Measures].[ParameterCaption] AS '[Reps].[Organisation].CURRENTMEMBER.MEMBER_CAPTION' MEMBER [Measures].[ParameterValue] AS '[Reps].[Organisation].CURRENTMEMBER.UNIQUENAME' MEMBER [Measures].[ParameterLevel] AS '[Reps].[Organisation].CURRENTMEMBER.LEVEL.ORDINAL' SELECT {[Measures].[ParameterCaption], [Measures].[ParameterValue], [Measures].[ParameterLevel]} ON COLUMNS ,

NONEMPTY([Reps].[Organisation].[Organisation].ALLMEMBERS,[Measures].[Gross Sales]) ON ROWS FROM [Sales]

WITH MEMBER [Measures].[ParameterCaption] AS '[Date].[Year].CURRENTMEMBER.MEMBER_CAPTION' MEMBER [Measures].[ParameterValue] AS '[Date].[Year].CURRENTMEMBER.UNIQUENAME' MEMBER [Measures].[ParameterLevel] AS '[Date].[Year].CURRENTMEMBER.LEVEL.ORDINAL' SELECT {[Measures].[ParameterCaption], [Measures].[ParameterValue], [Measures].[ParameterLevel]} ON COLUMNS , NONEMPTY([Date].[Year].[Year].ALLMEMBERS,[Measures].[Gross Sales]) ON ROWS FROM [Sales]

Discovered something else that is very strange, you change the value of the parameter, you get the error, you hit the back button, and you can run the report with the new parameter


Microsoft released a December update to the CTP yesterday. The update fixes the problem.

http://www.microsoft.com/downloads/details.aspx?FamilyId=D2DA6579-D49C-4B25-8F8A-79D14145500D&displaylang=en

|||thanks

Friday, February 24, 2012

"An error occurred during local report processing" for Preview

My report worked fine for a while, but suddenly I started getting the following errors for Preview:

An error occurred during local report processing.

An error has occurred during report processing.

Index was outside the bounds of the array.

I restarted VS, then rebooted my machine and the problem persists.Everything including the report posted to the server works fine. It is just the Preview of this report does not work any more.Preview of other reports work fine.

Any tip to resolve this problem would be greatly appreciated.

Is this the same error that is found in the log?|||

Simone, sorry for my ignorance. Could you tell me which log you referred to?

|||

I renamed the report's *.rdl.data to *.rdl.data.old following a tip from another thread (http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=284496&SiteID=1) and the problem was solved.

I do not fully understand this. It seems the problem was caused by a VS bug.