Error processing Cube - The syntax for ',' is incorrect.

Hi guys! Could you help me with the next problem:

Failed to build the OLAP cubes. Error: Analysis Services session failed with the following error: Query (1, 10) Parser: The syntax for ',' is incorrect.

I have installed sql2005 sp2, but didn't get much

Pls. help

If you have a new issue, please create a new thread rather than just replying to an old one. You are more likely to get an answer.

It sounds like there might possibly be an extra comma in your MDX script. It looks like it is at character 10 on the first line (that's what the 1,10 means)

Error on VB Sample which is delivered by installation.

Hi,

after i try to build the web application "Web Development - Data Entry Form" i get the following error message. I already change the variable username to system which is defined in Machine.Config.

The Error messega is like following:
SQL Server does not exist or access denied.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.Data.SqlClient.SqlException: SQL Server does not exist or access denied.

Thanks,The username you see in machine.config is most likely not the username you want to provide in the connection string in your application. You need to provide a valid username and password for your SQL server. If you did not install the db server yourself, you should be able to get valid login info from the person who installed it.

If the db server is local, you might be able to get away with the following for your connection string: "server=localhost;TrustedConnection=true;database=YOUR_DB"

Error message (event id 107)

I have installed Reporting services Enterprise Edition without any problems.
I have also been able to build and deploy a report.
But the Reporting Service logs the following error to the Application log:
"Schedule and Delivery Processor cannot connect to the report server
database" (Event id: 107 ).
There are no errors in the Reporting Services log files .
Can anyone tell me how to fix this error?
Regards,
MarileneI have a similar problem, we have Reporting services deployed & working
across a web cluster. Very intermittently Iâ'm getting the following error in
the application log twice in succession as the reports fail:
"Schedule and Delivery Processor cannot connect to the report server
database" (Event id: 107).
When the report is called a second time I get the following:
"The Report Server service has been activated." (Event id: 124)
So the question is why does the logon\connection to the report server
database fail at the first attempt?
Regards,
Graham
"ms" wrote:
> I have installed Reporting services Enterprise Edition without any problems.
> I have also been able to build and deploy a report.
> But the Reporting Service logs the following error to the Application log:
> "Schedule and Delivery Processor cannot connect to the report server
> database" (Event id: 107 ).
> There are no errors in the Reporting Services log files .
> Can anyone tell me how to fix this error?
> Regards,
> Marilene
>
>

Error Message "Key Sequence columns are not supported at the case level"

Hi group,
I was trying to build a sequence clustering model in MSAS.
I could deploy the model. Then while building the model, I end up getting an error with message "Key Sequence columns are not supported at the case level".

Can some one tell me what it means and how i can avoid it?

Thanks in advance to any kind of help here.
The Microsoft_Sequence_Clustering algorithm requires the sequence
information to be modeled as a nested table so you can only have a nested table column with Content=Key Sequence (right-click on the column in the Mining Structure tab and look at the Properties pane).

In the above case, you will have a case level key that uniquely identifies a sequence set (modelled as multiple nested table rows) and you'll need to mark that with Content=Key and IsKey=True.|||Thanks for your suggestion Raman.
I have made the change that you have suggested and proceeded to the processing step.

Hmm, the processing fails with error msg:
"OLE DB or ODBC error: A column has been specified more than once in the order by list. Columns in the order by list must be unique.; 42000."

The "Key sequence" column in the nested table has been used twice in a query. Query attached in the end for reference.
What could be the cause for this? / How do i make AnSer stop generating this wrong query?
(How do you like my new short name to MSAS? AnSer. Sounds like 'answer') :)

FYI.. the "Key Sequence" column in the nested table has a FK relationship with the "Key" column of the case table.

The processing fails because it runs the query:
SELECT
[nestedTable].[col1]
,[nestedTable].[col2]
,[nestedTable].[col3]
FROM [nestedTable]
ORDER BY [nestedTable].[col1]
,[nestedTable].[col1]
--col1 is a sequence key and has FK relation with the case table.|||The "Key Sequence" is the key of the nested table, while the foreign key
should be the column you used to join case table
and nested table. These 2 columns should be 2 seperate columns in the nested
table. The following is an example:

SeqClustCase -- Case table
UserId (Key)
A1
A2

SeqClustNested -- Nested table
UserId (foreign key)
Order(Key sequence)
Sequence (sequence data)

Please try fix your data source view and mining structure according to the
above example.

Thanks,|||

Actually the foreign key column is implicitly included as part of the bindings for the nested table when you use BI Dev Studio and you don't need to specify it as a column in the nested table.

Can you please post your mining structure and model definitions?