Connection is busy with results for another hstmt

HI guys,

I'm using ODBC driver from WinXP SP2 with SQL Server 2005 Express (on my machine for test) and SQL Server 2005 Standard (on the production machine).

With SQL Server 2005 Express I've no problem, but with SQL Server 2005 Standard, in some query, I get "Connection is busy with results for another hstmt".

I'm working with VisualStudio 2003 with standard CDatabase and CRecordSet MFC classes.

I looked for an advice in the Microsoft KB but I found only Service Pack for SQL Server 2000 !

Everything could be useful !

Thanks a lot!

Bye, Domenico

You can avoid this error message by switching to the SQL Server 2005 ODBC driver, 'SQL Native Client' and enabling the MARS (Multiple Active Result Sets feature). There is more information in Books Online and also here http://blogs.msdn.com/dataaccess/archive/2005/08/02/446894.aspx

Connection failed:

Hi Guys,

I encountered an error while opening my third SQL Connection in Enterprise Manager

--------
Microsoft SQL Server Login
--------
Connection failed:
SQLState: '01000'
SQL Server Error: 232
[Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionWrite (WrapperWrite()).
Connection failed:
SQLState: '08S01'
SQL Server Error: 11
[Microsoft][ODBC SQL Server Driver][Shared Memory]General network error. Check your network documentation.

--------
OK
--------

I am using the following
SQL Server 2000 Enterprise Edition (SP4)
Windows 2000 Professional (SP4)

first two connections are with Query Analyzer, the third attempt is when opening a table inside Enterprise Manager

anyone experienced this?Sounds like you have to enable the shared memory protocol for the instance in cliconfg.exe.|||hi MCrowley

yeah, but the problem is, I can't remember what I did (gosh, too much for making experiments :) )

Is there a way on how to reverse this effect?

Thanks|||Is the Shared Memory protocol enabled in Cliconfg.exe?|||Is the Shared Memory protocol enabled in Cliconfg.exe? ;)|||The first thing I would do if I were in your position would be to check the setting of Shared Memory Protocol in cliconfg.exe and make sure it is enabled.

Just my .02 :)|||gosh,

sorry for the very late reply

yes, its enabled, what does this option do by the way?

thanks|||Shared memory is a protocol that can be used by applications running on the same box as SQL Server. Now that it is enabled, do you still get the same error?

Connection failed!

Hi guys,

I have problem with this code:

TCHAR szCurrentDir[250];

TCHAR szDataDir[250];

lstrcpy(szDataDir,

TEXT("DRIVER={SQL Native Client};SERVER=.\\sqlexpress;Trusted_Connection=Yes;DATABASE=MyDic;AttachDBFileName="));

GetCurrentDirectory(sizeof(szCurrentDir), szCurrentDir);

lstrcat(szCurrentDir, TEXT("\\Database\\Data.mdf;"));

lstrcat(szDataDir, szCurrentDir);

SQLDriverConnect(hdbc, hWnd, szDataDir, SQL_NTS, szConnStrOut, sizeof(szConnStrOut), &cbConnStrOut, SQL_DRIVER_COMPLETE);

When I run my program, I get this message:

Microsoft SQL Server Login
Connection failed:
SQLState: '42000'
SQL Server Error: 5133
[Microsoft][SQL Native Client][SQL Server]Directory lookup for the file "C:\Program Files\MyDic\Database\Data.mdf" failed with the operating system error 5(Access is denied.).
Connection failed:
SQLState: '42000'
SQL Server Error: 1832
[Microsoft][SQL Native Client][SQL Server]Could not attach file 'C:\Program Files\MyDic\Database\Data.mdf' as database 'MyDic'.

OK

I have to mention that:

SQL Server: SQL Server (2005) Express

Operating System: Windows XP SP2

and I'm Local Admin.

I wanna deploy this program with data.mdf file that contains program data.

So, How can I fix it?

Regards

Curious issue. It looks like your connection string is correct. Can you check to see if your detached database's assocated .LDF file is read-only? (I had that issue before.) If it doesn't have one, then ignore this suggestion.

Another thing you might try is to see if putting your detached database into the SQL Server's 'Data' folder. Something along the lines of 'C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data'. Again, probably not the issue since you're getting an 'access denied' error, not one about 'file not found'.

Did you detach with same version SQL server? This could be a compatibility issue.

It almost sounds like you're trying to attach a database that already exists. Could this be possible?

Try to debug your issue with the following steps:

1) Create a database, with tables, etc...

2) Detach the database

3) drop the database

4) try to re-attach the database using a connection string like the one above.

If you can get this to work then you should be okay.

If you're still stuck, re-activate this issue and I'll try to think of something else.

~Warren

|||Does C:\Program Files\MyDic\Database\Data.mdf exist? Does the service account for your sqlexpress has permissions to read/write this file? You must have at least read permission to the file to logon to the server. (You cannot relay on sqlexpress create the file for you.)|||

Dear Warren,

I have checked all things you mentioned, but it doesn't work

I think this issue is concerned with the service account for my SQLEXPRESS as Xinwei Hong mentioned.

Well, Do you know how I can change this account programmatically so that I could get rid this issue?

Best

|||

Dear Xinwei,

I think you are right. But how can I change the service account programmatically in order to have read and write permission?

Thanks,

|||

I don't think you need to change the service account programmatically. You can just give the read/write permission to the service account. Do you have any special reason that you don't want to give the permission to the SQL service account on your computer?

Thanks.

|||

That's a tough one. I guess the easiest way would be to create an 'sa' login on your SQL Server installation, and then replace 'Trusted_Connection' with 'User=sa;Pwd=<<WhateverPasswordYouCreated>>;'.

This would guarantee you have admin rights to attach/detach databases.

Second easiest would be to log onto machine as admin, and add your user name as a machine admin. (I’m afraid I’m not too good at showing how to do that on an XP machine, since I only use W2K3 Server.)

The more difficult method to do this programmatically would be to use “Runas”. I’m not positive it would work, but you could try running your application from the command line via ‘Runas admin’ which would give it admin rights, and it should work. Please see http://www.microsoft.com/resources/documentation/windows/xp/all/proddocs/en-us/runas.mspx?mfr=true for more documentation on how to use this.

If anyone else has suggestions, please speak up!

Good luck!

~Warren

|||

Hi Xinwei,

As I said before, I just wanna deploy my program containing data.mdf file. I made installation and I tested but I got this problem. I read some technique to deploy MDF files such az Xcopy, but it didn't work.

sincerely.

|||

Hi Warren,

Thank you for your comments.

By the way, I read this article:

"How to verify and change the system administrator password in MSDE or SQL Server"

http://support.microsoft.com/Default.aspx?scid=kb;en-us;322336&spid=2855&sid=global

But when I created sa, sqlcmd said that sa account disabled. Do you know how I can enable it?

Thanks.

|||

Look here:

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

|||

Dear Markus,

Thank you so much. I got that.

Regards.

Connection Error: ADO.Net and SQL Server 2005

Hi guys,
I have an application that uses ADO.Net (2.0) to connect to SQL Server.
We've never had any problems connecting to SQL Server 2005 using this
application, but one client has had problems and the error he gets is of the
type "General Connection Error...[Microsoft][ODBC SQL Server
Driver][DBNETLIB]ConnectionRead (rec())."
I asked him to create an ODBC connection in Windows just to see if it
was only the application, and he has no problem connecting through ODBC.
So, as you can see, it is very puzzling because when we've had problems
in the past, ODBC would not work either.
Is there some issue with ADO.Net (2.0) and SQL Server 2005? Remember
that other clients are using the software connecting to SQL 2005 with no
problem.
The user says that Firewall is disabled and Remote Connection is enabled
at the server.
Anything else I could check'
Any help will be greatly appreciated.
Thank you,
MaerWell, using ODBC to connect to SQL Server (any version) can and does work.
However, it's certainly not the best way to do so--I recommend SqlClient.
Search my blog for "Connecting" and read the whitepapers there that discuss
the issues.
hth
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
----
---
"Maer" <maer@.auditleverage.com> wrote in message
news:e$qgOMlvHHA.5036@.TK2MSFTNGP03.phx.gbl...
> Hi guys,
> I have an application that uses ADO.Net (2.0) to connect to SQL Server.
> We've never had any problems connecting to SQL Server 2005 using this
> application, but one client has had problems and the error he gets is of
> the type "General Connection Error...[Microsoft][ODBC SQL Server
> Driver][DBNETLIB]ConnectionRead (rec())."
> I asked him to create an ODBC connection in Windows just to see if it
> was only the application, and he has no problem connecting through ODBC.
> So, as you can see, it is very puzzling because when we've had problems
> in the past, ODBC would not work either.
> Is there some issue with ADO.Net (2.0) and SQL Server 2005? Remember
> that other clients are using the software connecting to SQL 2005 with no
> problem.
> The user says that Firewall is disabled and Remote Connection is
> enabled at the server.
> Anything else I could check'
> Any help will be greatly appreciated.
> Thank you,
> Maer
>
>|||Hi Bill,
Thank you for your reply. I am actually using SqlClient, I only created
an ODBC connection to troubleshoot the problem.
So basically, I can connect to the server through an ODBC connection (in
the Data Sources in Windows), but when I try to use SqlClient to establish a
connection, it fails. The connection string is something like this:
"data source=servername;persist security info=True;initial
catalog=databasename;user id=username;Trusted_Connection=yes"
Once again, the error is "General Connection Error...[Microsoft][ODB
C
SQL Server Driver][DBNETLIB]ConnectionRead (rec())."
It is very puzzling because this client doesn't seem to have anything
different in his configuration.
So far I haven't heard of any problems with .Net 2.0 and SQL Server
2005. Could it be .Net?
Thanks,
Maer
"William (Bill) Vaughn" <billvaRemoveThis@.betav.com> wrote in message
news:eCBwqunvHHA.1212@.TK2MSFTNGP05.phx.gbl...
> Well, using ODBC to connect to SQL Server (any version) can and does work.
> However, it's certainly not the best way to do so--I recommend SqlClient.
> Search my blog for "Connecting" and read the whitepapers there that
> discuss the issues.
> hth
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> INETA Speaker
> www.betav.com/blog/billva
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> __________________________________
> Visit www.hitchhikerguides.net to get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> ----
---
> "Maer" <maer@.auditleverage.com> wrote in message
> news:e$qgOMlvHHA.5036@.TK2MSFTNGP03.phx.gbl...
>|||Okay, User ID and Trusted Connection are mutually exclusive. Either your
Windows ID is trusted or it's not. Did you read the whitepaper on
connecting?
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
----
---
"Maer" <maer@.auditleverage.com> wrote in message
news:uuvLyFBwHHA.4992@.TK2MSFTNGP04.phx.gbl...
> Hi Bill,
> Thank you for your reply. I am actually using SqlClient, I only created
> an ODBC connection to troubleshoot the problem.
> So basically, I can connect to the server through an ODBC connection
> (in the Data Sources in Windows), but when I try to use SqlClient to
> establish a connection, it fails. The connection string is something like
> this:
> "data source=servername;persist security info=True;initial
> catalog=databasename;user id=username;Trusted_Connection=yes"
> Once again, the error is "General Connection Error...[Microsoft]
1;ODBC
> SQL Server Driver][DBNETLIB]ConnectionRead (rec())."
> It is very puzzling because this client doesn't seem to have anything
> different in his configuration.
> So far I haven't heard of any problems with .Net 2.0 and SQL Server
> 2005. Could it be .Net?
> Thanks,
> Maer
>
> "William (Bill) Vaughn" <billvaRemoveThis@.betav.com> wrote in message
> news:eCBwqunvHHA.1212@.TK2MSFTNGP05.phx.gbl...
>|||Hi Bill,
Thank you so much for your help. I had read your articles which were
extremely helpful!
It turns out that the problem was that the client had an alias with an
invalid port. He insisted that the port was correct until I asked him to
indulge me and try the default 1433.
The funny thing is that when the port was invalid in the past, the error
I would usually get was something like "server does not exist." So this
error really threw me off.
Once again - thank you for your time.
Maer
"William (Bill) Vaughn" <billvaRemoveThis@.betav.com> wrote in message
news:eZBb2gLwHHA.484@.TK2MSFTNGP06.phx.gbl...
> Okay, User ID and Trusted Connection are mutually exclusive. Either your
> Windows ID is trusted or it's not. Did you read the whitepaper on
> connecting?
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> INETA Speaker
> www.betav.com/blog/billva
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> __________________________________
> Visit www.hitchhikerguides.net to get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> ----
---
> "Maer" <maer@.auditleverage.com> wrote in message
> news:uuvLyFBwHHA.4992@.TK2MSFTNGP04.phx.gbl...
>

Connection Error: ADO.Net and SQL Server 2005

Hi guys,
I have an application that uses ADO.Net (2.0) to connect to SQL Server.
We've never had any problems connecting to SQL Server 2005 using this
application, but one client has had problems and the error he gets is of the
type "General Connection Error...[Microsoft][ODBC SQL Server
Driver][DBNETLIB]ConnectionRead (rec())."
I asked him to create an ODBC connection in Windows just to see if it
was only the application, and he has no problem connecting through ODBC.
So, as you can see, it is very puzzling because when we've had problems
in the past, ODBC would not work either.
Is there some issue with ADO.Net (2.0) and SQL Server 2005? Remember
that other clients are using the software connecting to SQL 2005 with no
problem.
The user says that Firewall is disabled and Remote Connection is enabled
at the server.
Anything else I could check?
Any help will be greatly appreciated.
Thank you,
Maer
Well, using ODBC to connect to SQL Server (any version) can and does work.
However, it's certainly not the best way to do so--I recommend SqlClient.
Search my blog for "Connecting" and read the whitepapers there that discuss
the issues.
hth
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"Maer" <maer@.auditleverage.com> wrote in message
news:e$qgOMlvHHA.5036@.TK2MSFTNGP03.phx.gbl...
> Hi guys,
> I have an application that uses ADO.Net (2.0) to connect to SQL Server.
> We've never had any problems connecting to SQL Server 2005 using this
> application, but one client has had problems and the error he gets is of
> the type "General Connection Error...[Microsoft][ODBC SQL Server
> Driver][DBNETLIB]ConnectionRead (rec())."
> I asked him to create an ODBC connection in Windows just to see if it
> was only the application, and he has no problem connecting through ODBC.
> So, as you can see, it is very puzzling because when we've had problems
> in the past, ODBC would not work either.
> Is there some issue with ADO.Net (2.0) and SQL Server 2005? Remember
> that other clients are using the software connecting to SQL 2005 with no
> problem.
> The user says that Firewall is disabled and Remote Connection is
> enabled at the server.
> Anything else I could check?
> Any help will be greatly appreciated.
> Thank you,
> Maer
>
>
|||Hi Bill,
Thank you for your reply. I am actually using SqlClient, I only created
an ODBC connection to troubleshoot the problem.
So basically, I can connect to the server through an ODBC connection (in
the Data Sources in Windows), but when I try to use SqlClient to establish a
connection, it fails. The connection string is something like this:
"data source=servername;persist security info=True;initial
catalog=databasename;user id=username;Trusted_Connection=yes"
Once again, the error is "General Connection Error...[Microsoft][ODBC
SQL Server Driver][DBNETLIB]ConnectionRead (rec())."
It is very puzzling because this client doesn't seem to have anything
different in his configuration.
So far I haven't heard of any problems with .Net 2.0 and SQL Server
2005. Could it be .Net?
Thanks,
Maer
"William (Bill) Vaughn" <billvaRemoveThis@.betav.com> wrote in message
news:eCBwqunvHHA.1212@.TK2MSFTNGP05.phx.gbl...
> Well, using ODBC to connect to SQL Server (any version) can and does work.
> However, it's certainly not the best way to do so--I recommend SqlClient.
> Search my blog for "Connecting" and read the whitepapers there that
> discuss the issues.
> hth
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> INETA Speaker
> www.betav.com/blog/billva
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> __________________________________
> Visit www.hitchhikerguides.net to get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> ------
> "Maer" <maer@.auditleverage.com> wrote in message
> news:e$qgOMlvHHA.5036@.TK2MSFTNGP03.phx.gbl...
>
|||Okay, User ID and Trusted Connection are mutually exclusive. Either your
Windows ID is trusted or it's not. Did you read the whitepaper on
connecting?
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
INETA Speaker
www.betav.com/blog/billva
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
Visit www.hitchhikerguides.net to get more information on my latest book:
Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
------
"Maer" <maer@.auditleverage.com> wrote in message
news:uuvLyFBwHHA.4992@.TK2MSFTNGP04.phx.gbl...
> Hi Bill,
> Thank you for your reply. I am actually using SqlClient, I only created
> an ODBC connection to troubleshoot the problem.
> So basically, I can connect to the server through an ODBC connection
> (in the Data Sources in Windows), but when I try to use SqlClient to
> establish a connection, it fails. The connection string is something like
> this:
> "data source=servername;persist security info=True;initial
> catalog=databasename;user id=username;Trusted_Connection=yes"
> Once again, the error is "General Connection Error...[Microsoft][ODBC
> SQL Server Driver][DBNETLIB]ConnectionRead (rec())."
> It is very puzzling because this client doesn't seem to have anything
> different in his configuration.
> So far I haven't heard of any problems with .Net 2.0 and SQL Server
> 2005. Could it be .Net?
> Thanks,
> Maer
>
> "William (Bill) Vaughn" <billvaRemoveThis@.betav.com> wrote in message
> news:eCBwqunvHHA.1212@.TK2MSFTNGP05.phx.gbl...
>
|||Hi Bill,
Thank you so much for your help. I had read your articles which were
extremely helpful!
It turns out that the problem was that the client had an alias with an
invalid port. He insisted that the port was correct until I asked him to
indulge me and try the default 1433.
The funny thing is that when the port was invalid in the past, the error
I would usually get was something like "server does not exist." So this
error really threw me off.
Once again - thank you for your time.
Maer
"William (Bill) Vaughn" <billvaRemoveThis@.betav.com> wrote in message
news:eZBb2gLwHHA.484@.TK2MSFTNGP06.phx.gbl...
> Okay, User ID and Trusted Connection are mutually exclusive. Either your
> Windows ID is trusted or it's not. Did you read the whitepaper on
> connecting?
> --
> ____________________________________
> William (Bill) Vaughn
> Author, Mentor, Consultant
> Microsoft MVP
> INETA Speaker
> www.betav.com/blog/billva
> www.betav.com
> Please reply only to the newsgroup so that others can benefit.
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> __________________________________
> Visit www.hitchhikerguides.net to get more information on my latest book:
> Hitchhiker's Guide to Visual Studio and SQL Server (7th Edition)
> and Hitchhiker's Guide to SQL Server 2005 Compact Edition (EBook)
> ------
> "Maer" <maer@.auditleverage.com> wrote in message
> news:uuvLyFBwHHA.4992@.TK2MSFTNGP04.phx.gbl...
>

connection error

Hi guys, my asp.net web page was working fine on my laptop. Until i transferred it into my friend's.. an error msg popped out. My SQL Northwind database was been copied over but still there seems to be a problem with the connection, can any one help me?
Personal guess: You are using an sa username/password in the connection string, and the other server you are connecting to is not set up for SQL security, only Windows security.
Show the connection string you are using (with any passwords obscured, of course).
|||

SqlConnection conn=new SqlConnection("server=localhost;uid=sa;pwd=;database=Northwind");

SqlCommand cmd = conn.CreateCommand();

cmd.CommandText = "SELECT * FROM tblDoor";

conn.Open();
//how to find out what user id to use?

|||Do you have SQL Server or MSDE? If SQL Server, then you should be able to use Enterprise Manager to try and figure out what the SA password is, as well as determining whether SQL Server security is enabled. If you have Enterprise manager, right click the SQL Server and select Porperties. In the properties window, go to the Security tab make sure authentication is set to SQL Server and Windows.|||oh it is working already, thanks man!

Connection between Principal and Mirror servers

Hi guys, right now I am facing this scenario several times and I wonder why it can be happen. Both SQL servers are in Enterprise SP1 edition. The mirroring setup can be work fine to me. Once my principal get attacking by DDOS, then mirroring session change the status to 'DISCONNECTED'. However, after DDOS attack solved and line connection gets back on the principal server, the mirroring session still remain to the status ('DISCONNECTED'). If I restart the SQL services on principal server or mirror server, then only the mirroring session change to 'SYNCHRONIZING' status. Does anyone faced this happen before? I need some assistance on it and hope able to get any explanation or solution from you guys. Thanx and have a nice day.

Best Regards,

Hans

Are the SQL server services set to BOOT or enabled to restart on the failure.

Also chekc the SQL server error log in this case.

Connection

Hi guys,

I'm a little stumped by this one. I was wondering whether anybody has any ideas:

I have an application that uses the following connection string to connect to a SQL server database:

<add key="connectionString" value="workstation id=WKSXXX;packet size=4096;user id=mydatabase;data source=servername;persist security info=True;initial catalog=databasename;password=password" />

The same string has been used for three different databases for the application which has been deployed on three different NT Servers. The application has been put on a fourth NT server, and I've modified this key and double checked it to correspond to the new SQL server. No go.

The application on the new servers connects to the other 3 SQL servers, but not this one. I've checked the connection with OBDC and it succeeds so the database is okay. I've checked the login credentials and they are correct.

Does anybody have any suggestions as to what's going on? Thanks guys!

what error it generates?

thanks

|||

This is the error, however this happens whenever there is a problem connecting to the database. Doesn't tell me much.

Configuration Error

Description:An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.

Parser Error Message:Given arguments NavigationGraph='Task1', CurrentView='viewenquiries', and NavigateValue='fail', could not find next View name. Check the config file to be sure that given the current parameters a next View can be derived correctly; be sure there is a navigateTo node corresponding to this combination of parameters.

Source Error:

[No relevant source lines]

|||

That error message is coming from the User Interface Process (UIP) block, which I assume you're using in the application. It's not a database connection problem as such, although that could be the cause of it.

I'm guessing that there is something messed up in the config file for the UIP. Start looking there.

Don