How To Get Hold Of Data From Web Provider Using SQL Server?

Feb 16, 2006

I am new to SQL server so apologies if this is a stupid question.



I have a website built and hosted by another company, with SQL server
back end data. They don't want to analyse the data but I do. I am
familiar with SQL and have SQL server express running on my laptop.



So I was thinking I could get them to send me the data from the server
(it will be less than 1GB I imagine), and I could analyse it myself.



So my questions are:

will this work?

and what do I ask them to send me? Is it just a couple of files they
have to copy and send me? Or is it more complicated than that?



Many thanks for any advice you can offer.



James

View 1 Replies


ADVERTISEMENT

Many Data Entry Tables - Which Ones Hold Records?

Oct 23, 2005

We have an asp.net app with about 200 data entry forms. Customers mayenter data into any number of forms. Each form's data is persisted ina corresponding sql table. When data entry is complete, it needs to beprocessed. Here's where the questions start.How can we easily determine in which tables a customer has data and howbest to select that data?We're not opposed to putting all the data in a single table. Thistable would wind up having ~15 million records and constantly have CRUDoperations performed against it by up to 5000 users simultaneously.With sufficient hardware, is this too much to ask of the db?

View 10 Replies View Related

Handling Provider-level Errors From .Net SqlClient Data Provider

Jun 26, 2007



Hi,



After reading this helpful blog entry:



http://blogs.msdn.com/sql_protocols/archive/2007/05/13/sql-network-interfaces-error-26-error-locating-server-instance-specified.aspx



I think this might be a good place to ask the following question.



I am writing the error handling code for my data access layer for a web application. I am using the Enterprise Library Data Access Application Block. Although this supports generic database connections, I realized that I need to handle errors specific to each database type. Microsoft SQL is the only database type I am using for now, so I am using a try...catch (SqlException e).



In testing my code, I intentionally changed the instance name in web.config to a name that does not exist. I get the very popular error 26 - Error Locating Server/Instance Specified. This is returned as a SqlException, but the SqlError.Number property is set to -1.

Am I getting "-1" because the provider hasn't actually connected to SQL yet, so it doesn't have an actual SQL error number?
Can I assume that (SqlError.Number == -1) is always a fatal, provider-level connection exception?
Will the provider ever use another SqlError.Number of its own? Or do all numbers besides -1 come from the SQL sysmessages table?.
Is there a comprehensive list of what exceptions might be raised by the SqlClient provider, including #26?

The reason for all the questions is that in a web application, I want to prevent the end-user from seeing the "real" exception if it has to do with configuration errors. However, maybe there are other errors that the user should see and handle? It's hard to know without a full list of SqlClient provider errors, along with the SqlError.Number that each error maps to.



Thanks and regards,



Mark

View 6 Replies View Related

Default Settings SQL Server Does Not Allow Remote Connections. (provider: Named Pipes Provider, Error: 40 - Could Not Open A Connection To SQL Server

Jan 28, 2008

Hi I always get good reply from u all, thank you,
 I have copied my asp.net website from one server to another. they administrator made necessary modification on IIS manager . and able to see the website on browser. but now i can't loging to system using old password.
I tryed to create new password then also it gives error
System.Data.SqlClient.SqlException: An error has occurred while establishing a connection to the server.  When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
Here I have used asp.net login control and membership class. Do I need to make nay changes in code.
I have already modified server name in connection string in web config file.
any one can say what is the problem and how to solve this.
thanks
Pat
 
 

View 1 Replies View Related

This Failure May Be Caused By The Fact That Under The Default Settings SQL Server Does Not Allow Remote Connections. (provider: Named Pipes Provider, Error: 40 - Could Not Open A Connection To SQL Server)

Apr 18, 2008

Hi ,
      I am struck with one issue.Plz help me out if you have any solution for this one.
Details
Front End - Visual Studio 2005
Back End -SQL Server 2000 (Remote database) 
Error i am getting is
{System.Data.SqlClient.SqlException: An error has occurred while establishing a connection to the server.  When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
   at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)   at System.Data.SqlClient.TdsParser.Connect(Boolean& useFailoverPartner, Boolean& failoverDemandDone, String host, String failoverPartner, String protocol, SqlInternalConnectionTds connHandler, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection owningObject, Boolean aliasLookup)   at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)   at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)   at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)   at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options)   at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject)   at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject)   at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)   at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)   at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)   at System.Data.SqlClient.SqlConnection.Open()   at dbcAccess.clsSQL.GetConnect() in C:Documents and SettingskerlsgMy DocumentsVisual Studio 2005ProjectsdbcAccessdbcAccessclsSQL.cs:line 296} 
 
 
 
   
 
{System.Data.SqlClient.SqlException: An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

View 6 Replies View Related

SQL Express - When Connecting To SQL Server 2005, This Failure May Be Caused By The Fact That Under The Default Settings SQL Server Does Not Allow Remote Connections. (provider: Named Pipes Provider, Error: 40 - Could Not Open A Connection To SQL Serve

Apr 10, 2008

Hi,I have SQL Server Express Edition. I tried working out some ASP.NET Labs in my local system. Here is the link of the Virtual Lab which I tried. http://msevents.microsoft.com/CUI/WebCastEventDetails.aspx?EventID=1032286906&EventCategory=3&culture=en-US&CountryCode=USI recieve this error in my local system. An error has occurred while establishing a connection to the server.  When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)I tried working out solutions from various websites. But the no solution is effective. Could anyone help me in solving this issue.  

View 3 Replies View Related

SQL 2005 : Provider: Named Pipes Provider, Error: 40 - Could Not Open A Connection To SQL Server

Mar 17, 2008

Hi to all,


We have 4 client machine and 1 server machine, that server have all the sql server 2005 database€™s.


A project developed from client1 with Asp.net 2005 now I need to access that project from client2 so I type http://My Ip address/Folder Name/home.aspx in my browser here when the sql connection is open(SqlConnection.Opn()) then I meet this problem


An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)


Please reply me.

View 2 Replies View Related

(provider: Named Pipes Provider,error: 40 - Could Not Open A Connection To SQL Server)

Jan 23, 2007

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.
 I am getting this error and using this connection string
Data Source=192.168.0.100;Network Library=DBMSSOCN;Initial Catalog=ENet;User ID=eonline;Password=eonline;
What can be solution for this.

View 4 Replies View Related

Provider: Named Pipes Provider, Error: 40 - Could Not Open A Connection To SQL Server

Mar 10, 2008

Hi,    I am working on VS 2005 and using SQL 2005 Express and i am processing excel files and inserting records in data base as i processing starts and almost after processing 600 i got this error provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server. how can i solve that thanx  

View 3 Replies View Related

SQL Server Does Not Allow Remote Connections. (provider: Named Pipes Provider, Error: 40)

Apr 15, 2008

Hi,
My .NET 2005 application is on a server outsite company's domain. SQL server is in domain and port for sql server is open. TCP/IP is set for remote connection in SQL Server. Connection string in .config is
    <add name="X_Conn" connectionString="Data Source=XXX;Initial Catalog=XXX;User ID=XX; Password=XXX;" providerName="System.Data.SqlClient"/>
I receive the error below:
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
thanks a lot in advance!

View 3 Replies View Related

Provider: Named Pipes Provider, Error: 40 - Could Not Open A Connection To SQL Server

Apr 26, 2007



We just changed the dev environment to sqlagent. From then we were unable to see the reports on the report server because:



An error has occurred during report processing.

Cannot create a connection to data source 'IHRSDataSource'.

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

this error is cropping up.



To Resolve this issue, we checked the Surface Area Configuration and also checked the Reporting Service Configuration . There seem to be no problem and everything looks ok.



Please help me in resolving this issue.











View 4 Replies View Related

Provider: Named Pipe Provider, Error: 40 - Could Not Open Connection To SQL Server

Apr 14, 2007

After I installed the various service packs via Windows Update, my WindowsForms application can no longer connect to the server.



The error message is:



provider: Named Pipe Provider, error: 40 - Could not open connection to SQL server.



However, the Reporting Services work just fine.



Please help.

View 1 Replies View Related

Provider: Named Pipes Provider, Error: 40 - Could Not Open A Connection To SQL Server

Mar 17, 2008

Hi to all,


We have 4 client machine and 1 server machine, that server have all the sql server 2005 database€™s.


A project developed from client1 with Asp.net 2005 now I need to access that project from client2 so I type http://My Ip address/Folder Name/home.aspx in my browser here when the sql connection is open(SqlConnection.Opn()) then I meet this problem


An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)




Please reply me.

View 1 Replies View Related

Provider: Named Pipes Provider, Error: 40 - Could Not Open A Connection To SQL Server

Feb 20, 2006

Hi All,

   I am new to dotnet. I tried connecting to the database MS SQL Server 2000. I gave the code like, the one below, in form load event,

SqlDataReader dr = null;

SqlConnection myConnection = new SqlConnection("Data Source=IP;Initial Catalog=name;User Id=uid;Password=pwd;");

myConnection.Open();

myConnection.Close();

But I could not connect. The error message highlights the line myConnection.Open() and displays the error

An error has occurred while establishing a connection to the server.  When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)


It tries connecting to SQL Server 2005. There is no SQL Server 2005 in that system. There is only SQL Server 2000.

I have the aspx code in my local system and the database in another machine.

Could Someone please help me out in solving this problem.

 

Thanks,

Arun. S

 

 

 

 

 

View 26 Replies View Related

Provider: Named Pipes Provider, Error: 40 - Could Not Open A Connection To SQL Server

May 20, 2008



hi all

I realised this has been done to death, and so much information out there but I am still in a quandry.

I have had to rebuild my computer.

This is what I did

XP machine
using SQL Server 2005 Standard Edition
using Windows Authentication
NZ6(MSSQLSERVER)

straight default install all the way

unfortunately when ready to run reports from my instance(computer)
I received the error as in provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server

thought I had it all okayed but obviously something not right

so ended up unistalling then - did the following:

Load SQL Server from disc1 and start install
failed on alter Counter Registry key error
fixed this from KB article (known error that can happen)
restarted
Went to Windows Update
check IIS is installed - tick is on - IIS - admin tools - make sure asp2 is associated - yes ok
Then back to install sql server - there is no instance set up yet
Disk 2 and setup .exe

All ok on Reporting Services, Analysis etc.


But once again all seems fine but still getting the error:

connection is all fine in Management Studio - eg I can see tables etc
connection is all fine in Business Intelligence - eg I can preview my reports
I then can deploy up to - NZ6
open NZ6
eports
report is there fine - but just errors

some simple little tick that I have not done!!

I seem to have checked and rechecked everything and obviously doing another re-install does not seem a logical step from here.
I will continue to check but if someone jump in and advise please would be great.

cheers
jewel

View 6 Replies View Related

Provider: Named Pipes Provider, Error: 40 - Could Not Open A Connection To SQL Server

Oct 15, 2007



Hi

I am creating a web site using Visual Studio 2008 & trying to connect to database on SQL Server 2000. My test connection is successful but while debugging the page I am getting this error :
" provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server "

Your suggestions on that will be appreciated.

Thanks

Ashok

View 5 Replies View Related

Provider: Named Pipes Provider, Error: 40 - Could Not Open A Connection To SQL Server

Aug 27, 2007

Guys!
has MS done Anything about this issue? I am running NT2K and have the same issue y'all having

provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server

Does anyone have a fix or a workaround that will work once the application goes live?

View 1 Replies View Related

Provider: Named Pipes Provider, Error: 40 - Could Not Open A Connection To SQL Server

Apr 3, 2007

Hi,



Am getting the followning error:



{"An error has occurred while establishing a connection to the server. When

connecting to SQL Server 2005, this failure may be caused by the fact that under

the default settings SQL Server does not allow remote connections. (provider: Named

Pipes Provider, error: 40 - Could not open a connection to SQL Server)"}



from my application where 3 service references had been added

and hav added this segment in app.config file



<configSections>

<section name="dataConfiguration" type="Microsoft.Practices.EnterpriseLibrary.Data.Configuration.DatabaseSettings, Microsoft.Practices.EnterpriseLibrary.Data, Version=2.0.0.0, Culture=neutral, PublicKeyToken=null" />

</configSections>

<dataConfiguration defaultDatabase="Connection String" />

<connectionStrings>

<add name="Connection String" connectionString="Data Source=DPA1W075Binstancename;Initial Catalog=SoapBox;Integrated Security=SSPI;"

providerName="System.Data.SqlClient" />

</connectionStrings>



Solutions recommended for this were start running the SQL browser instance and enable Namespipes in Sqlserver configuration manager.Did both.. but nothing worked.

Still getting the same error..



Can somebody plz help me?

View 2 Replies View Related

Provider: Named Pipes Provider, Error: 40 - Could Not Open A Connection To SQL Server

Jul 21, 2007

Hi guys, I have a problem with error: 40.

I made a Web page, and it works perfect on my local machine, everything is OK, until I uloaded page to the server, it reports this error:


An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

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: An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)

Source Error:





An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:




[SqlException (0x80131904): An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)]
System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) +735091
System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) +188
System.Data.SqlClient.TdsParser.Connect(Boolean& useFailoverPartner, Boolean& failoverDemandDone, String host, String failoverPartner, String protocol, SqlInternalConnectionTds connHandler, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection owningObject, Boolean aliasLookup) +820
System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance) +628
System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance) +170
System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection) +359
System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options) +28
System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject) +424
System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject) +66
System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject) +496
System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) +82
System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) +105
System.Data.SqlClient.SqlConnection.Open() +111
System.Data.Common.DbDataAdapter.FillInternal(DataSet dataset, DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior) +121
System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior) +137
System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, String srcTable) +83
System.Web.UI.WebControls.SqlDataSourceView.ExecuteSelect(DataSourceSelectArguments arguments) +1770
System.Web.UI.WebControls.Repeater.GetData() +50
System.Web.UI.WebControls.Repeater.CreateControlHierarchy(Boolean useDataSource) +232
System.Web.UI.WebControls.Repeater.OnDataBinding(EventArgs e) +53
System.Web.UI.WebControls.Repeater.DataBind() +72
System.Web.UI.WebControls.Repeater.EnsureDataBound() +55
System.Web.UI.WebControls.Repeater.OnPreRender(EventArgs e) +12
System.Web.UI.Control.PreRenderRecursiveInternal() +77
System.Web.UI.Control.PreRenderRecursiveInternal() +161
System.Web.UI.Control.PreRenderRecursiveInternal() +161
System.Web.UI.Control.PreRenderRecursiveInternal() +161
System.Web.UI.Control.PreRenderRecursiveInternal() +161
System.Web.UI.Control.PreRenderRecursiveInternal() +161
System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1360



I dont't Know what to do. Please HELP!

View 6 Replies View Related

(provider: Named Pipes Provider, Error: 40 - Could Not Open A Connection To SQL Server) Urgent Please Help Me| Admin Please Rush It Thanks A Lot

Apr 4, 2008

I've just posted mywebsite andthis error keep being trhrown as soon as I access the DB
I dont understand what is going on and if I dont get it working bu today will delivery date will expire and I will get in trouble...
So anyone knows what is going on
It says the following:
An error has occurred while establishing a connection to the server.  When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
Here is my con string :
<add name="ASPNETDBConnectionString" connectionString="Data Source=p3swhsql-v09.shr.secureserver.net;Initial Catalog=myCatalog;User ID=MyID;Password='Mypassword"/>
Thanks a lot

View 4 Replies View Related

Is There A Way To Hold The Results Of A Select Query Then Operate On The Results And Changes Will Be Reflected On The Actual Data?

Apr 1, 2007

hi,  like, if i need to do delete some items with the id = 10000 then also need to update on the remaining items on the with the same idthen i will need to go through all the records to fetch the items with the same id right?  so, is there something that i can use to hold those records so that i can do the delete and update just on those records  and don't need to query twice? or is there a way to do that in one go ?thanks in advance! 

View 1 Replies View Related

Connecting To Sql Server 2000 On Godaddy Error: (provider: Named Pipes Provider, Error: 40 - Could Not Open A Connection To SQL Server)

Mar 5, 2007

Facts:1. I am using my account on Godaddy trying to connect to my sql server db.2. I can get into my db using user id and password.3. Godaddy's help file shows this for a connection string: connectstr = "Driver={SQL Server};SERVER=" & db_server & ";DATABASE="
&db_name & ";UID=" & db_username & ";PWD=" &
db_userpassword4. My connection string: "Server=whsql-v09.prod.mesa1.secureserver.net;uid=dbasolutions;pwd=***;database=DB_87972;"  & _                    "Trusted_Connection=False providerName=System.Data.SqlClient"{password **** out}5. Get error message  An error has occurred while establishing a connection to the server.  When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server) I tried to email Godaddy's help desk with this information. There first response: We do not allow remote connections to our sql server database.There second response was to read the help file!Does anybody have any suggestions?  Thanks in advance,bswanson     

View 1 Replies View Related

Data Provider Or Other Service Returned An E_Fail Status In Sql Server 2005

May 15, 2007

after converting database from sql server 2000 to sql server 2005. my program on vb6 is facing runtime error. i.e.data provider or other service returned an E_Fail status .

how can i get rid this problem

View 2 Replies View Related

SQL Server 2005 &&amp; Data Provider Or Other Service Returned An E_FAIL Status

Apr 22, 2007

Dear all,



I am running an Access adp application with SQL Server 2005 as back end database. I run a query by using Management Studio query window, and it returned correct results with some columns containing NULL value. But when I run this query through MS Access client side, popup an error "Data provider or other service returned an E_FAIL status" and crash the Access application. I moved the database back to SQL Server 2000, and it runs perfect on both client side and server side returning the correct result. This query is important for the application. Please help!!!!



Query as followed:



SELECT TOP (100) PERCENT dbo.VWINFO312FYTRStreamEnrolments.StudentID, dbo.RequiredStreams.StreamType,
dbo.VWINFO312FYTRStreams.StreamCode + CAST(dbo.VWINFO312FYTRStreams.StreamNo AS varchar) AS FullStreamCode,
dbo.DaysOfWeek.DayCode, dbo.VWINFO312FYTRClasses.StartTime, dbo.VWINFO312FYTRClasses.EndTime, dbo.VWINFO312FYTRClasses.Room,
dbo.Tutors.TutorName, dbo.Tutors.PhoneExtn, dbo.Tutors.OfficeHours, dbo.DaysOfWeek.DaySequence, dbo.RequiredStreams.StreamOrder
FROM dbo.RequiredStreams INNER JOIN
dbo.VWINFO312FYTRStreams ON dbo.RequiredStreams.PaperID = dbo.VWINFO312FYTRStreams.PaperID AND
dbo.RequiredStreams.StreamCode = dbo.VWINFO312FYTRStreams.StreamCode INNER JOIN
dbo.VWINFO312FYTRStreamEnrolments ON dbo.VWINFO312FYTRStreams.PaperID = dbo.VWINFO312FYTRStreamEnrolments.PaperID AND
dbo.VWINFO312FYTRStreams.StreamCode = dbo.VWINFO312FYTRStreamEnrolments.StreamCode AND
dbo.VWINFO312FYTRStreams.StreamNo = dbo.VWINFO312FYTRStreamEnrolments.StreamNo LEFT OUTER JOIN
dbo.DaysOfWeek INNER JOIN
dbo.VWINFO312FYTRClasses ON dbo.DaysOfWeek.DayCode = dbo.VWINFO312FYTRClasses.DayofWeek ON
dbo.VWINFO312FYTRStreams.PaperID = dbo.VWINFO312FYTRClasses.PaperID AND
dbo.VWINFO312FYTRStreams.StreamCode = dbo.VWINFO312FYTRClasses.StreamCode AND
dbo.VWINFO312FYTRStreams.StreamNo = dbo.VWINFO312FYTRClasses.StreamNo LEFT OUTER JOIN
dbo.Tutors ON dbo.VWINFO312FYTRClasses.ResponsibleTutor = dbo.Tutors.TutorID

View 4 Replies View Related

Data Provider Or Other Service Returned An E_Fail Status In Sql Server 2005

May 17, 2007

Main_Module.STRCNNN1 = "driver={SQL Server};server=" & Main_Module.Server_Name & ";" & _
"uid=SA;pwd=;database=" & Main_Module.Common_Database
error msg is

runtime error

data provider or other service returned an E_Fail status in sql server 2005



when i am fetching record from view using order by clause in select statement then error is coming

as

select * from vew_emp where grade='C' order empno



at the first time it fetching record with order by

but when i am using recordset.Requiry

it cud not fetch the record

i think when the recordset is open with the record of view

i am deleting ,inserting record in the view base table then the main recordset is not working

without using order by it is running and working well
plz reply me quickly

View 3 Replies View Related

Missing Data Mining Provider In Management Studio Linked Server Definition

Dec 7, 2006



I'm trying to define a linked server using Microsoft OLE DB Provider for Data Mining Services. MSDMine data provider is missing. Do you know where I can get this? Thanks in advance.

I'm have a Xeon 64bit proc. using SP2. And had installed:

SQLServer2005_ADOMD_x64.msi, SLQServer2005_ASOLEDB9_x64.msi,SQLServer2005_OLAPDM_x64.msi, and SQLServer2005_XMO_x64.msi.

View 4 Replies View Related

Can't Connect To Linked SQL Server: Cannot Initialize The Data Source Object Of OLE DB Provider SQLNCLI

May 23, 2007

I find this most perplexing.



I have two servers, DEV and PROD. Now my DEV server works just great, I can connect to the linked server, query, etc... all is well.



So I'm setting up my PROD server and when I go to add the linked server I get:

Cannot initialize the data source object of OLE DB provider "SQLNCLI".... and Unable to complete login process due to delay in opening server connection.



Now I am running SQL Server 2005 and connecting to an SQL 2000 server.



The odd part is that this works just fine on DEV.



When I go to create the linked server I set:

Linked Server: "LinkedServerName"

Server Type: "SQL Server"



and that's it.



I go to Security and enter my DOMAINUSER.ACCOUNT and then enter the login creds for the linked server.



When I click "OK" I get the above mentioned error code.



Any thoughts?

View 2 Replies View Related

Cannot Initialize Data Source Object Of OLE DB Provider When Reset Linked Server To Oracle

Aug 19, 2015

I wanna to create a linked server which connect to oracle.  Here are my steps:

1.Install Oracel drivers Oracle Data Access Components.

2.Configure the Oracle Ole DB provider to run inside the SQL Server process and configure it to accept parameters. exec

master.dbo.sp_MSset_oledb_prop
'ORAOLEDB.Oracle',
N'AllowInProcess', 1
exec master.dbo.sp_MSset_oledb_prop
'ORAOLEDB.Oracle',
N'DynamicParameters', 1 

3.Create linked server with scripts:
exec sp_addlinkedserver N'MyOracle1', 'Oracle', 'ORAOLEDB.Oracle', N'//10.154.14.235', N'FetchSize=2000', ''
exec sp_addlinkedsrvlogin @rmtsrvname='MyOracle', @useself=N'FALSE', @rmtuser=N'root', @rmtpassword='Sqlexp!23'    
4. After create successful and testing the connection ,I got the error below.(My windows firewall is turn off)

An exception occurred while executing a Transact-SQL statement or batch. (Microsoft.SqlServer.ConnectionInfo)

Cannot initialize the data source object of OLE DB provider "ORAOLEDB.Oracle" for linked server "MyOracle".OLE DB provider "ORAOLEDB.Oracle" for linked server "MyOracle" returned message "ORA-12504: TNS:listener was not given the SERVICE_NAME in CONNECT_DATA". (Microsoft SQL Server, Error: 7303)

View 4 Replies View Related

Failed To Find Or Load The Registered .Net Framework Data Provider When Using SQL Server Compact Edition

Jul 3, 2007

Hello



I have recently downloaded Orcas beta VS product and had no previous version of VS before. The install went clean and I have been able to generate Window apps and web apps with very little issues; however, I have one issue with running a web app using the "view in browser" option for checking an aspx page for validity. If I use the default Northwind database provided and generate an aspx form using the "DataSet" toolbox widget, the tool prompts for the datasource etc. required to generate the required code. I can select the Northwind database and select the desired columns from one of the tables. Once completed, I build the project (clean build) and then select the "view in browser" option to verify the results. The result is an error page indicating a server error ->
Failed to find or load the registered .Net Framework Data Provider.

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.Configuration.ConfigurationErrorsException: Failed to find or load the registered .Net Framework Data Provider.



I created on odbc connection to an iSeries(as400) box and was successfull in displaying the table on the webpage! I looked into the web.config file and it appears that all the required XML data is present. Any help would be appreciated as I am fairly green when it comes the .NET world.



Thanks

View 5 Replies View Related

A Transport-level Error Has Occurred When Receiving Results From The Server.(provider:TCP Provider,error:0-The Handle Is Invalid

Jan 24, 2007

Hi,



I am using SQL Server 2005,



while trying to retrieve data from the database; I am getting the following
error:



A transport-level error has occurred when receiving results
from the server. (Provider: TCP Provider, error: 0 - The handle is invalid.)



But I am getting this error randomly.







Can some one help me out?
Waiting for your response



Sudhakar

View 7 Replies View Related

A Transport-level Error Has Occurred When Receiving Results From The Server. (provider: TCP Provider, Error: 0 - The Handle Is I

Mar 8, 2007

Hi,

Basically the error that I am getting is in our test automation when running as non-admin on the box (regular user). We use .Net C# SQLConnection class to connect to SQL express 2005 impersonating with admin credentials. After getting the connection we try to execute a select command and it some time fails with following error:
A transport-level error has occurred when receiving results from the server. (provider: TCP Provider, error: 0 - The handle is invalid.) at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) at System.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject stateObj, UInt32 error) at System.Data.SqlClient.TdsParserStateObject.ReadSni(DbAsyncResult asyncResult, TdsParserStateObject stateObj) at System.Data.SqlClient.TdsParserStateObject.ReadPacket(Int32 bytesExpected) at System.Data.SqlClient.TdsParserStateObject.ReadBuffer() at System.Data.SqlClient.TdsParserStateObject.ReadByte() at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) at System.Data.SqlClient.SqlDataReader.ConsumeMetaData() at System.Data.SqlClient.SqlDataReader.get_MetaData() at System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) at System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result) at System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method) at System.Data.SqlClient.SqlCommand.ExecuteReader(CommandBehavior behavior, String method) at System.Data.SqlClient.SqlCommand.ExecuteReader()

This happen only in the non-admin scenario mentioned above. Any idea what is triggering this?

Thanks in advance for all replies.

View 3 Replies View Related

Any Solution? Cannot Initialize The Data Source Object Of OLE DB Provider Microsoft.jet.oledb.4.0 For Linked Server (null).

Jul 22, 2007

This is a problem that never get solved, sometime I can use other way to avoid it, but havn't found a solution yet, i hope I can get some more idea here.

I am using SQL 2005, when I run



select * into #import1
from OpenRowSet('microsoft.jet.oledb.4.0','Excel 8.0;hdr=yes;database=\ws8webjeff2.xls',
'select * from [jeff2$]')



I get

Cannot initialize the data source object of OLE DB provider "microsoft.jet.oledb.4.0" for linked server "(null)".



when I try to compile a SP with that statement in it, I get the same error, like



create stored procedure test

as begin

select * into #import1
from OpenRowSet('microsoft.jet.oledb.4.0','Excel 8.0;hdr=yes;database=\ws8webjeff2.xls',
'select * from [jeff2$]')

end



so it seems the error may not relate to the real file, since at the compile stage, it should not check the real file?



On my live db, after I restart the SQL service, the statement will work, after a while, one or several days, I get the same error again. I can not restart my live db quite often for sure, so now I have another backup db server, I need run the statement on the backup server and then read the data from there.



I have the same problem at two places, both use SQL 2005.



So far there are three questions

1, why it works after restart, but only last for a while? something about memory? since the backup db seldom need restart and work fine after many days.



2, why it gives error in compile stage?



3, why two dbs in different Enviroment has the same problem



The most answer I have gathered so far is permission issue, true I got similar error if the import file is located in a place which SQL has no right to access. But in this case, it should not be.



Any other idea or suggestion?



thanks

View 2 Replies View Related

SQL Server Mobile Merge Replication Walkthrough, Cant Find The .NET Framework Data Provider For SQL Server Mobile Edition.

Sep 9, 2005

Hi,

View 3 Replies View Related







Copyrights 2005-15 www.BigResource.com, All rights reserved