error: 'Dts' does not exist in the namespace 'Microsoft.Sqlserver'

I tried to create a package from a C# program, and I copied this from SQL server online book:

using Microsoft.Sqlserver.Dts.Runtime;

But I got compilation error:
The type or namespace name 'Dts' does not exist in the namespace 'Microsoft.Sqlserver'(are you missing an asssembly reference?)
What am I missing?

Thanks a lot

Have you, in fact, set a reference to Microsoft.SqlServer.ManagedDTS ? This is the assembly that contains the Dts.Runtime namespace.

-Doug
|||How do I set a reference to ManagedDTS? by writting:
using Microsoft.SqlServer.ManagedDTS
?

In this case ManagedDTS can not be found by compiler

Thanks for the hint
|||Please consult the Books Online for support. For example, the following article mentions what DLLs need to be registered:

ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/dtsref9/html/e44bcc70-32d3-43e8-a84b-29aef819d5d3.htm
regards,
ash|||found the solution: from visual studio, click Project->Add reference, then browse the assembly ManagedDTS.dll at directory c:\program files\microsoft sql server\90\SDK\Assemblies, this willl add ManagedDTS.dll to the project and solve the problem.

Thanks everyone!|||

Hello,

if you get this problem on your server. build your site in release mode and then you have this dll in your bin\release folder.

Either find this DLL and upload that in your server bin directory manually

error: 'Dts' does not exist in the namespace 'Microsoft.Sqlserver'

I tried to create a package from a C# program, and I copied this from SQL server online book:

using Microsoft.Sqlserver.Dts.Runtime;

But I got compilation error:
The type or namespace name 'Dts' does not exist in the namespace 'Microsoft.Sqlserver'(are you missing an asssembly reference?)
What am I missing?

Thanks a lotHave you, in fact, set a reference to Microsoft.SqlServer.ManagedDTS ? This is the assembly that contains the Dts.Runtime namespace.

-Doug|||How do I set a reference to ManagedDTS? by writting:
using Microsoft.SqlServer.ManagedDTS
?

In this case ManagedDTS can not be found by compiler

Thanks for the hint|||Please consult the Books Online for support. For example, the following article mentions what DLLs need to be registered:

ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/dtsref9/html/e44bcc70-32d3-43e8-a84b-29aef819d5d3.htm
regards,
ash|||found the solution: from visual studio, click Project->Add reference, then browse the assembly ManagedDTS.dll at directory c:\program files\microsoft sql server\90\SDK\Assemblies, this willl add ManagedDTS.dll to the project and solve the problem.

Thanks everyone!|||

Hello,

if you get this problem on your server. build your site in release mode and then you have this dll in your bin\release folder.

Either find this DLL and upload that in your server bin directory manually

Error: 17884

I'm looking for more information on Error: 17884
Error: 17884, Severity: 1, State: 0
Potential deadlocks exist on all the schedulers
I have done a google and usenet search and not found alot on scheduler
deadlocks
other types of deadlocks are commen, not scheduler deadlocks
The following kb article is not alot of help either
http://support.microsoft.com/kb/319892
Error 17882 and 17884
These messages indicate that all the UMS schedulers have experienced yield
problems. This indicates a SQL Server system wide problem and SQL Server
will appear to have stopped responding. As with the 17881 and 17883
messages, consult the error log and Microsoft the Knowledge Base for more
information. If necessary, engage in extended support efforts.
I am wondering if someone may have more information on this so I can try a
few things before opening a ticket with MS. The last time I had to open a
ticket they were helpful, and did help us solve the problem, but it took
many weeks.
I have had problems with temp db and our disk system in the past, that was
resolved and it has been about a year of fairly smooth running until this
popped up. It seems to happen once a week, or once every two weeks with
seemingly no pattern.
If you think you may have some ideas and need more information I will try to
get it for you.
It is a heavily used 24x7 database with alot of stress on the disk system
sql std sp3a, w2k sp4, 3gigs ram, dual xeon 2.4gig 6x72gig drives in a
hardware raid10
thanks,
DaveV
Dave V wrote:
> I'm looking for more information on Error: 17884
> Error: 17884, Severity: 1, State: 0
> Potential deadlocks exist on all the schedulers
> I have done a google and usenet search and not found alot on scheduler
> deadlocks
> other types of deadlocks are commen, not scheduler deadlocks
> The following kb article is not alot of help either
> http://support.microsoft.com/kb/319892
> Error 17882 and 17884
> These messages indicate that all the UMS schedulers have experienced
> yield problems. This indicates a SQL Server system wide problem and
> SQL Server will appear to have stopped responding. As with the 17881
> and 17883 messages, consult the error log and Microsoft the Knowledge
> Base for more information. If necessary, engage in extended support
> efforts.
> I am wondering if someone may have more information on this so I can
> try a few things before opening a ticket with MS. The last time I had
> to open a ticket they were helpful, and did help us solve the
> problem, but it took many weeks.
> I have had problems with temp db and our disk system in the past,
> that was resolved and it has been about a year of fairly smooth
> running until this popped up. It seems to happen once a week, or once
> every two weeks with seemingly no pattern.
> If you think you may have some ideas and need more information I will
> try to get it for you.
> It is a heavily used 24x7 database with alot of stress on the disk
> system
> sql std sp3a, w2k sp4, 3gigs ram, dual xeon 2.4gig 6x72gig drives in
> a hardware raid10
>
> thanks,
> DaveV
Sounds like an internal problem with SQL Server related to your disk
subsystem. I would open a support ticket immediately.
David Gugick
Imceda Software
www.imceda.com
|||Hi
If it is disk subsystem as David suggests, KB 810885 describes the issue.
It have only seen this on large EMC systems and your drive subsystem does
not seem to be fast enough to have this problem.
I would install Hotfix 878 as I have seen a lot of scheduler issues fixed in
that timeframe.
http://support.microsoft.com/default...b;en-us;838166
That hotfix is the highest publicly available hotfix you can download
without opening a support incident. If it does not help, open a case with
PSS.
Regards
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"David Gugick" <davidg-nospam@.imceda.com> wrote in message
news:O6LzmtQ1EHA.936@.TK2MSFTNGP12.phx.gbl...
> Dave V wrote:
> Sounds like an internal problem with SQL Server related to your disk
> subsystem. I would open a support ticket immediately.
> --
> David Gugick
> Imceda Software
> www.imceda.com
>

Error: 17884

I'm looking for more information on Error: 17884
Error: 17884, Severity: 1, State: 0
Potential deadlocks exist on all the schedulers
I have done a google and usenet search and not found alot on scheduler
deadlocks
other types of deadlocks are commen, not scheduler deadlocks
The following kb article is not alot of help either
http://support.microsoft.com/kb/319892
Error 17882 and 17884
These messages indicate that all the UMS schedulers have experienced yield
problems. This indicates a SQL Server system wide problem and SQL Server
will appear to have stopped responding. As with the 17881 and 17883
messages, consult the error log and Microsoft the Knowledge Base for more
information. If necessary, engage in extended support efforts.
I am wondering if someone may have more information on this so I can try a
few things before opening a ticket with MS. The last time I had to open a
ticket they were helpful, and did help us solve the problem, but it took
many weeks.
I have had problems with temp db and our disk system in the past, that was
resolved and it has been about a year of fairly smooth running until this
popped up. It seems to happen once a week, or once every two weeks with
seemingly no pattern.
If you think you may have some ideas and need more information I will try to
get it for you.
It is a heavily used 24x7 database with alot of stress on the disk system
sql std sp3a, w2k sp4, 3gigs ram, dual xeon 2.4gig 6x72gig drives in a
hardware raid10
thanks,
DaveVDave V wrote:
> I'm looking for more information on Error: 17884
> Error: 17884, Severity: 1, State: 0
> Potential deadlocks exist on all the schedulers
> I have done a google and usenet search and not found alot on scheduler
> deadlocks
> other types of deadlocks are commen, not scheduler deadlocks
> The following kb article is not alot of help either
> http://support.microsoft.com/kb/319892
> Error 17882 and 17884
> These messages indicate that all the UMS schedulers have experienced
> yield problems. This indicates a SQL Server system wide problem and
> SQL Server will appear to have stopped responding. As with the 17881
> and 17883 messages, consult the error log and Microsoft the Knowledge
> Base for more information. If necessary, engage in extended support
> efforts.
> I am wondering if someone may have more information on this so I can
> try a few things before opening a ticket with MS. The last time I had
> to open a ticket they were helpful, and did help us solve the
> problem, but it took many weeks.
> I have had problems with temp db and our disk system in the past,
> that was resolved and it has been about a year of fairly smooth
> running until this popped up. It seems to happen once a week, or once
> every two weeks with seemingly no pattern.
> If you think you may have some ideas and need more information I will
> try to get it for you.
> It is a heavily used 24x7 database with alot of stress on the disk
> system
> sql std sp3a, w2k sp4, 3gigs ram, dual xeon 2.4gig 6x72gig drives in
> a hardware raid10
>
> thanks,
> DaveV
Sounds like an internal problem with SQL Server related to your disk
subsystem. I would open a support ticket immediately.
--
David Gugick
Imceda Software
www.imceda.com|||Hi
If it is disk subsystem as David suggests, KB 810885 describes the issue.
It have only seen this on large EMC systems and your drive subsystem does
not seem to be fast enough to have this problem.
I would install Hotfix 878 as I have seen a lot of scheduler issues fixed in
that timeframe.
http://support.microsoft.com/default.aspx?scid=kb;en-us;838166
That hotfix is the highest publicly available hotfix you can download
without opening a support incident. If it does not help, open a case with
PSS.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"David Gugick" <davidg-nospam@.imceda.com> wrote in message
news:O6LzmtQ1EHA.936@.TK2MSFTNGP12.phx.gbl...
> Dave V wrote:
> > I'm looking for more information on Error: 17884
> >
> > Error: 17884, Severity: 1, State: 0
> > Potential deadlocks exist on all the schedulers
> >
> > I have done a google and usenet search and not found alot on scheduler
> > deadlocks
> >
> > other types of deadlocks are commen, not scheduler deadlocks
> >
> > The following kb article is not alot of help either
> >
> > http://support.microsoft.com/kb/319892
> >
> > Error 17882 and 17884
> >
> > These messages indicate that all the UMS schedulers have experienced
> > yield problems. This indicates a SQL Server system wide problem and
> > SQL Server will appear to have stopped responding. As with the 17881
> > and 17883 messages, consult the error log and Microsoft the Knowledge
> > Base for more information. If necessary, engage in extended support
> > efforts.
> >
> > I am wondering if someone may have more information on this so I can
> > try a few things before opening a ticket with MS. The last time I had
> > to open a ticket they were helpful, and did help us solve the
> > problem, but it took many weeks.
> >
> > I have had problems with temp db and our disk system in the past,
> > that was resolved and it has been about a year of fairly smooth
> > running until this popped up. It seems to happen once a week, or once
> > every two weeks with seemingly no pattern.
> >
> > If you think you may have some ideas and need more information I will
> > try to get it for you.
> >
> > It is a heavily used 24x7 database with alot of stress on the disk
> > system
> >
> > sql std sp3a, w2k sp4, 3gigs ram, dual xeon 2.4gig 6x72gig drives in
> > a hardware raid10
> >
> >
> > thanks,
> > DaveV
> Sounds like an internal problem with SQL Server related to your disk
> subsystem. I would open a support ticket immediately.
> --
> David Gugick
> Imceda Software
> www.imceda.com
>sql

Error: 17884

I'm looking for more information on Error: 17884
Error: 17884, Severity: 1, State: 0
Potential deadlocks exist on all the schedulers
I have done a google and usenet search and not found alot on scheduler
deadlocks
other types of deadlocks are commen, not scheduler deadlocks
The following kb article is not alot of help either
http://support.microsoft.com/kb/319892
Error 17882 and 17884
These messages indicate that all the UMS schedulers have experienced yield
problems. This indicates a SQL Server system wide problem and SQL Server
will appear to have stopped responding. As with the 17881 and 17883
messages, consult the error log and Microsoft the Knowledge Base for more
information. If necessary, engage in extended support efforts.
I am wondering if someone may have more information on this so I can try a
few things before opening a ticket with MS. The last time I had to open a
ticket they were helpful, and did help us solve the problem, but it took
many weeks.
I have had problems with temp db and our disk system in the past, that was
resolved and it has been about a year of fairly smooth running until this
popped up. It seems to happen once a week, or once every two weeks with
seemingly no pattern.
If you think you may have some ideas and need more information I will try to
get it for you.
It is a heavily used 24x7 database with alot of stress on the disk system
sql std sp3a, w2k sp4, 3gigs ram, dual xeon 2.4gig 6x72gig drives in a
hardware raid10
thanks,
DaveVDave V wrote:
> I'm looking for more information on Error: 17884
> Error: 17884, Severity: 1, State: 0
> Potential deadlocks exist on all the schedulers
> I have done a google and usenet search and not found alot on scheduler
> deadlocks
> other types of deadlocks are commen, not scheduler deadlocks
> The following kb article is not alot of help either
> http://support.microsoft.com/kb/319892
> Error 17882 and 17884
> These messages indicate that all the UMS schedulers have experienced
> yield problems. This indicates a SQL Server system wide problem and
> SQL Server will appear to have stopped responding. As with the 17881
> and 17883 messages, consult the error log and Microsoft the Knowledge
> Base for more information. If necessary, engage in extended support
> efforts.
> I am wondering if someone may have more information on this so I can
> try a few things before opening a ticket with MS. The last time I had
> to open a ticket they were helpful, and did help us solve the
> problem, but it took many weeks.
> I have had problems with temp db and our disk system in the past,
> that was resolved and it has been about a year of fairly smooth
> running until this popped up. It seems to happen once a week, or once
> every two weeks with seemingly no pattern.
> If you think you may have some ideas and need more information I will
> try to get it for you.
> It is a heavily used 24x7 database with alot of stress on the disk
> system
> sql std sp3a, w2k sp4, 3gigs ram, dual xeon 2.4gig 6x72gig drives in
> a hardware raid10
>
> thanks,
> DaveV
Sounds like an internal problem with SQL Server related to your disk
subsystem. I would open a support ticket immediately.
David Gugick
Imceda Software
www.imceda.com|||Hi
If it is disk subsystem as David suggests, KB 810885 describes the issue.
It have only seen this on large EMC systems and your drive subsystem does
not seem to be fast enough to have this problem.
I would install Hotfix 878 as I have seen a lot of scheduler issues fixed in
that timeframe.
http://support.microsoft.com/defaul...kb;en-us;838166
That hotfix is the highest publicly available hotfix you can download
without opening a support incident. If it does not help, open a case with
PSS.
Regards
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
IM: mike@.epprecht.net
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"David Gugick" <davidg-nospam@.imceda.com> wrote in message
news:O6LzmtQ1EHA.936@.TK2MSFTNGP12.phx.gbl...
> Dave V wrote:
> Sounds like an internal problem with SQL Server related to your disk
> subsystem. I would open a support ticket immediately.
> --
> David Gugick
> Imceda Software
> www.imceda.com
>

Error: "EXECUTE permission denied on object..."

I get this error when I try to preview a report that uses a stored procedure. The stored procedure does not exist in the database, but in the directory I run the report from. The stored procedure declares which database to use, and to create the temp table I want. Do I require special permissions on the sql db I am using to be able to create temp tables? Any help would be great, thanks!

Michael

How are you connecting to the stored procedure in a directory?

SQL Profiler may let you troubleshoot what user account and object this error message relates to.

|||

I had a developer do this awhile ago too; you require elevated permissions to create tables. Try just clearing the table rather than deleting and recreating the table every time the report is run it requires less security.

Error>>"SQL Server does not exist or access denied"

I have re-installed Visual Studio and SQL Server and now i am getting this error for all applications i try to run
Error:

"

SQL Server does not exist or access denied.

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: SQL Server does not exist or access denied.
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: SQL Server does not exist or access denied.] System.Data.SqlClient.ConnectionPool.GetConnection(Boolean& isInTransaction) +474 System.Data.SqlClient.SqlConnectionPoolManager.GetPooledConnection(SqlConnectionString options, Boolean& isInTransaction) +372 System.Data.SqlClient.SqlConnection.Open() +384 System.Data.Common.DbDataAdapter.QuietOpen(IDbConnection connection, ConnectionState& originalState) +44 System.Data.Common.DbDataAdapter.FillFromCommand(Object data, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior) +304 System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior) +77 System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, String srcTable) +36 ResNet2.top_animals.BindGrid() +64 ResNet2.top_animals.Page_Load(Object sender, EventArgs e) +525 System.Web.UI.Control.OnLoad(EventArgs e) +67 System.Web.UI.Control.LoadRecursive() +35 System.Web.UI.Page.ProcessRequestMain() +731

"
any suggestions?We will need to see your connection string to be able to help you.
|||

tmorton wrote:

We will need to see your connection string to be able to help you.

Connection String:

Session("ResNet_Connection_String") = "workstation id=PC_ID;packet size=4096;user id=USER_ID;data source=SAC063;persist" & _

" security info=True;initial catalog=Jo;password=PASSWORD"

The connection string was working fine before installations. I got a feeling that the application is not able to connect to sql server at all and there is some wee configurations which got to be done.

|||

Other than just trying to connect to the SQL server i was even trying to connect to the local SQL Sserver (MSDE 2000) which gives a slightly different error:

Error:
***************************************************************************************************************************************************************************************************************

Server Error in '/TestApp' Application.

---

Login failed for user '4NSQ11J\ASPNET'.

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: Login failed for user '4NSQ11J\ASPNET'.
Source Error:

Line 179: Private Sub Page_Load(ByVal sender As System.Object, ByVal e As System.EventArgs) Handles MyBase.LoadLine 180: 'Put user code to initialize the page hereLine 181: Me.SqlDataAdapter1.Fill(Me.DataSet1)Line 182: Me.DataGrid1.DataSource = Me.DataSet1Line 183: Me.DataGrid1.DataBind()

Source File:c:\inetpub\wwwroot\TestApp\DbTest_App.aspx.vb Line:181
Stack Trace:

[SqlException: Login failed for user '4NSQ11J\ASPNET'.] System.Data.SqlClient.ConnectionPool.GetConnection(Boolean& isInTransaction) +472 System.Data.SqlClient.SqlConnectionPoolManager.GetPooledConnection(SqlConnectionString options, Boolean& isInTransaction) +372 System.Data.SqlClient.SqlConnection.Open() +384 System.Data.Common.DbDataAdapter.QuietOpen(IDbConnection connection, ConnectionState& originalState) +44 System.Data.Common.DbDataAdapter.FillFromCommand(Object data, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior) +304 System.Data.Common.DbDataAdapter.Fill(DataSet dataSet, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior) +77 System.Data.Common.DbDataAdapter.Fill(DataSet dataSet) +38 TestApp.WebForm1.Page_Load(Object sender, EventArgs e) in c:\inetpub\wwwroot\TestApp\DbTest_App.aspx.vb:181 System.Web.UI.Control.OnLoad(EventArgs e) +67 System.Web.UI.Control.LoadRecursive() +35 System.Web.UI.Page.ProcessRequestMain() +731

---

Version Information: Microsoft .NET Framework Version:1.1.4322.573; ASP.NET Version:1.1.4322.573

***************************************************************************************************************************************************************************************************************
Where 'NSQ11J' is my local server as well as computer name.

|||Does the user who is trying to run the query have sufficient access rights on the database/table?
Tryst
|||

Tryst wrote:

Does the user who is trying to run the query have sufficient access rights on the database/table?
Tryst

Yes DB Owner rights!|||Do you have your <machinename>/ASPNET as the user in the USER accounts ? and make sure this user account has permissions on the tables/stored procs.|||

ndinakar wrote:

Do you have your <machinename>/ASPNET as the user in the USER accounts ? and make sure this user account has permissions on the tables/stored procs.

As i mentioned earlier the account i am using has got DBO rights.|||Solution Found:

Ther Alias port had to be set to a specific one to listen to TCP/IP protocols.

Steps to check the Alias settings:

1) go to 'Client Network Utility' in Microsoft SQL Server utlities

2)check if there are any protocols disabled which you going to use in the application

3)click on the tab 'Alias' to add/edit/remove currently Alias servers in the list

Thanks for you guys help anyway!

Cheers
Umer|||Hi UmerTahir,
you solved the problem by doing this, but what exactly was the problem you had with the Server Network Utility?
Tryst
|||

Tryst wrote:

Hi UmerTahir,
you solved the problem by doing this, but what exactly was the problem you had with the Server Network Utility?
Tryst

The problem was with the application and its connection to the SQL server. To access the sql server through TCP/IP protocols some empty port is required which is usualy left to be detected automatically. In my case i had to access through specific port which my company has set for some security issues so that solved the problem.
Umer

Error with a fieldname that does not exist anymore.

I get an :
[Microsoft][ODBC SQL Server Driver}[SQL Server]Invalid column name
'oldfieldname_eid'
While inserting in the Enterprise Manager. The 'oldfieldname_eid' does not
exist in any table of the target database. The error only occurs if an
insert trigger is defined. The insert trigger does not contain a string
resembling the 'oldfieldname_eid'. The name has been used in the past for a
field.
The error does reproduce, after a reset of the client, after setting the
database offline and online again.
The error does disappear when the trigger is 'removed' but reappears
again when the trigger is recreated. The error does not appear when
a 'dummy' trigger is used, only containing "print 'hello'"
Does anybody have a suggestion ?
ben brugmanIt would have been quite helpful if you had posted the text of the trigger,
because that seems to be where the problem is, now we have to make a guess.
One thing I can think of is if you have a view on the table that contained
the 'oldfieldname_eid' column, and that view contains SELECT *. The
definition of a view is not updated automatically when the underlying table
changes, so the column might still exist in the view definition.
Try SELECT table_name FROM information_schema.columns
WHERE column_name = 'oldfieldname_eid'
to find a view or table that includes a column with that name.
--
Jacco Schalkwijk
SQL Server MVP
"ben brugman" <ben@.niethier.nl> wrote in message
news:O$T6PNioDHA.2512@.TK2MSFTNGP09.phx.gbl...
> I get an :
> [Microsoft][ODBC SQL Server Driver}[SQL Server]Invalid column name
> 'oldfieldname_eid'
> While inserting in the Enterprise Manager. The 'oldfieldname_eid' does not
> exist in any table of the target database. The error only occurs if an
> insert trigger is defined. The insert trigger does not contain a string
> resembling the 'oldfieldname_eid'. The name has been used in the past for
a
> field.
> The error does reproduce, after a reset of the client, after setting the
> database offline and online again.
> The error does disappear when the trigger is 'removed' but reappears
> again when the trigger is recreated. The error does not appear when
> a 'dummy' trigger is used, only containing "print 'hello'"
> Does anybody have a suggestion ?
> ben brugman
>
>|||> Try SELECT table_name FROM information_schema.columns
> WHERE column_name = 'oldfieldname_eid'
The field 'oldfieldname_eid' does not appear in any View/table or trigger.
It does not appear anywhere anymore in the complete database.
There does not exist a field 'oldfieldname_eid'.
If we change the fieldname into 'AAAAAA' we get the following error
that the field 'newfieldname_eid' does not exist
> > [Microsoft][ODBC SQL Server Driver}[SQL Server]Invalid column name
> > 'newfieldname_eid'
> It would have been quite helpful if you had posted the text of the
trigger,
> because that seems to be where the problem is, now we have to make a
guess.
For the trigger see the end of the message.
Adding a new column to the table with 'newfieldname_eid' next to 'AAAAAA'
and
then deleting the 'AAAAAA' field did solve the problem. We expect that the
count
of columns did have a mismatch in the internal meta data and that this was
solved
by adding and deletion of columns. (But this is a guess).
(The table appears to be exactly as when the error occured but the error is
'gone').
(probably a bug).
We still would like to know what happened !
ben brugman
The trigger.
The trigger :
SET QUOTED_IDENTIFIER ON
GO
SET ANSI_NULLS ON
GO
CREATE TRIGGER [TR_I_Tabel2] ON dbo.Tabel1
FOR INSERT
NOT FOR REPLICATION
AS
INSERT INTO
Tabel2 (Field1, Field2, Field3, Field4, Field5, Field6)
SELECT
Field1, Field2, Field3, current_Field4, current_Field5, current_Field6
FROM inserted
UPDATE
Tabel1
SET
Field7 =NULL
FROM
Tabel1
INNER JOIN
inserted
ON
Tabel1.Field3 = inserted.Field3
INNER JOIN
Table3
ON
Table3.Field4 = inserted.current_Field4
WHERE
Table3.status_nbr >= 50
GO
SET QUOTED_IDENTIFIER OFF
GO
SET ANSI_NULLS ON
GO
> Jacco Schalkwijk
> SQL Server MVP
>
> "ben brugman" <ben@.niethier.nl> wrote in message
> news:O$T6PNioDHA.2512@.TK2MSFTNGP09.phx.gbl...
> > I get an :
> >
> > [Microsoft][ODBC SQL Server Driver}[SQL Server]Invalid column name
> > 'oldfieldname_eid'
> >
> > While inserting in the Enterprise Manager. The 'oldfieldname_eid' does
not
> > exist in any table of the target database. The error only occurs if an
> > insert trigger is defined. The insert trigger does not contain a string
> > resembling the 'oldfieldname_eid'. The name has been used in the past
for
> a
> > field.
> > The error does reproduce, after a reset of the client, after setting the
> > database offline and online again.
> >
> > The error does disappear when the trigger is 'removed' but reappears
> > again when the trigger is recreated. The error does not appear when
> > a 'dummy' trigger is used, only containing "print 'hello'"
> >
> > Does anybody have a suggestion ?
> >
> > ben brugman
> >
> >
> >
>

Error while connecting to DB through Public IP

While connecting to the DB through a public IP from my system i'm getting an SQL Server does not exist or access denied.But while using localhost its working fine.DB setting in the web.config file.The Code is

<!-- application specific settings -->
 <appSettings>
 <!-- <add key="connString" value="data source=10.1.1.228;initial catalog=ACE;password=XXXX;persist security info=True;user id=sa;packet size=4096" />-->
 <add key="connString" value="packet size=4096;user id=sa;data source=EBIZ;persist security info=True;initial catalog=ACE;password=password" />
 </appSettings>

What to do for this error.Did you try following the connection string advice athttp://www.connectionstrings.com?

Terri

error while connecting

Hey all,

I am new to ASP.NET. While executing a simple code , i got the error:System.Data.SqlClient.SqlException: SQL Server does not exist or access denied.

Whats wrong?

Regards

Yasir

Maybe the problem is in your connection string or you don't open database connection when executing data manipulating.Please check this again.If you still have a problem.please paste your code here.