Database Authentication Error in FrontPage

Hi,
I am trying to add a Data view to a sharepoint site. When I try to create a
connection to the SQL database I get an Authentication error.
I have tried both the Windows Authentication and a Username. I am a DB
administrator and have full access to the database and its server.
Thanks!Please see the reply in
microsoft.public.sqlserver.connect
-Sue
On Fri, 14 Oct 2005 13:04:04 -0700, "Slim"
<Slim@.discussions.microsoft.com> wrote:

>Hi,
>I am trying to add a Data view to a sharepoint site. When I try to create a
>connection to the SQL database I get an Authentication error.
>I have tried both the Windows Authentication and a Username. I am a DB
>administrator and have full access to the database and its server.
>Thanks!

Database Authentication Error in FP

Hi,
I am trying to add a Data view to a sharepoint site. When I try to create a
connection to the SQL database I get an Authentication error.
I have tried both the Windows Authentication and a Username. I am a DB
administrator and have full access to the database and its server.
Thanks!
It's hard to say without detailed error information. But try
turning on failure audits in SQL Server and check the SQL
Server log to see what account is failing. That should help
you track it down. You also want the entire error message -
there are different types of authentication errors that can
point to different problems.
-Sue
On Fri, 14 Oct 2005 13:04:02 -0700, "Slim"
<Slim@.discussions.microsoft.com> wrote:

>Hi,
>I am trying to add a Data view to a sharepoint site. When I try to create a
>connection to the SQL database I get an Authentication error.
>I have tried both the Windows Authentication and a Username. I am a DB
>administrator and have full access to the database and its server.
>Thanks!

Database Authentication Error in FP

Hi,
I am trying to add a Data view to a sharepoint site. When I try to create a
connection to the SQL database I get an Authentication error.
I have tried both the Windows Authentication and a Username. I am a DB
administrator and have full access to the database and its server.
Thanks!It's hard to say without detailed error information. But try
turning on failure audits in SQL Server and check the SQL
Server log to see what account is failing. That should help
you track it down. You also want the entire error message -
there are different types of authentication errors that can
point to different problems.
-Sue
On Fri, 14 Oct 2005 13:04:02 -0700, "Slim"
<Slim@.discussions.microsoft.com> wrote:

>Hi,
>I am trying to add a Data view to a sharepoint site. When I try to create a
>connection to the SQL database I get an Authentication error.
>I have tried both the Windows Authentication and a Username. I am a DB
>administrator and have full access to the database and its server.
>Thanks!

Database Access Right Issues

Recently I have changed the VB Application for Authentication method
to connect to the SQL Server 7.0 database using the Windows NT
Authentication.

Later I had created permissions for Select, Insert, Update, Delete,
Exec everything based on the Windows NT Authentication on an Active
Directory Group based.

Now I am trying to use the application from the Windows 2000 machine.
It runs normal with the all rules applied.

When I run from a windows 98 PC. It connects to the database without
any problem. When I tried to run the transactions or reports, It
throws the error as either Permission denied or Runt-time Error '13'
Type mismatch like that.

Can anybody tell me the work around for this issue?

I doubt this is something do with OS incompatiblity to access database
tables from Windows 98. Where as it is ok with Windows 2000.

Thanks in advance
SaravanakumarYour problem is with Win98, I believe. Win98 does not use named pipes,
nor does it use Windows Authentication since it does notprovide
security for different users in the same way that Windows 2000 Pro
does.

The solution to the security aspect is to set the sqlserver up with
Mixed mode logon security, and then create, in the sqkserver, a user
name and password for the user that works from thw Win98 machine. Each
time that user attempts to access sqlserver, he will have to specify
the username and password.

You may be able to solve the named pipes problem by disabling this
protocol in the client computer with the Client Network Utility. Run
this utility from the dos command Start>Run>cliconfg.exe. Then disable
Named pipes, or alternatively define an alias for the server instance
that enables only TCP/IP.

I'm not experienced with Win98 so another reader should verify this.
Also check the SQL server 2000 Books Online (download and install from
microsoft web site). This handy help file explains authentication
methods and may also have specific recommendations for Win98.

Mark Ferguson.
Ottawa Canada

On 21 Jun 2004 22:21:28 -0700, kssaran@.hotmail.com (Saravanakumar)
wrote:

>Recently I have changed the VB Application for Authentication method
>to connect to the SQL Server 7.0 database using the Windows NT
>Authentication.
>Later I had created permissions for Select, Insert, Update, Delete,
>Exec everything based on the Windows NT Authentication on an Active
>Directory Group based.
>Now I am trying to use the application from the Windows 2000 machine.
>It runs normal with the all rules applied.
>When I run from a windows 98 PC. It connects to the database without
>any problem. When I tried to run the transactions or reports, It
>throws the error as either Permission denied or Runt-time Error '13'
>Type mismatch like that.
>Can anybody tell me the work around for this issue?
>I doubt this is something do with OS incompatiblity to access database
>tables from Windows 98. Where as it is ok with Windows 2000.
>Thanks in advance
>Saravanakumar

Database Access across servers or Firewall Issue

Hi All,

I am facing a strange issue with accessing data from SQL server 2000. We are using SQL Server authentication for connecting to SQL Server 2000 and ADO .Net SQL client in the application. The problem here is, we have databases installed in one of the servers in some other office location that is in different state but on same domain. We do development from two locations that is one from Virtual Machines hosted on servers where Database Servers are located and on our local desktops in India.

Now when I developed a test client in Virtual Machines which will call a web service to get datasetof some data and show them in DataGrid. When I run the test client in debug mode from Visual Studio 2003, then I am getting data in the DataGrid. Even when I just run the exe from Virtual Machine still I am getting data.

But when I copy debug folder of the test client to the local desktop in India and when I run the Test client I am not getting any data loaded on to the DataGrid. I am getting an empty dataset when I am running from the local desktop.

Also I have converted the VS2003 project to VS2005 and when I run the application from Local Desktop then I am getting the data loaded fine. I could not understand what is the problem, what is the difference between accessing data from VS2003 and VS2005 using webservice.

Is this a firewall issue or I am missing any thing here. The webservice method I am calling to get data is actually returning dataset when I am calling this method directly from the browser also and even through application in virtual machine.

I am still not able to come to terms with this problem. This is severely affecting our deployment. Please help us resolve this problem. Please let me know if you need more information.

Thanks,

Venkatesh

Hi Venkatesh,

From what I understand, you have 3 components in your application system. There's the SQL Server, some client code, and a web service.

The SQL Server is in the same domain as the Virtual Machines that you are developing in. Your local desktops in India are in the same domain or a different domain than the SQL Server machine?

Since you are using SQL Server user authentication, the cross domain connectivity should not be an issue. You can verify this by running osql.exe or Query Analyzer tool on your local desktop connecting to the SQL Server machine using the same SQL Server user credentials as your client application.

As for the test client not seeing any data from the web service, I think it would help if you can mention how the web service is connecting to SQL Server and how the ADO.Net application is retrieving data from the web service. I can see the web service using ADO.Net (SqlClient) to connect to the backend SQL Server. Then, some front end client application built using the web service's WSDL document.

I think it will help people understand your application setup and provide possible solutions, if you can specify:

What is the web service using to connect to SQL Server (SqlClient)? Is the web service running on the same machine as SQL Server? If the web service is running on a different machine, is there a connectivity issue between the web service and SQL Server? Is the web service connected to SQL Server using SQL User credentials or Integrated authentication? Does the client application require to send user credentials to connect to the web service?|||

Sorry for the delay in response,

1. Web Service has Business Logic DLL reference which uses SQLClient ADO .Net commands to connect to database.

2. Web Service and SQL Server are on different servers but on the same domain.

3. There is no connectivity issue between the two machines because when I access same WebService through Web Browser, it works fine.

4. Web Service is connecting to SQL Server using SQL User credentials.

5. The User credentials are configured through WebService's Web.Config file.

I really have no clue about this issue. The issue just lies between the Windows Client and Web Service. Because when I access WebService directly through Web Browser then the Web Method is returning data, that means Web Service is getting the data fine but it is not able to give it to the Client.

FYI this issue occurs only on Windows 2003 Server if I install the same service on Windows 2000 server it works fine.

Anyhelp will be greatly appreciated.

Database Access across servers or Firewall Issue

Hi All,

I am facing a strange issue with accessing data from SQL server 2000. We are using SQL Server authentication for connecting to SQL Server 2000 and ADO .Net SQL client in the application. The problem here is, we have databases installed in one of the servers in some other office location that is in different state but on same domain. We do development from two locations that is one from Virtual Machines hosted on servers where Database Servers are located and on our local desktops in India.

Now when I developed a test client in Virtual Machines which will call a web service to get datasetof some data and show them in DataGrid. When I run the test client in debug mode from Visual Studio 2003, then I am getting data in the DataGrid. Even when I just run the exe from Virtual Machine still I am getting data.

But when I copy debug folder of the test client to the local desktop in India and when I run the Test client I am not getting any data loaded on to the DataGrid. I am getting an empty dataset when I am running from the local desktop.

Also I have converted the VS2003 project to VS2005 and when I run the application from Local Desktop then I am getting the data loaded fine. I could not understand what is the problem, what is the difference between accessing data from VS2003 and VS2005 using webservice.

Is this a firewall issue or I am missing any thing here. The webservice method I am calling to get data is actually returning dataset when I am calling this method directly from the browser also and even through application in virtual machine.

I am still not able to come to terms with this problem. This is severely affecting our deployment. Please help us resolve this problem. Please let me know if you need more information.

Thanks,

Venkatesh

Hi Venkatesh,

From what I understand, you have 3 components in your application system. There's the SQL Server, some client code, and a web service.

The SQL Server is in the same domain as the Virtual Machines that you are developing in. Your local desktops in India are in the same domain or a different domain than the SQL Server machine?

Since you are using SQL Server user authentication, the cross domain connectivity should not be an issue. You can verify this by running osql.exe or Query Analyzer tool on your local desktop connecting to the SQL Server machine using the same SQL Server user credentials as your client application.

As for the test client not seeing any data from the web service, I think it would help if you can mention how the web service is connecting to SQL Server and how the ADO.Net application is retrieving data from the web service. I can see the web service using ADO.Net (SqlClient) to connect to the backend SQL Server. Then, some front end client application built using the web service's WSDL document.

I think it will help people understand your application setup and provide possible solutions, if you can specify:

What is the web service using to connect to SQL Server (SqlClient)? Is the web service running on the same machine as SQL Server? If the web service is running on a different machine, is there a connectivity issue between the web service and SQL Server? Is the web service connected to SQL Server using SQL User credentials or Integrated authentication? Does the client application require to send user credentials to connect to the web service?|||

Sorry for the delay in response,

1. Web Service has Business Logic DLL reference which uses SQLClient ADO .Net commands to connect to database.

2. Web Service and SQL Server are on different servers but on the same domain.

3. There is no connectivity issue between the two machines because when I access same WebService through Web Browser, it works fine.

4. Web Service is connecting to SQL Server using SQL User credentials.

5. The User credentials are configured through WebService's Web.Config file.

I really have no clue about this issue. The issue just lies between the Windows Client and Web Service. Because when I access WebService directly through Web Browser then the Web Method is returning data, that means Web Service is getting the data fine but it is not able to give it to the Client.

FYI this issue occurs only on Windows 2003 Server if I install the same service on Windows 2000 server it works fine.

Anyhelp will be greatly appreciated.