Error in deploying cube

Hi,

I'm getting an internal exception error while deploying the solution. The error is as follows -

"Error - 1056964586: Internal error: An unexpected exception occured."

When deployed for the first time, it went through and subsequent changes processed as well. For a specific reason I had to delete the database and redeploy.

From then on I'm getting this error. Earlier threads said try SP2, still the error persists.

Had to share this solution with my teammate as well and even he is getting this error, even though he is deploying it for the first time.

Any help on this would really help, otherwise I would have to recreate the entire solution, changes etc.

Thanks in advance.

Hi,

I do not know this sepcific error message or number.

But I now - you cannot deploy the cube if you have a role with a user which does not exists. Remove incorrect users from you roles (or try remove all and then deploy again)

I had such issues in most of my deployment scenarios.

Else - does the message come from deployment or processing - try only deploy the solution and do not process.

HANNES

|||

Hi Hannes,

I dont have any user roles defined. Also I'm the administrator of the system and the Analysis Services server as well.

And the error comes when I'm trying to deploy the solution.

|||

"Unexpected Exception" errors usually indicate a bug in the server, and we would require either a crash dump or a copy of the solution in order to diagnose exactly why we're hitting it. I'd recommend opening a support ticket if that option is available to you.

- Brad

|||

I was able to track down the problem in my case.

I had 3 cubes and there was 2 relationships (linked objects), viz. Cube 1 refering Cube 2 and Cube 2 refering Cube 3.

When I removed one of the references, the deployment and processing went through.

I guess this is a limitation not to have such kind of references.

-

Vivek C.

Error importing excel file

When ever importing a excel file or flat file, I get an Unhandled exception error and the event log reads a .Netframework error ID 1000.

Checking the database I was importing into, I find that the table was created with the columns, but no data within the columns.

The import wizards report 509 row copyed before crashing with the Handle error, where a dialog box appears allowing debug or close.

Can anyone help?

I include the logged errors.

Event Log

.NET Runtime 2.0 Error
Event ID: 1000

Faulting application dtswizard.exe, version 9.0.1399.0, stamp 434f5e2a, faulting module dtspipeline.dll, version 2005.90.1399.0, stamp 434f5dbc, debug? 0, fault address 0x0004ba38.

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

0000: 41 00 70 00 70 00 6c 00 A.p.p.l.
0008: 69 00 63 00 61 00 74 00 i.c.a.t.
0010: 69 00 6f 00 6e 00 20 00 i.o.n. .
0018: 46 00 61 00 69 00 6c 00 F.a.i.l.
0020: 75 00 72 00 65 00 20 00 u.r.e. .
0028: 20 00 64 00 74 00 73 00 .d.t.s.
0030: 77 00 69 00 7a 00 61 00 w.i.z.a.
0038: 72 00 64 00 2e 00 65 00 r.d...e.
0040: 78 00 65 00 20 00 39 00 x.e. .9.
0048: 2e 00 30 00 2e 00 31 00 ..0...1.
0050: 33 00 39 00 39 00 2e 00 3.9.9...
0058: 30 00 20 00 34 00 33 00 0. .4.3.
0060: 34 00 66 00 35 00 65 00 4.f.5.e.
0068: 32 00 61 00 20 00 69 00 2.a. .i.
0070: 6e 00 20 00 64 00 74 00 n. .d.t.
0078: 73 00 70 00 69 00 70 00 s.p.i.p.
0080: 65 00 6c 00 69 00 6e 00 e.l.i.n.
0088: 65 00 2e 00 64 00 6c 00 e...d.l.
0090: 6c 00 20 00 32 00 30 00 l. .2.0.
0098: 30 00 35 00 2e 00 39 00 0.5...9.
00a0: 30 00 2e 00 31 00 33 00 0...1.3.
00a8: 39 00 39 00 2e 00 30 00 9.9...0.
00b0: 20 00 34 00 33 00 34 00 .4.3.4.
00b8: 66 00 35 00 64 00 62 00 f.5.d.b.
00c0: 63 00 20 00 66 00 44 00 c. .f.D.
00c8: 65 00 62 00 75 00 67 00 e.b.u.g.
00d0: 20 00 30 00 20 00 61 00 .0. .a.
00d8: 74 00 20 00 6f 00 66 00 t. .o.f.
00e0: 66 00 73 00 65 00 74 00 f.s.e.t.
00e8: 20 00 30 00 30 00 30 00 .0.0.0.
00f0: 34 00 62 00 61 00 33 00 4.b.a.3.
00f8: 38 00 0d 00 0a 00 8.....

Debug Log

Unhandled exception at 0x2357ba38 in DTSWizard.exe: 0xC000001D: Illegal Instruction.

Would you be able to help us nail down this problem by identifying what data is exactly causing this crash?

You can do this by reducing the data set in your spreadsheet (i.e. take 10 rows around the row #509 and see if the problem reproes, than try to find the exact row, then the exact column if possible) and figuring out what is the data and data type of the cell that could not be handled.

In the case you can give us the entire spreadsheet or the minimal piece that still reproes the problem; we could start our investigation from there.

Thanks.

|||

Hi

I have cut down the excel file, still no luck. I have even created a new excel file with two columns and two rows and I still get the error. I have noticed the test file I created "test.xls" is imported with a $ "test$" .

test.xls

Temp Contract 1 231 2 234

This should be simple to import.

John

|||

Well, this is quite simple data and it should not cause any problem. It worked for me quite easy.

Could it be possible that you have some problems with your installation/binaries? What edition of SQL Server do you have installed? Have you installed some previous versions on the same machine?

|||

Bob,

Here are the version information:

Microsoft SQL Server Management Studio 9.00.1399.00
Microsoft Analysis Services Client Tools 2005.090.1399.00
Microsoft Data Access Components (MDAC) 2000.086.1830.00 (srv03_sp1_rtm.050324-1447)
Microsoft MSXML 2.6 3.0 6.0
Microsoft Internet Explorer 6.0.3790.1830
Microsoft .NET Framework 2.0.50727.42
Operating System 5.2.3790

There was no prevoius installations of SQL, However after installing SQL2005 I installed the MSDN disk that came with it, I believe there was an error, I uninstalled and re-install MSDN without any errors "Installation Successful".

John

Error Handling problem

I have a strange behavior when executing a CLR SP:

The SP contains the following test code:

try {
int.Parse("");
}
catch (Exception ex) {
try {
command.CommandText = "raiserror (100003, 16, 1, 'parse error') with seterror";
pipe.ExecuteAndSend(command);
}
catch {
return;
}
}

Here the SQL I use to test it

decare @.e int
begin try
exec MySP
set @.e = @.@.error
print @.e
print 'phew!'
end try
begin catch
print error_message()
end catch
print 'done'

What I expect is that, since MySP throws an error, the catch block is executed and the error message is printed out.

What happens is that
@.@.error contains the correct error code 100003
the catch block does not executes
Here the output of SSMS:

Msg 100003, Level 16, State 1, Line 1
"invalid operation: parse error"
100003
phew!
done

Any Idea of why @.@.error is set but the catch block does not executes ?

just a final note: if do not use the try/catch block in the SP and let the exception be caught into the server engine, the catch block on the T-SQL is correctly executed (and it is my current solution, sigh !!!)Hi,

see this connect bug here: https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=251376

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de|||Thanks from providing the link.
I'm skeptical they will fix it less time than a couple of years.