Connect to SQL Server: pull

Showing posts with label pull. Show all posts

Thursday, March 22, 2012

Connecting to SQL 2005 from a client pc

I am getting this message. On the actual server I can pull up the report builder, but from a client on the network when trying to connect to the sql report builder I get this message:

PLATFORM VERSION INFO
Windows : 5.1.2600.131072 (Win32NT)
Common Language Runtime : 2.0.50727.42
System.Deployment.dll : 2.0.50727.42 (RTM.050727-4200)
mscorwks.dll : 2.0.50727.42 (RTM.050727-4200)
dfdll.dll : 2.0.50727.42 (RTM.050727-4200)
dfshim.dll : 2.0.50727.42 (RTM.050727-4200)

SOURCES
Deployment url : http://webdev.ci.lubbock.tx.us/reportserver$sql05/reportbuilder/reportbuilder.application

ERROR SUMMARY
Below is a summary of the errors, details of these errors are listed later in the log.
* Activation of http://webdev.ci.lubbock.tx.us/reportserver$sql05/reportbuilder/reportbuilder.application resulted in exception. Following failure messages were detected:
+ Downloading http://webdev.ci.lubbock.tx.us/reportserver$sql05/reportbuilder/reportbuilder.application did not succeed.
+ The remote server returned an error: (401) Unauthorized.

COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.

WARNINGS
There were no warnings during this operation.

OPERATION PROGRESS STATUS
* [3/16/2006 10:10:28 AM] : Activation of http://webdev.ci.lubbock.tx.us/reportserver$sql05/reportbuilder/reportbuilder.application has started.

ERROR DETAILS
Following errors were detected during this operation.
* [3/16/2006 10:10:28 AM] System.Deployment.Application.DeploymentDownloadException (Unknown subtype)
- Downloading http://webdev.ci.lubbock.tx.us/reportserver$sql05/reportbuilder/reportbuilder.application did not succeed.
- Source: System.Deployment
- Stack trace:
at System.Deployment.Application.SystemNetDownloader.DownloadSingleFile(DownloadQueueItem next)
at System.Deployment.Application.SystemNetDownloader.DownloadAllFiles()
at System.Deployment.Application.FileDownloader.Download(SubscriptionState subState)
at System.Deployment.Application.DownloadManager.DownloadManifestAsRawFile(Uri& sourceUri, String targetPath, IDownloadNotification notification, DownloadOptions options, ServerInformation& serverInformation)
at System.Deployment.Application.DownloadManager.DownloadDeploymentManifestDirectBypass(SubscriptionStore subStore, Uri& sourceUri, TempFile& tempFile, SubscriptionState& subState, IDownloadNotification notification, DownloadOptions options, ServerInformation& serverInformation)
at System.Deployment.Application.DownloadManager.DownloadDeploymentManifestBypass(SubscriptionStore subStore, Uri& sourceUri, TempFile& tempFile, SubscriptionState& subState, IDownloadNotification notification, DownloadOptions options)
at System.Deployment.Application.ApplicationActivator.PerformDeploymentActivation(Uri activationUri, Boolean isShortcut)
at System.Deployment.Application.ApplicationActivator.ActivateDeploymentWorker(Object state)
Inner Exception
System.Net.WebException
- The remote server returned an error: (401) Unauthorized.
- Source: System
- Stack trace:
at System.Net.HttpWebRequest.GetResponse()
at System.Deployment.Application.SystemNetDownloader.DownloadSingleFile(DownloadQueueItem next)

COMPONENT STORE TRANSACTION DETAILS
No transaction information is available.

Remote connections is enabled and I am connecting as the servers admin. Any suggestions. I think it might be a user thing, but I am not sure. Do I need to add a user to the report builder folder in iss or what.

Thank you for any suggestions

Have you had any luck with your issue? I am having a similar issue and have posted about it, but so far, no response.

ANY info you might have would be appreciated, thanks!

|||

I'm having the same problem, seams like reportbuilder can't connect to host when you try to use it in an EXTRANET, because if you try it in an INTRANET works perfectly.

I hope someone could help us on this matter. (ASAP)

|||

Couple of things about Report Builder -

1) Report Builder requires the .net framework 2.0 to be installed on the client machine. I think that's the problem you're encountering related to to the .application file.

2) Report Builder requires a direct connection back to the report server in order to work. That means that you have to expose your report server on the extranet. This has security implications for your deployement - when report server is available on the extranet, so are all the other reports that are on that report server. Also, the report server SOAP API is available on the internet - so application authors can try to have programmatic access to your report server.

When pursuing this type of deployment you should evaluate your security story for your corporate data. Often what is sufficient is to provide the actual report output to the user through the use of a ReportViewer control in an ASP.Net application - this reduces the amount of data that is accessible from outside your company's firewall.

Hope that helps,

-Lukasz

|||Hi Lukasz,
I have the same issue, however I am trying to execute the report builder from the server itself. If I login as the domain administrator then it works. If I log in as any one else (even users that are part of the Administrators and Domain Admin accounts) then it fails with this error.

Thoughts?|||

Have you had any luck with this issue? If so, please let me know what you did to figure it out.

|||Have you had any luck with this problem. If so please inform me on your solutions.|||

Your users, are they able to see the report builder button in report manager?

What is the exact error they get when they try to launch report builder?

-Lukasz

|||Yes, they can see the button.

When they click on the Report Builder button a dialog pops up saying that it is Launching Application.

This is quickly replaced by a dialog titled "Cannot start application" which says:
"Cannot retrieve application. Authentication error."

When I click on the details button then I can see the error "The remote server returned an error: (401) Unauthorized."|||We are trying to get the report builder to be accessed from the url and at the time we can, due to the fact that we are allowing the users to access it using the administrator login. At the moment it is not asking for credentials, but we are wanting to add users and allow them access through the users credentials, not the administrators. We are also wanting to allow users to access reports on the server through their credentials and allow certain users access to certain folders on the server. Could you walk us through adding a user and allowing the user access to certain folders on the server and finally the report builder?|||

I think your issue is different than that of the others on this thread. You can get started with security in reporting services here:

http://msdn2.microsoft.com/en-us/library/ms156014.aspx

-Lukasz

|||

Are your users in the same domain or a trusted domain as your report server? Do you use forms authentication for your report server?

-Lukasz

|||I had this same problem and found a good solution here.|||I have the same problem except Reporting Services is running in SharePoint integration mode, setting anonymous access on the report builder directory doesn't help.

Any ideas how to fix this problem when running Reporting Services in integrated mode?

Connecting to SQL 2005 from a client pc

I am getting this message. On the actual server I can pull up the report builder, but from a client on the network when trying to connect to the sql report builder I get this message:

SOURCES
Deployment url : http://webdev.ci.lubbock.tx.us/reportserver$sql05/reportbuilder/reportbuilder.application

COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.

WARNINGS
There were no warnings during this operation.

OPERATION PROGRESS STATUS
* [3/16/2006 10:10:28 AM] : Activation of http://webdev.ci.lubbock.tx.us/reportserver$sql05/reportbuilder/reportbuilder.application has started.

COMPONENT STORE TRANSACTION DETAILS
No transaction information is available.

Thank you for any suggestions

Have you had any luck with your issue? I am having a similar issue and have posted about it, but so far, no response.

ANY info you might have would be appreciated, thanks!

|||

I'm having the same problem, seams like reportbuilder can't connect to host when you try to use it in an EXTRANET, because if you try it in an INTRANET works perfectly.

I hope someone could help us on this matter. (ASAP)

|||

Couple of things about Report Builder -

1) Report Builder requires the .net framework 2.0 to be installed on the client machine. I think that's the problem you're encountering related to to the .application file.

Hope that helps,

-Lukasz

Thoughts?|||

Have you had any luck with this issue? If so, please let me know what you did to figure it out.

|||Have you had any luck with this problem. If so please inform me on your solutions.|||

Your users, are they able to see the report builder button in report manager?

What is the exact error they get when they try to launch report builder?

-Lukasz

|||Yes, they can see the button.

When they click on the Report Builder button a dialog pops up saying that it is Launching Application.

This is quickly replaced by a dialog titled "Cannot start application" which says:
"Cannot retrieve application. Authentication error."

I think your issue is different than that of the others on this thread. You can get started with security in reporting services here:

http://msdn2.microsoft.com/en-us/library/ms156014.aspx

-Lukasz

|||

Are your users in the same domain or a trusted domain as your report server? Do you use forms authentication for your report server?

-Lukasz

Any ideas how to fix this problem when running Reporting Services in integrated mode?

Connecting to SQL 2005 from a client pc

I am getting this message. On the actual server I can pull up the report builder, but from a client on the network when trying to connect to the sql report builder I get this message:

SOURCES
Deployment url : http://webdev.ci.lubbock.tx.us/reportserver$sql05/reportbuilder/reportbuilder.application

COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.

WARNINGS
There were no warnings during this operation.

OPERATION PROGRESS STATUS
* [3/16/2006 10:10:28 AM] : Activation of http://webdev.ci.lubbock.tx.us/reportserver$sql05/reportbuilder/reportbuilder.application has started.

COMPONENT STORE TRANSACTION DETAILS
No transaction information is available.

Thank you for any suggestions

Have you had any luck with your issue? I am having a similar issue and have posted about it, but so far, no response.

ANY info you might have would be appreciated, thanks!

|||

I'm having the same problem, seams like reportbuilder can't connect to host when you try to use it in an EXTRANET, because if you try it in an INTRANET works perfectly.

I hope someone could help us on this matter. (ASAP)

|||

Couple of things about Report Builder -

1) Report Builder requires the .net framework 2.0 to be installed on the client machine. I think that's the problem you're encountering related to to the .application file.

Hope that helps,

-Lukasz

Thoughts?|||

Have you had any luck with this issue? If so, please let me know what you did to figure it out.

|||Have you had any luck with this problem. If so please inform me on your solutions.|||

Your users, are they able to see the report builder button in report manager?

What is the exact error they get when they try to launch report builder?

-Lukasz

|||Yes, they can see the button.

When they click on the Report Builder button a dialog pops up saying that it is Launching Application.

This is quickly replaced by a dialog titled "Cannot start application" which says:
"Cannot retrieve application. Authentication error."

I think your issue is different than that of the others on this thread. You can get started with security in reporting services here:

http://msdn2.microsoft.com/en-us/library/ms156014.aspx

-Lukasz

|||

Are your users in the same domain or a trusted domain as your report server? Do you use forms authentication for your report server?

-Lukasz

Any ideas how to fix this problem when running Reporting Services in integrated mode?
sql sql

Connecting to SQL 2005 from a client pc

I am getting this message. On the actual server I can pull up the report builder, but from a client on the network when trying to connect to the sql report builder I get this message:

SOURCES
Deployment url : http://webdev.ci.lubbock.tx.us/reportserver$sql05/reportbuilder/reportbuilder.application

COMPONENT STORE TRANSACTION FAILURE SUMMARY
No transaction error was detected.

WARNINGS
There were no warnings during this operation.

OPERATION PROGRESS STATUS
* [3/16/2006 10:10:28 AM] : Activation of http://webdev.ci.lubbock.tx.us/reportserver$sql05/reportbuilder/reportbuilder.application has started.

COMPONENT STORE TRANSACTION DETAILS
No transaction information is available.

Thank you for any suggestions

Have you had any luck with your issue? I am having a similar issue and have posted about it, but so far, no response.

ANY info you might have would be appreciated, thanks!

|||

I'm having the same problem, seams like reportbuilder can't connect to host when you try to use it in an EXTRANET, because if you try it in an INTRANET works perfectly.

I hope someone could help us on this matter. (ASAP)

|||

Couple of things about Report Builder -

1) Report Builder requires the .net framework 2.0 to be installed on the client machine. I think that's the problem you're encountering related to to the .application file.

Hope that helps,

-Lukasz

Thoughts?|||

Have you had any luck with this issue? If so, please let me know what you did to figure it out.

|||Have you had any luck with this problem. If so please inform me on your solutions.|||

Your users, are they able to see the report builder button in report manager?

What is the exact error they get when they try to launch report builder?

-Lukasz

|||Yes, they can see the button.

When they click on the Report Builder button a dialog pops up saying that it is Launching Application.

This is quickly replaced by a dialog titled "Cannot start application" which says:
"Cannot retrieve application. Authentication error."

I think your issue is different than that of the others on this thread. You can get started with security in reporting services here:

http://msdn2.microsoft.com/en-us/library/ms156014.aspx

-Lukasz

|||

Are your users in the same domain or a trusted domain as your report server? Do you use forms authentication for your report server?

-Lukasz

Any ideas how to fix this problem when running Reporting Services in integrated mode?

Connecting to SharePoint MSDE Database

I have a SharePoint server that I want to be able to connect to its database
and pull info off. When I installed the Sharepoint server it installed an
instance of msde. For the life of me I cannot remotely connect to this MSDE
instance. I am able to remotely connect to the backup exec instance on the
same server and I am able to connect to it when logged in locally. I read
somewhere that you can only connect to the default instance of msde, is this
true? If so is there a way to change the sharepoint instance to the default
instance? any suggestions to this would be greatly appreciated.Hi,
You should be able to connect to any instance of MSDE, whether or not it
is a default or named instance. In fact you are already connecting to a
named instance (the BACKUPEXEC one). Named instances are identified as
follows:
server_name\instance_name
Default instances are identified just by the server (host) name.
Furthermore you cannot change which instance is the default instance on
your server. There is no such thing as a DEFAULT property associated
with an instance. A default instance is one that uses the name of the
host server. Named instances are a development over SQL Server 7.0 in
which only one instance could be installed per Windows server. To get
around this in SQL Server 2000 and later you can install multiple
instances. You can choose to give them all a unique name or you could
give up to one instance no name. It assumes the name of the host and is
called the default instance.
As far as your problem is concerned, in order to help further you need
to tell us what error message you are getting when you attempting a
connection.
Jonathan
APT SA wrote:
> I have a SharePoint server that I want to be able to connect to its databa
se
> and pull info off. When I installed the Sharepoint server it installed an
> instance of msde. For the life of me I cannot remotely connect to this MS
DE
> instance. I am able to remotely connect to the backup exec instance on th
e
> same server and I am able to connect to it when logged in locally. I read
> somewhere that you can only connect to the default instance of msde, is th
is
> true? If so is there a way to change the sharepoint instance to the defau
lt
> instance? any suggestions to this would be greatly appreciated.|||OK, the error I get when attempting to connect to the sharepoint instance
from computer on LAN on port 1433 is:
SQL server does not exist or access denied
I can connect to Backup Exec instance from same computer on LAN. This
instance uses port 1207
I can connect to Sharepoint instance when logged on locally to the
sharepoint server.
I have port scanned the server and it is listening on port 1207 but not on
port 1433. I can telnet to port 1207 but not to 1433.
I have attempted to change the port # for the sharepoint instance and still
no success. There are no firewalls inbetween the connection.
I am running MSDE for 2000 with sp4 on it
TCP/IP and Named Pipes are enabled on both instances of MSDE.
We are discussing connecting to backupexec instance and linking servers to
sharepoint instance and then pull data off but this is kind of backwards way
of doing this...
"JPD" wrote:

> Hi,
> You should be able to connect to any instance of MSDE, whether or not it
> is a default or named instance. In fact you are already connecting to a
> named instance (the BACKUPEXEC one). Named instances are identified as
> follows:
> server_name\instance_name
> Default instances are identified just by the server (host) name.
> Furthermore you cannot change which instance is the default instance on
> your server. There is no such thing as a DEFAULT property associated
> with an instance. A default instance is one that uses the name of the
> host server. Named instances are a development over SQL Server 7.0 in
> which only one instance could be installed per Windows server. To get
> around this in SQL Server 2000 and later you can install multiple
> instances. You can choose to give them all a unique name or you could
> give up to one instance no name. It assumes the name of the host and is
> called the default instance.
> As far as your problem is concerned, in order to help further you need
> to tell us what error message you are getting when you attempting a
> connection.
> Jonathan
>
> APT SA wrote:
>|||Hi,
Look at the SQL Server error log under c:\program files\microsoft sql
server\mssql\log. The file ERRORLOG should tell you what ip address(es)
and port number(s) the service is listening on. Maybe you could get
more info on what's going wrong in there.
Jonathan
APT SA wrote:[vbcol=seagreen]
> OK, the error I get when attempting to connect to the sharepoint instance
> from computer on LAN on port 1433 is:
> SQL server does not exist or access denied
> I can connect to Backup Exec instance from same computer on LAN. This
> instance uses port 1207
> I can connect to Sharepoint instance when logged on locally to the
> sharepoint server.
> I have port scanned the server and it is listening on port 1207 but not on
> port 1433. I can telnet to port 1207 but not to 1433.
> I have attempted to change the port # for the sharepoint instance and stil
l
> no success. There are no firewalls inbetween the connection.
> I am running MSDE for 2000 with sp4 on it
> TCP/IP and Named Pipes are enabled on both instances of MSDE.
> We are discussing connecting to backupexec instance and linking servers to
> sharepoint instance and then pull data off but this is kind of backwards w
ay
> of doing this...
>
>
> "JPD" wrote:
>

Tuesday, March 20, 2012

Connecting to Oracle from Windows 64bit IA server

I am trying to pull data from an Oracle 9i database to my SQL Server 2005 sp1 database on Windows 2003 64bit Itanium server. Each time I try to use the import wizard, select the Microsoft OLE DB driver for Oracle, I get an error message telling me that the Oracle client tools are not installed. This happened after I had already installed the 9i tools, tested the connection using TNSPING and confirmed the tnsnames file was correct. So, I uninstalled the 9i tools and then installed the 10g client tools. Tested everything after the install and then tried the import again selecting the MS OLE DB driver for Oracle. I again got the error message that the Oracle tools were not installed.

has anyone ran into this problem and if so, were you able to fix it?

It seems that there is an with how Oracle parses the Program Files (x86) directory. Has anyone heard of this?|||

This is a known Oracle bug, with plenty of information about the issue here -

Connecting to Oracle on 64-bit (x64) machine - MSDN Forums
(http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=159581&SiteID=1)

sql sql

Thursday, March 8, 2012

Connecting to another server

Hi,

I have an adp that hits a databse on an 2005SQL server (databseserver). This server needs to pull information from another table in a SQL2000 server database (DBServer). When I click on the button on a form in the adp, I get this error:

"OLE DB provider "SQLNCLI" linked server communications error"

Now the server shows up in the SQL2005 Management studio, and I can open the tables in this database on this server from the studio. Additionally, it did work until recently as we changed the sa password.

I also was able to move some databases off of the SQL2000 server and then this database failed to move; it errors out.

I do not know what I am doing and am looking for help from anyone who can help.

the error looks like the linked server between sql 2005 and 2000 is not able to communicate... just check the Linkedserver configuration and makesure it is configured properly. post thecomplete error with error no

Madhu

|||

Madhu please forgive me but I am not proficient in SQL server. I do not know how to check what you suggested. Could you give me some direction. The error message box that comes up in the ADP application say the following:

OLE DB Provider "SQLNCLI" for linked server "DBServer" returned message "Communication link failure"

Could you please specify what seerver I am to do it on also?

Thank you for your help!

|||

click on Server Objects, right click on Linked Servers and create one if you dot' have one; or right click on the one select property to edit it.

hope this can help!

|||Ok! That did in fact help. I deleted the old link and created a new one but I still get the error I mentioned in my previous post about the communication link failure.|||

OK... delete the existing linked server configuration and start afresh

Scenario

Servers : Server1 ,Server2

you want to configure Server2 as Linkedserver in SERVER1

All the below statement are to be run on Server1

(a) EXEC master.dbo.sp_addlinkedserver @.server = N'Server2', @.srvproduct=N'SQL Server'

(b) EXEC master.dbo.sp_addlinkedsrvlogin @.rmtsrvname=N'Server2',@.useself=N'False',@.locallogin=NULL,@.rmtuser=N'SomeLoginInServer2',@.rmtpassword='Password'

Saturday, February 25, 2012

Connecting Sybase

Hi there

I want to pull data out of sysbase database.

Could you tell me which connection should I use to connect to sybase database?

Rahul Kumar

ny solution?

how to connect to Sybase in SSIS?

Connecting Sybase

Hi there

I want to pull data out of sysbase database.

Could you tell me which connection should I use to connect to sybase database?

Rahul Kumar

ny solution?

how to connect to Sybase in SSIS?

Friday, February 24, 2012

connecting Oracle to SQL 2000?

Hi, i need to build some way of connecting Oracle to SQL Server in order to pull data off Oracle and house it temporarily on SQL 2000 for searching.

Basically we've built an intranet using ASP and SQL 2000 and which also pulls data off Oracle, however our connection to Oracle is very slow so an idea to speed it up would be to have SQL store a temporary snapshot of this data and the ASP site query off the fast connection it has to SQL rather than use our slow connection to Oracle.

This temporary snapshot of Oracle data would be stored on SQL 2000 and updated on a scheduled basis.

Any ideas how to do this, or a better way to work this?

Thing is I tried installing the Official Oracle ODBC & Client software on our SQL 2000 server before and it just took out SQL 2000 so would really like to hear other options.

Thanks in advance,

:confused:I'm not sure why you've had such problems with Oracle and SQL Server. They usually behave like siblings... They fight at first until somebody hauls one or the other "out to the woodshed", then they seem to grudgingly accept each other (although they sometimes still squabble).

Things get a wee bit corn-fused sometimes when you install the Oracle ODBC drivers, because most of them either skirt the rules or violate them outright. Most of those problems are well understood by Oracle users (they have to), and are not usually very hard to work around. The biggest problem I've seen is that no two sets of Oracle drivers seem to misbehave in quite the same way, so you are always fighting a new and different battle with them.

Once I get the Oracle ODBC problems resolved, I'm usually "home free" until the next release. If you are having problems beyond that, I'd like to hear about them... It is almost always good to get new challenges!

-PatP|||I think my problem was i tried to make a Linked Server connection to Oracle directly inside SQL Enterprise Manager connecting via ODBC and that killed the database.

Thursday, March 22, 2012

Connecting to SQL 2005 from a client pc

Connecting to SQL 2005 from a client pc

Connecting to SQL 2005 from a client pc

Connecting to SQL 2005 from a client pc

Connecting to SharePoint MSDE Database

Connecting to SharePoint MSDE Database

Tuesday, March 20, 2012

Connecting to Oracle from Windows 64bit IA server

Thursday, March 8, 2012

Connecting to another server

Saturday, February 25, 2012

Connecting Sybase

Connecting Sybase

Friday, February 24, 2012

connecting Oracle to SQL 2000?

Connect to SQL Server

Blog Archive

About Me