The following system error occurred: .

This appears regularly on reports. It does not seem to be connected to
whether the report returns a lot of data or not, or with any particular
report. If I refresh then the report usually runs fine. What can be
causing this? Where do I look to find more information about the error than
just a period?

The reports run fine most of the time so I cannot see it being an issue with
the port, and it also occurs in development as well as production so I can
only put it down to the ds driver (MSOLAP.3), the connection is
Provider=MSOLAP.3;Data Source=its-my-sqlserver;Initial
Catalog=AS_DATABASE;Connect Timeout=0

I have looked through
http://www.sqljunkies.com/WebLog/edw.../26/21447.aspx a
number of times but these do not help so please don't ask me to look through
this document.

What is wrong??

Please help.

Hi Nick,
This is a quick note to let you know that I am performing research on this
post and will respond to you as soon as possible. I appreciate your
patience.

Best regards,
Charles Wang
Microsoft Online Community Support
================================================== =======
Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msdnmg (AT) microsoft (DOT) com.
================================================== =======
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== =======

Hi Nick,

I have checked the links that you provided and find it provides us some
guide for troubleshooting connecting issue. However I didn't find any
detailed system error in your post. Could you please provide us the
detailed error information?

Best Regards,
Robbie Meng
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscripti...ult.aspx#notif
ications
<http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx>.
Note: The MSDN Managed Newsgroup support offering is for non-urgent issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach the
most efficient resolution. The offering is not appropriate for situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are best
handled working with a dedicated Microsoft Support Engineer by contacting
Microsoft Customer Support Services (CSS) at
<http://msdn.microsoft.com/subscriptions/support/default.aspx>.
==================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

Robbie, The error I get is:
a.. An error has occurred during report processing.
a.. Cannot create a connection to data source 'dsMyDS'.
a.. The following system error occurred: .
The connection specified in the error is the OLAP connection described in
the original post.

This is intermittent and usually resolves when the user refreshes the page
(F5). The error occurs on SSIS reports that have links to OLAP (SSAS 2005)
cubes.

Regards,

"Robbie Meng" <v-gameng (AT) online (DOT) microsoft.com> wrote

Robbie,

I managed to get a look at the reportserver log. I can see which entries
the error occured on and I think I might be close to the answer, but I will
need your help.

I logged into the sql server where reporting services is and ran the
following query on the ReportServer database:

select *

from executionlog

where UserName = '<my user name>'

order by timeend desc

This gave me a list of the information passed to RS. The bytecount is 0 and
rowcount is 0, the Status reads "rsProcessingAborted", the
timeprocessing=2293, timedataretrieval and timerendering is 0. The
parameters are the same as the parameters on the next item (when I refreshed
the report and it ran correctly).

So the log tells me that the instance failed with error
"rsProcessingAborted", I assume that means that something aborted the
process. How can I find out what aborted it, or if there are any other log
items that might help resolve the issue?

Regards,


"Nick Large" <nlarge (AT) newsgroups (DOT) nospam> wrote

Hello Nick,

Did you try to use SQL profiler to trace the "audit logon" event to see if
there is any difference between 1st and 2nd try to connect?

To isolate the issue of MSOLAP.3, you may want to try to change it MSOLAP.2
to see if there is any difference.


Via Report Manager (http://localhost/Reports) view the properties of the
Data Source and change the above connection string to the following

Provider=MSOLAP.2;Client Cache Size=25;Data Source=servername;Auto Synch
Period=20000;Initial Catalog=dbname

Also, to make sure it's not related to servername or port, please try the
IP address and "servername,<port number>" (without quote) for server name
to see if makes any difference. You could check the port number of the SSAS
by using

netstat -nba

and check the msmdsrv.exe process for the port.

If you have any update, please feel free to let's know.

Best Regards,

Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Partner Support


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

newsreader so that others may learn and benefit from this issue.
================================================== ====
This posting is provided "AS IS" with no warranties, and confers no rights.

Peter,

Just out of interest, the same error occurs in Visual Studio report designer
intermittently it states

A Connection cannot be made to the database.
Set and test the connection string.

Additional Information:
for Analysis Services 2005)

I did change the value to MSOLAP.2 and got a different error:

A Connection cannot be made to the database.
Set and test the connection string.

Additional Information:
started or too busy. (Microsoft OLE DB Provider for Analysis Services)

Actually, I would expect this behaviour because MSOLAP.2 is for 2000 OLAP,
not 2005, right?

OK, so I tried adding the port number to the connection string as Data
Source=myserverort eg. "yahoo:2399", and I don't seem to be getting any
issues, no issues in report designer or when running the reports. I will
say that I did need to specify the port address in the properties for the
server in SSMS as the default is 0 (dynamic) so that it is always the value
specified and SSRS connection to the cube will always look on that port. I
will repost if there are any further issues with this.

""Peter Yang"" <petery (AT) online (DOT) microsoft.com> wrote

Hi Nick,
How are things going?
I was on a vacation last week. My colleague Robbie and Peter helped assist
you on this post. Now I am back to office and will provide further
assistance for you.

Regarding this issue, it looked that you worked around it by specifying the
TCP port number after the data source name. That is a great news and I am
glad to hear that. Going after your current workaround, I would like to add
more comments. Did you check if SQL Server Browser service was started on
your server? Analysis Services records the port number and the instance
name with SQL Server Browser, which is the service that handles lookup of
named instances. If your SQL Server Browser service was not started, your
Analysis Services instance may not be correctly identified by your clients.

You can check the status of SQL Server Browser from SQL Server
Configuration Manager->SQL Server 2005 Services. If it is not started,
please manually start it.

Thank you for choosing Microsoft. Please do not hesitate to let me know if
you have any other questions or concerns.

Best regards,
Charles Wang
Microsoft Online Community Support
================================================== =======
Delighting our customers is our #1 priority. We welcome your
comments and suggestions about how we can improve the
support we provide to you. Please feel free to let my manager
know what you think of the level of service provided. You can
send feedback directly to my manager at: msdnmg (AT) microsoft (DOT) com.
================================================== =======
This posting is provided "AS IS" with no warranties, and confers no rights.
================================================== =======

Thanks Charles.

It seemed to work splendidly for a while and then I started getting the
message again. I did see that the browser service was disabled. I assume
that this is by default on installation of SQL 2005, but would not
understand why that would be wise, could it be a security risk having it on,
or just that it is not necessary in most cases to have it switched on?
Anyway, I will post back if I see the message again.

Thanks,
Nick.


""Charles Wang [MSFT]"" <changliw (AT) online (DOT) microsoft.com> wrote

Oh, and the other thing, I did see that when the error occurs that the
system logs in as NT Authority\ANONYMOUS whereas when I refresh it, it
appears as the correctly assigned user on the connection string and the
report is generated. Could this possibly be an OLEDB issue (ie. the OLEDB
is not parsing the connection correctly in some instances), or reporting
services issue (Ie. RS is not finding the correct connection?) ??
Nick.

"Nick Large" <nlarge (AT) newsgroups (DOT) nospam> wrote