Do not use on any
shared computer
September 4, 2008 09:42pm pdt
 
[x]
Attachment Details

Stored Procedure runs in Management Studio but not IDE.

Tags: Microsoft, SQL, 2005, Reporting Services
I am running a stored procedure to get data from a MAS90 database via a Linked Server.  The stored procedure returns the proper data in Management studio but in the IDE it returns the error "Can not initialize the data source object of OLE DB Provider "MSDASQL" for linked server MAS90OIL.
Start your free trial to view this solution
[x]
The Solution Rating System

With so many solutions, how can you tell which solutions are most likely to help you and which ones are not? To provide you with a tool to use, we rate our solutions based on various elements that most accurately determine if a solution is a quality solution. To explain what factors affect the solution rating, here are the elements we take into consideration when formulating our solution rating.

  • The Grade of the Solution
  • The Zone Rank of the Expert Providing the Solution
  • The Number of Author and Expert Comments
  • The Number of Experts Contributing
  • The Feedback of the Community

Your Input Matters
Because of the way the system is set up, the most important variable in this equation is you. As a member of Experts Exchange, you are able to cast your vote on the quality of the solutions in regard to how complete, accurate, helpful and easy to understand each solution is. When you provide your feedback, each rating is adjusted accordingly. So, if you see a solution that has a poor rating that you think is a good solution, let us know by rating it. As you do, the rating will be adjusted and will become more accurate for other members of our site.

If you have any suggestions that you would like to make for our rating system, please ask a question in the Suggestions Zone of Community Support.

Thank you!

Question Stats
Zone: Software
Question Asked By: johnston01
Solution Provided By: angelIII
Participating Experts: 2
Solution Grade: A
Views: 0
Translate:
Loading Advertisement...
 
[+][-]Expert Comment by angelIII

Rank: Genius

Expert Comment by angelIII:

All comments and solutions are available to Premium Service Members only.

Start your 7-day free trial and see for yourself why Experts Exchange is the easiest and most proven technology resource in the world. Get Started

Already a member? Login to view this solution.

 
 
[+][-]Expert Comment by zephyr_hex
Expert Comment by zephyr_hex:

All comments and solutions are available to Premium Service Members only.

Start your 7-day free trial and see for yourself why Experts Exchange is the easiest and most proven technology resource in the world. Get Started

Already a member? Login to view this solution.

 
 
[+][-]Author Comment by johnston01
Author Comment by johnston01:

All comments and solutions are available to Premium Service Members only.

Start your 7-day free trial and see for yourself why Experts Exchange is the easiest and most proven technology resource in the world. Get Started

Already a member? Login to view this solution.

 
 
[+][-]Accepted Solution by angelIII

Rank: Genius

Accepted Solution by angelIII:

All comments and solutions are available to Premium Service Members only.

Start your 7-day free trial and see for yourself why Experts Exchange is the easiest and most proven technology resource in the world. Get Started

Already a member? Login to view this solution.

 
 
Loading Advertisement...
Open Discussion
Open Discussion
 
Comment by johnston01
Any reason why this would not work on a SQL 2000 server.  I have it running on a 2005 server with out error but fails on SQL 2000.
 
 
Comment by angelIII
> Any reason why this would not work on a SQL 2000 server.  
no. the SET NOCOUNT ON shall work on both versions equally.

is it the same error you described initially?
 
 
Comment by johnston01
No, the error is different.  This is the error the SQL 2000 server had before and after the Set nocount on.


An error has occurred during report processing. (rsProcessingAborted) Get Online Help
Query execution failed for data set 'DataSet1'. (rsErrorExecutingCommand) Get Online Help
SqlDumpExceptionHandler: Process 60 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOLATION. SQL Server is terminating this process. OLE DB provider 'MSDASQL' reported an error. The provider reported an unexpected catastrophic failure. OLE DB error trace [OLE/DB Provider 'MSDASQL' IDBInitialize::Initialize returned 0x8000ffff: The provider reported an unexpected catastrophic failure.].
 
 
Comment by angelIII
>EXCEPTION_ACCESS_VIOLATION
not good.
only service packs might help, or changes like avoiding the SELECT * in the openquery (ie to avoid any implicit data type conversion... )
 
 
Comment by johnston01
Why would this happen in 2000 and not in 2005?
 
 
Comment by angelIII
the underlying answer to that question shall be directly to MS, I guess :)
anyhow, I guess because sql 2000 was not expected to get some "results" in certain cases...
 
 
20080723-EE-VQP-34 / EE_QW_2_20070628