Showing posts with label type. Show all posts
Showing posts with label type. Show all posts

Sunday, March 25, 2012

Connecting to SQL Data Base with ADODB

Hi I need help regarding ADODB Connection that i have used in connecting database in my web application, do tell me is this connection type is ok? or I need to switch to ADO.NET Connection.

Hi There,

Of course you still can use ADODB, below is some example:

http://www.dotnetcoders.com/web/Articles/ShowArticle.aspx?article=54

http://www.vbdotnetheaven.com/UploadFile/ptailor/ADODBServices04082005081324AM/ADODBServices.aspx

Having said that, i long run, you should migrate to ADO.net. ;) Good luck!

Thursday, March 8, 2012

Connecting to an Access Database

I am trying to stablish a shared data source to an Access database for my reporting services. Is this possible? I only see connection type Microsoft SQL Server as Connection Type.. OLEDB is not recognized. How can I achieve this?

Hi,

Create a system ODBC data source for your access db from Control Panel Administrative tools.

Create a shared ODBC data souce in RS and select the data source you just created in Control panel.

After that it is business as usual. You may have to finetune some quirks for deployment, the host server should have the ODBC data source as well. An idea would be to try to use an UNC when defining the ODBC datasource and post your access db in a share in some server. That would give more portability.

Philippe

Connecting to an Access Database

I am trying to stablish a shared data source to an Access database for my reporting services. Is this possible? I only see connection type Microsoft SQL Server as Connection Type.. OLEDB is not recognized. How can I achieve this?

Hi,

Create a system ODBC data source for your access db from Control Panel Administrative tools.

Create a shared ODBC data souce in RS and select the data source you just created in Control panel.

After that it is business as usual. You may have to finetune some quirks for deployment, the host server should have the ODBC data source as well. An idea would be to try to use an UNC when defining the ODBC datasource and post your access db in a share in some server. That would give more portability.

Philippe

Sunday, February 19, 2012

connecting jdbc type 4 with ms sql server.

Hello to all,

I am using windows 2000 and i want to connect to ms sql server with
jdbc type 4 driver.
can you give me sample code and few tips to get me through this.,

thank you in advance,
vishnu.http://support.microsoft.com/defaul...kb;en-us;313100

http://java.sun.com/docs/books/tuto...ot0/sample.html

HTH,
Dave

"vishnu mahendra" <vishnu_mahendra@.yahoo.com> wrote in message
news:c24d8b9.0311200931.2e4d5ad2@.posting.google.co m...
> Hello to all,
> I am using windows 2000 and i want to connect to ms sql server with
> jdbc type 4 driver.
> can you give me sample code and few tips to get me through this.,
> thank you in advance,
> vishnu.|||"Dave Hau" <nospam_dave_nospam_123@.nospam_netscape_nospam.net_ nospam> wrote in message news:<puevb.11619$_m6.10136@.newssvr13.news.prodigy.com>...
> http://support.microsoft.com/defaul...kb;en-us;313100
> http://java.sun.com/docs/books/tuto...ot0/sample.html
> HTH,
> Dave
>
> "vishnu mahendra" <vishnu_mahendra@.yahoo.com> wrote in message
> news:c24d8b9.0311200931.2e4d5ad2@.posting.google.co m...
> > Hello to all,
> > I am using windows 2000 and i want to connect to ms sql server with
> > jdbc type 4 driver.
> > can you give me sample code and few tips to get me through this.,
> > thank you in advance,
> > vishnu.

hello dave,

Thank you for the information.
your help is much appreciated.

vishnu.

Tuesday, February 14, 2012

Connect to SSIS Service on machine "Servername" failed: Error loading type library/DLL

Got above error on clustered sql2k5 x86 when connect to SSIS, any solution?

Check the article on "How to: Configure Integration Services on a Cluster" @. http://msdn2.microsoft.com/en-us/library/ms345193.aspx

Thanks,
Loonysan

|||Thanks for the info, but it's not related to my problem. SSIS installation is fine, the issue is I got above error when register SSIS in SSMS on active node. I can register same SSIS remotely on passive node without error.

Connect to SSIS Service on machine "Servername" failed: Error loading type library

Hi,

Anyone who can tell me why I get this error !

I can connect to Integration services on the server from another client.

Pls help

//T

I have the same problem from one server but it's working fine from another server.

Scenario:
Our developer have set up a SQL 2005 x32 with Integration Services. Everything works fine.

I set up the production server (x64) clustered and without SSIS. Later on I installed SSIS and configured it according to the guide for failover clustering. From the "old" x32 dev sever we can connect to both SSIS instances but not from the "new" prod server. We get the same error as in the initial post.

Ideas anyone?

|||

I'm getting the same problem and they only solution I've found is to add the user to the local admin group of hte remote server which is obviously not the desired approach.

Did you every manage to resolve this?

thanks

|||

TSZ wrote:

Hi,

Anyone who can tell me why I get this error !

I can connect to Integration services on the server from another client.

Pls help

//T

Is it timing out? It may be a firewall issue, where you would have to have port 135 open between your server and you. Also, you'll want to make sure that your user is in a trusted domain to SSIS.

Brian

|||

Per J wrote:

I have the same problem from one server but it's working fine from another server.

Scenario:
Our developer have set up a SQL 2005 x32 with Integration Services. Everything works fine.

I set up the production server (x64) clustered and without SSIS. Later on I installed SSIS and configured it according to the guide for failover clustering. From the "old" x32 dev sever we can connect to both SSIS instances but not from the "new" prod server. We get the same error as in the initial post.

Ideas anyone?

I know it's a bit OT, but I have the same scenario, but was not able to install SSIS on a failover cluster.
Can you point me to the "Guide" that you used for installation?

Thanks|||

Re: Clustering SSIS, there's a great whitepaper on TechNet or I have a video that can be seen here on how to cluster SSIS (about 10 mins in length): http://www.jumpstarttv.com/Media.aspx?vid=36

Brian

|||I ran into the exact same problem. I found, however, that its not really a SSIS issue, but actually a problem with a DLL, or a registry value from the client tools that was either erased or overwritten with a different version. With that in mind I removed the client tools and reinstalled them and that solved the problem

Connect to SSIS Service on machine "Servername" failed: Error loading type library

Got above error on clustered sql2k5 x86 when connect to SSIS, any solution?

Check the article on "How to: Configure Integration Services on a Cluster" @. http://msdn2.microsoft.com/en-us/library/ms345193.aspx

Thanks,
Loonysan

|||Thanks for the info, but it's not related to my problem. SSIS installation is fine, the issue is I got above error when register SSIS in SSMS on active node. I can register same SSIS remotely on passive node without error.

Connect to SSIS Service on machine "Servername" failed: Error loading type library

Hi,

Anyone who can tell me why I get this error !

I can connect to Integration services on the server from another client.

Pls help

//T

I have the same problem from one server but it's working fine from another server.

Scenario:
Our developer have set up a SQL 2005 x32 with Integration Services. Everything works fine.

I set up the production server (x64) clustered and without SSIS. Later on I installed SSIS and configured it according to the guide for failover clustering. From the "old" x32 dev sever we can connect to both SSIS instances but not from the "new" prod server. We get the same error as in the initial post.

Ideas anyone?

|||

I'm getting the same problem and they only solution I've found is to add the user to the local admin group of hte remote server which is obviously not the desired approach.

Did you every manage to resolve this?

thanks

|||

TSZ wrote:

Hi,

Anyone who can tell me why I get this error !

I can connect to Integration services on the server from another client.

Pls help

//T

Is it timing out? It may be a firewall issue, where you would have to have port 135 open between your server and you. Also, you'll want to make sure that your user is in a trusted domain to SSIS.

Brian

|||

Per J wrote:

I have the same problem from one server but it's working fine from another server.

Scenario:
Our developer have set up a SQL 2005 x32 with Integration Services. Everything works fine.

I set up the production server (x64) clustered and without SSIS. Later on I installed SSIS and configured it according to the guide for failover clustering. From the "old" x32 dev sever we can connect to both SSIS instances but not from the "new" prod server. We get the same error as in the initial post.

Ideas anyone?

I know it's a bit OT, but I have the same scenario, but was not able to install SSIS on a failover cluster.
Can you point me to the "Guide" that you used for installation?

Thanks|||

Re: Clustering SSIS, there's a great whitepaper on TechNet or I have a video that can be seen here on how to cluster SSIS (about 10 mins in length): http://www.jumpstarttv.com/Media.aspx?vid=36

Brian

|||I ran into the exact same problem. I found, however, that its not really a SSIS issue, but actually a problem with a DLL, or a registry value from the client tools that was either erased or overwritten with a different version. With that in mind I removed the client tools and reinstalled them and that solved the problem