Error: Cannot open database requested in login projectAllocations. Login fails. Login fail

Hi,
Im getting this error when attempting to retrieve data from an sql database.

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: Cannot open database requested in login 'projectAllocations'. Login fails. Login failed for user 'sa'.

Source Error:

Line 13: objConn = New SqlConnection( "Server=LAB303-066\NETSDK; Database=projectAllocations; User ID=sa;Password=mypassword")
Line 14: objCmd = New SqlCommand("SELECT * FROM project_descriptions", objConn)
Line 15: objConn.Open()
Line 16: objRdr = objCmd.ExecuteReader()
Line 17: While objRdr.Read()

Source File: C:\finalyearproject2\sample.aspx Line: 15

Please Help!! Im a beginner to this, so if anyone knows the answer, take baby steps when explaining. Thanksas the message says you prbly need to give permissions to the user to access the database. in your enterprise manager, if you xpand the databases tab and then the db you are working on, there's a Users tab. click on it and in the panel to your right you would see a list of users. You might need to add the user "projectAllocations" to the list here and give permissions to the user to access the tables/stored procs and other objects..

hth|||Hi,
Thanks for the response. When I login to the web data administrator and expad the database im workin on, there is no users tab. Does the database have to be empty to do this?|||>>in your enterprise manager, if you xpand the databases tab

Error: 1203 - attempting to unlock unowned resource

I have located several references to this issue, most refer to SQL 2000 -
KBs 814654, 828090 (n/a), 331885, etc. Ken Henderson at Tech-Ed 2005
suggested this likely indicates a SQL Server BUG.
Is a more recent SQL 7.0 build available that corrects for this issue?
DESCRIPTION: Error: 1203, Severity: 20, State: 1
Process ID 19 attempting to unlock unowned resource PAG: 14:1:20715.
SQL Server will hang and crash when this occurs. We have correlated this
with concurrent <Log backups plus OLTP users from an ASP application plus MS
Access analytic/query users>.
Can we realistically use PROFILER to trace for this occasional condition and
detect the SPID/Login/Workstation that is implicated in the error? Would
that provide us any useful information? For example, start a TRACE
immediately prior to our hourly Log Backups and stop the trace after they
complete? The occurrence of this issue is capricious.
SQL Server 7.00.1094, NT Server 4.0 with latest SPs and Hotfixes.
Issues began after applying build 1094. I have turned off lightwegtht
pooling (inherited from a prior DBA), applied NPFS patch to NT 4.0, had
developer use MAXDOP Query Hint,. reconfigured the Server to MAXDOP = 1, and
am ready to perform invasive monitoring to detect the root cause and a cure.
Thanks in advance for any suggestions on this very annoying problem.
Hi,
Welcome to use MSDN Managed Newsgroup!
From your descriptions, I understood you encounter the error message
"Process ID <number> attempting to unlock unowned resource PAG". If I have
misunderstood your concern, please feel free to point it out.
As you have found KB 828090 said "When you run the xp_sendmail stored
procedure on a computer that is running SQL Server 7.0 versions 7.00.1085
to 7.00.1098, error 1203 is reported in the SQL Server error log.
Subsequently, a fatal exception might occur, causing the computer that is
running SQL Server to shut down"
The hotfix for KB 828090 is available now, but it is only intended to
correct the problem that this article describes. Apply it only to systems
that are experiencing this specific problem.
To resolve this problem, contact Microsoft Product Support Services to
obtain the hotfix. For a complete list of Microsoft Product Support
Services phone numbers and information about support costs, visit the
following Microsoft Web site:
http://support.microsoft.com/default.aspx?scid=fh;[LN];CNTACTMS
NOTE that ONLY asking for hotfix by contacting PSS will be a FREE service.
Please apply the hotfix and then let me know whether it works for you.
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.

Error: 1203 - attempting to unlock unowned resource

I have located several references to this issue, most refer to SQL 2000 -
KBs 814654, 828090 (n/a), 331885, etc. Ken Henderson at Tech-Ed 2005
suggested this likely indicates a SQL Server BUG.
Is a more recent SQL 7.0 build available that corrects for this issue?
----
DESCRIPTION: Error: 1203, Severity: 20, State: 1
Process ID 19 attempting to unlock unowned resource PAG: 14:1:20715.
----
SQL Server will hang and crash when this occurs. We have correlated this
with concurrent <Log backups plus OLTP users from an ASP application plus MS
Access analytic/query users>.
Can we realistically use PROFILER to trace for this occasional condition and
detect the SPID/Login/Workstation that is implicated in the error? Would
that provide us any useful information? For example, start a TRACE
immediately prior to our hourly Log Backups and stop the trace after they
complete? The occurrence of this issue is capricious.
SQL Server 7.00.1094, NT Server 4.0 with latest SPs and Hotfixes.
Issues began after applying build 1094. I have turned off lightwegtht
pooling (inherited from a prior DBA), applied NPFS patch to NT 4.0, had
developer use MAXDOP Query Hint,. reconfigured the Server to MAXDOP = 1, and
am ready to perform invasive monitoring to detect the root cause and a cure.
Thanks in advance for any suggestions on this very annoying problem.Hi,
Welcome to use MSDN Managed Newsgroup!
From your descriptions, I understood you encounter the error message
"Process ID <number> attempting to unlock unowned resource PAG". If I have
misunderstood your concern, please feel free to point it out.
As you have found KB 828090 said "When you run the xp_sendmail stored
procedure on a computer that is running SQL Server 7.0 versions 7.00.1085
to 7.00.1098, error 1203 is reported in the SQL Server error log.
Subsequently, a fatal exception might occur, causing the computer that is
running SQL Server to shut down"
The hotfix for KB 828090 is available now, but it is only intended to
correct the problem that this article describes. Apply it only to systems
that are experiencing this specific problem.
To resolve this problem, contact Microsoft Product Support Services to
obtain the hotfix. For a complete list of Microsoft Product Support
Services phone numbers and information about support costs, visit the
following Microsoft Web site:
http://support.microsoft.com/default.aspx?scid=fh;[LN];CNTACTMS
NOTE that ONLY asking for hotfix by contacting PSS will be a FREE service.
Please apply the hotfix and then let me know whether it works for you.
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================This posting is provided "AS IS" with no warranties, and confers no rights.

Error: 1203 - attempting to unlock unowned resource

I have located several references to this issue, most refer to SQL 2000 -
KBs 814654, 828090 (n/a), 331885, etc. Ken Henderson at Tech-Ed 2005
suggested this likely indicates a SQL Server BUG.
Is a more recent SQL 7.0 build available that corrects for this issue?
----
DESCRIPTION: Error: 1203, Severity: 20, State: 1
Process ID 19 attempting to unlock unowned resource PAG: 14:1:20715.
----
SQL Server will hang and crash when this occurs. We have correlated this
with concurrent <Log backups plus OLTP users from an ASP application plus MS
Access analytic/query users>.
Can we realistically use PROFILER to trace for this occasional condition and
detect the SPID/Login/Workstation that is implicated in the error? Would
that provide us any useful information? For example, start a TRACE
immediately prior to our hourly Log Backups and stop the trace after they
complete? The occurrence of this issue is capricious.
SQL Server 7.00.1094, NT Server 4.0 with latest SPs and Hotfixes.
Issues began after applying build 1094. I have turned off lightwegtht
pooling (inherited from a prior DBA), applied NPFS patch to NT 4.0, had
developer use MAXDOP Query Hint,. reconfigured the Server to MAXDOP = 1, and
am ready to perform invasive monitoring to detect the root cause and a cure.
Thanks in advance for any suggestions on this very annoying problem.Hi,
Welcome to use MSDN Managed Newsgroup!
From your descriptions, I understood you encounter the error message
"Process ID <number> attempting to unlock unowned resource PAG". If I have
misunderstood your concern, please feel free to point it out.
As you have found KB 828090 said "When you run the xp_sendmail stored
procedure on a computer that is running SQL Server 7.0 versions 7.00.1085
to 7.00.1098, error 1203 is reported in the SQL Server error log.
Subsequently, a fatal exception might occur, causing the computer that is
running SQL Server to shut down"
The hotfix for KB 828090 is available now, but it is only intended to
correct the problem that this article describes. Apply it only to systems
that are experiencing this specific problem.
To resolve this problem, contact Microsoft Product Support Services to
obtain the hotfix. For a complete list of Microsoft Product Support
Services phone numbers and information about support costs, visit the
following Microsoft Web site:
http://support.microsoft.com/defaul...scid=fh;[LN];CNTACTMS
NOTE that ONLY asking for hotfix by contacting PSS will be a FREE service.
Please apply the hotfix and then let me know whether it works for you.
Thank you for your patience and cooperation. If you have any questions or
concerns, don't hesitate to let me know. We are always here to be of
assistance!
Sincerely yours,
Michael Cheng
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
========================================
=============
This posting is provided "AS IS" with no warranties, and confers no rights.

Error with restoring Backups

I recieved 4 database's that were backed up from our client. They are using SQL Server 2000 and each of the files has no extension.

When attempting to restore a database of the same name in SQL Server Express 2k5 I recieve the following error.

System.Data.SqlClient.SqlError: The media set has 2 media families but only 1 are provided

Is there a way to restore the backup without the log backup?

Thank you
-Robert-

Hi,

i just guess that you don′t have a full backup specified here. YOu will have to pick the Full backup and apply the Diff. backups or transactional backups afterwards.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

Error with Registering a SQL Server 2000.

Anyone heard of this error when attempting to Register a
SQL Server from Enterprise Manager Standard 2000 client.
Invalid attribute/Option Identifier. If so, how have you
resolved it?
The error is usually related to an MDAC issue. Try
reapplying SP3a.
-Sue
On Wed, 24 Mar 2004 12:58:00 -0800, "Jackson_Greg"
<anonymous@.discussions.microsoft.com> wrote:

>Anyone heard of this error when attempting to Register a
>SQL Server from Enterprise Manager Standard 2000 client.
>Invalid attribute/Option Identifier. If so, how have you
>resolved it?

Error with Registering a SQL Server 2000.

Anyone heard of this error when attempting to Register a
SQL Server from Enterprise Manager Standard 2000 client.
Invalid attribute/Option Identifier. If so, how have you
resolved it?The error is usually related to an MDAC issue. Try
reapplying SP3a.
-Sue
On Wed, 24 Mar 2004 12:58:00 -0800, "Jackson_Greg"
<anonymous@.discussions.microsoft.com> wrote:

>Anyone heard of this error when attempting to Register a
>SQL Server from Enterprise Manager Standard 2000 client.
>Invalid attribute/Option Identifier. If so, how have you
>resolved it?

Error with linked Servers

I am having an extremely difficult time getting a linked server to
work. I am attempting to link to using an ODBC driver to a proprietary
database. I can create the ODBC connection and see the tables from
with Access using this connection. I can set up the linked server but
as soon as I attempt to view the tables it either gives me an error
7399 or just sits there. Any help would be appreciative and if there
are any other questions I need to answer just let me know.
Thanks,
Matt
Can you elaborate on how are you connecting via Access and how are you using
to create the linked server?
"Matt" wrote:

> I am having an extremely difficult time getting a linked server to
> work. I am attempting to link to using an ODBC driver to a proprietary
> database. I can create the ODBC connection and see the tables from
> with Access using this connection. I can set up the linked server but
> as soon as I attempt to view the tables it either gives me an error
> 7399 or just sits there. Any help would be appreciative and if there
> are any other questions I need to answer just let me know.
> Thanks,
> Matt
>

Error with linked Servers

I am having an extremely difficult time getting a linked server to
work. I am attempting to link to using an ODBC driver to a proprietary
database. I can create the ODBC connection and see the tables from
with Access using this connection. I can set up the linked server but
as soon as I attempt to view the tables it either gives me an error
7399 or just sits there. Any help would be appreciative and if there
are any other questions I need to answer just let me know.
Thanks,
MattCan you elaborate on how are you connecting via Access and how are you using
to create the linked server?
"Matt" wrote:

> I am having an extremely difficult time getting a linked server to
> work. I am attempting to link to using an ODBC driver to a proprietary
> database. I can create the ODBC connection and see the tables from
> with Access using this connection. I can set up the linked server but
> as soon as I attempt to view the tables it either gives me an error
> 7399 or just sits there. Any help would be appreciative and if there
> are any other questions I need to answer just let me know.
> Thanks,
> Matt
>

Error with linked Servers

I am having an extremely difficult time getting a linked server to
work. I am attempting to link to using an ODBC driver to a proprietary
database. I can create the ODBC connection and see the tables from
with Access using this connection. I can set up the linked server but
as soon as I attempt to view the tables it either gives me an error
7399 or just sits there. Any help would be appreciative and if there
are any other questions I need to answer just let me know.
Thanks,
MattCan you elaborate on how are you connecting via Access and how are you using
to create the linked server?
"Matt" wrote:
> I am having an extremely difficult time getting a linked server to
> work. I am attempting to link to using an ODBC driver to a proprietary
> database. I can create the ODBC connection and see the tables from
> with Access using this connection. I can set up the linked server but
> as soon as I attempt to view the tables it either gives me an error
> 7399 or just sits there. Any help would be appreciative and if there
> are any other questions I need to answer just let me know.
> Thanks,
> Matt
>

Error While Installing SQLServer CE

Hi,
I'm attempting to install SQL Server CE on a freshly built Windows XP (IIS 5.1).
I am an administrator on the machine.
I have run Windows Update on the Server, installed .NET Framework 1.1 SP1
and SQL Server 2000 with Service pack ...SP3a.
My Sql Server Registration lists the Product Version as 8.00.760.
I have attempted to install SQL Server CE using the setup.exe version
2.11.15.0 and sqlce20sql2ksp3a.exe version 2.11.15.0.
I have rebooted the machine.
I still get the error "SQL Server CE Server Tools is compatible only with
SQL Server 2000 Service Pack 1 or higher. etc..."
Does anyone have any ideas?
Thanks,
Sailu

Try running MSI (You can extract sqlce20sql2ksp3a.exe into a folder and get the MSI). This is a work around. But, one thing cleear is why Version Check by setup.exe fails.

Thanks,
Laxmi NRO MSFT, SQL Mobile, Microsoft Corporation