a DB connection Problem

Hello, I am developping a web application in which I have used SQL Server 2005 (installed in the same comuter ). Now my objective is to migrate the solution to other computer. So I have moved the project to the new Post.. By this way, the connection between the solution and the DB become distant . For this reason when I run this solution the error below is raising

Login failed for user ''. The user is not associated with a trusted SQL Server connection.

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 ''. The user is not associated with a trusted SQL Server connection.

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 (0x80131904): Login failed for user ''. The user is not associated with a trusted SQL Server connection.] System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) +734963 System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) +188 System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) +1838 System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK) +33 System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance) +628 System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance) +170 System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection) +359 System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options) +28 System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject) +424 System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject) +66 System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject) +496 System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) +82 System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) +105 System.Data.SqlClient.SqlConnection.Open() +111 System.Web.DataAccess.SqlConnectionHolder.Open(HttpContext context, Boolean revertImpersonate) +84 System.Web.DataAccess.SqlConnectionHelper.GetConnection(String connectionString, Boolean revertImpersonation) +197 System.Web.Security.SqlMembershipProvider.GetPasswordWithFormat(String username, Boolean updateLastLoginActivityDate, Int32& status, String& password, Int32& passwordFormat, String& passwordSalt, Int32& failedPasswordAttemptCount, Int32& failedPasswordAnswerAttemptCount, Boolean& isApproved, DateTime& lastLoginDate, DateTime& lastActivityDate) +1121 System.Web.Security.SqlMembershipProvider.CheckPassword(String username, String password, Boolean updateLastLoginActivityDate, Boolean failIfNotApproved, String& salt, Int32& passwordFormat) +105 System.Web.Security.SqlMembershipProvider.CheckPassword(String username, String password, Boolean updateLastLoginActivityDate, Boolean failIfNotApproved) +42 System.Web.Security.SqlMembershipProvider.ValidateUser(String username, String password) +83 System.Web.UI.WebControls.Login.OnAuthenticate(AuthenticateEventArgs e) +160 System.Web.UI.WebControls.Login.AttemptLogin() +105 System.Web.UI.WebControls.Login.OnBubbleEvent(Object source, EventArgs e) +99 System.Web.UI.Control.RaiseBubbleEvent(Object source, EventArgs args) +35 System.Web.UI.WebControls.Button.OnCommand(CommandEventArgs e) +115 System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument) +163 System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument) +7 System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) +11 System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData) +33 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +5102

I understand from this that the connection with SQL Server 2005 was failed. I know also that I must change something in the connection String But I don' know it . So how doing this?

Thanks in advance

What's your connection string? I guess you're using Windows Authentication to connect to SQL. Make sure the there is a login for the account used in your connection string in the SQL Server. To manage SQL logins, connect to the SQL Server in Management Studio->go to Security->Logins|||

Hello , My connection strin is as below

<

addname="LocalSqlServer"connectionString="Data Source=IBM7;Initial Catalog=Reclamation;Integrated Security=True"providerName="System.Data.SqlClient" />

According to the message Error I have created a new login named IBM7/ASPNET and a new schema named IBM7/ASPNET owned by the new login IBM7/ASPNET . The error message become as follow:

Server Error in '/Rec_Web' Application.

---

Procédure stockée 'dbo.aspnet_CheckSchemaVersion' introuvable.

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: Procédure stockée 'dbo.aspnet_CheckSchemaVersion' introuvable.

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 (0x80131904): Procédure stockée 'dbo.aspnet_CheckSchemaVersion' introuvable.] System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection) +857338 System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) +734950 System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) +188 System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj) +1838 System.Data.SqlClient.SqlCommand.FinishExecuteReader(SqlDataReader ds, RunBehavior runBehavior, String resetOptionsString) +149 System.Data.SqlClient.SqlCommand.RunExecuteReaderTds(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, Boolean async) +886 System.Data.SqlClient.SqlCommand.RunExecuteReader(CommandBehavior cmdBehavior, RunBehavior runBehavior, Boolean returnStream, String method, DbAsyncResult result) +132 System.Data.SqlClient.SqlCommand.InternalExecuteNonQuery(DbAsyncResult result, String methodName, Boolean sendToPipe) +415 System.Data.SqlClient.SqlCommand.ExecuteNonQuery() +135 System.Web.Util.SecUtility.CheckSchemaVersion(ProviderBase provider, SqlConnection connection, String[] features, String version, Int32& schemaVersionCheck) +367 System.Web.Security.SqlMembershipProvider.CheckSchemaVersion(SqlConnection connection) +85 System.Web.Security.SqlMembershipProvider.GetPasswordWithFormat(String username, Boolean updateLastLoginActivityDate, Int32& status, String& password, Int32& passwordFormat, String& passwordSalt, Int32& failedPasswordAttemptCount, Int32& failedPasswordAnswerAttemptCount, Boolean& isApproved, DateTime& lastLoginDate, DateTime& lastActivityDate) +1121 System.Web.Security.SqlMembershipProvider.CheckPassword(String username, String password, Boolean updateLastLoginActivityDate, Boolean failIfNotApproved, String& salt, Int32& passwordFormat) +105 System.Web.Security.SqlMembershipProvider.CheckPassword(String username, String password, Boolean updateLastLoginActivityDate, Boolean failIfNotApproved) +42 System.Web.Security.SqlMembershipProvider.ValidateUser(String username, String password) +83 System.Web.UI.WebControls.Login.OnAuthenticate(AuthenticateEventArgs e) +160 System.Web.UI.WebControls.Login.AttemptLogin() +105 System.Web.UI.WebControls.Login.OnBubbleEvent(Object source, EventArgs e) +99 System.Web.UI.Control.RaiseBubbleEvent(Object source, EventArgs args) +35 System.Web.UI.WebControls.Button.OnCommand(CommandEventArgs e) +115 System.Web.UI.WebControls.Button.RaisePostBackEvent(String eventArgument) +163 System.Web.UI.WebControls.Button.System.Web.UI.IPostBackEventHandler.RaisePostBackEvent(String eventArgument) +7 System.Web.UI.Page.RaisePostBackEvent(IPostBackEventHandler sourceControl, String eventArgument) +11 System.Web.UI.Page.RaisePostBackEvent(NameValueCollection postData) +33 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +5102

So what should I do ? Thanks in advance

|||

Sorry I can't understand the error message very well. I guess it indicates a permission issue on the'dbo.aspnet_CheckSchemaVersion' .So please make sure you're connecting to the right database which contains the'dbo.aspnet_CheckSchemaVersion', and the IBM7/ASPNET account has proper permission to the database objects. Suppose for the login IBM7/ASPNET, you map it to amyuser user in the database:

grant execute on dbo.aspnet_CheckSchemaVersion tomyuser

Consider the IBM7/ASPNET account may use other database objects, you can add it to the db_owner database role in the database.

|||

Thanks for this indication, I think that I understand the problem : The database to which I want connect is imported from another DB who use the ASP membership feature... but it seems during the DB copy the stored procedures related to the membership weren't copied. For this reason, this procedure wasn't founded. My question now , Is there a manner to copy only the non system stored procedures ?

Thanks in advance

A connection was successfully established with the server, but then an error occurred during the

I have just installed MS SQL Server 2005 Express edition along with the SSMSE. I am using windows authentication. When I open SSMSE it connects me to a 'local instance' of the server. From there I right click on Database and select to add a new Database and I get the error above. I think I only need to allow local connections to the engine but I have tried allowing remote conections with all varations of named pipes and TCP/IP. I am running on Windows XP SP2 (home).Hi,

could you please post the whole error message ?

You might take a look at this site in the meantime: http://blogs.msdn.com/sql_protocols/Default.aspx?p=2

HTH; Jens K. Suessmeyer.

http://www.sqlserver2005.de

A connection was successfully established with the server, but then an error occurred duri

Hi,

I am having such a problem. I have SQL Express installed on the windows 2003 server and originally I installed instance1 of SQL Server 2005. When I installed Instance1, I remember having problems with remotely connecting to that instance1, but somehow I fixed it. Now I installed instance2 and I started having remote connection issues again with that instance2. I am able to connect to instance1 but not instance2. I checked settings for both instances and they look identical.

I turned firewall off for now. I checked TCP settings using surface area configuration (allowing both local and remote connections). I turned off VIA protocol. I specified TCP properties to use dynamic port for that instance2.

In the sql native client configuration I have the following order#: 1. Shared memory, 2. tcp, 3. np, 4. VIA(Disabled). TCP is configured to use 1433.

I have no clue about what is going on. Sometimes I am able to connect remotely and sometimes I get the following error:

"A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: TCP Provider, error: 0 - The specified network name is no longer available.) (.Net SqlClient Data Provider)."

When I connect locally - everything connects fine. File sharing is also checked, it works etc...

Thanks for help!!!

GK

I just noticed that I was able to connect from different computer on the different network.

What kind of account are you trying to connect with, Windows or SQL? I'm guessing it is trying to do a windows authentication but the remote computer isn't authenticated to the domain.

|||

No. It is SQL server account. I connect remotely to the sql server on different network.

Thanks,
GK

|||

You say it only happens sometimes? It sounds like a timeout issue. Changing the connection timeout property in the connection string will temporarily solve your problem but it sounds like there is a greater underlying network problem between the client and sql server.

Connection timeout and other connection string properties:http://msdn2.microsoft.com/en-us/library/system.data.sqlclient.sqlconnection.connectionstring(VS.71).aspx

|||

I am connecting using Client Tools (Enterprise Manager).

You are correct about network problem. I am not sure how to configure network on the server.

It is not timeout.

Also, I am not the only one. It happends to everyone who just installed sql server 2005 with sql express. There so many posts on Google, but not a single solution.

Thanks,
GK

|||

Just to be clear, when you set up sql server 2005 you went in to sql security and cre-created all your logins?

Also, is there SSL or any other kind of extra security on the sql server?

|||

All the accounts have same privilidges, I connect using dbo.

No SSL or anything like that.

Thanks,
GK

|||

I asked whether or not you re-created the accounts when you installed sql server 2005. Did you actually go into sql 2005 and re-create all the accounts.

Also, here is a post that seemed to have helped a couple othershttp://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=984492&SiteID=1

A connection could not be made with report server ...

I just installed SQL Server 2005 (Reporting Services) on my collegues laptop
(Windows XP, SP2) and when we try to deploy the reports we get the message:
"A connection could not be made with report server at
http://localhost/ReportServer"
Everything is running (green checks) in the Reporting Services configuration
manager. We get the error, "Page not found." when we just try to open
http://<machinename>/Reports or http://localhost/Reports. I see the virtual
directories in IIS, all services seem to be running correctly.
Please help! I have installed reporting services about 10 times and have
not run into this problem before. The only issue that we had initially was
that the IIS default web site would not run because there was a conflict on
TCP Port 80, so I switched that TCP Port to port 81 -- this shouldn't be a
problem should it.
Thank you,
Laurie
--
LaurieTWhat happens when you try going to http://localhost/?
Have you tried http://localhost:81/Reports, since that's what you changed
the port to?
Clint
"LaurieT" <LaurieT@.discussions.microsoft.com> wrote in message
news:75CE650E-D235-4DDC-9408-802E8AE9312A@.microsoft.com...
>I just installed SQL Server 2005 (Reporting Services) on my collegues
>laptop
> (Windows XP, SP2) and when we try to deploy the reports we get the
> message:
> "A connection could not be made with report server at
> http://localhost/ReportServer"
> Everything is running (green checks) in the Reporting Services
> configuration
> manager. We get the error, "Page not found." when we just try to open
> http://<machinename>/Reports or http://localhost/Reports. I see the
> virtual
> directories in IIS, all services seem to be running correctly.
> Please help! I have installed reporting services about 10 times and have
> not run into this problem before. The only issue that we had initially
> was
> that the IIS default web site would not run because there was a conflict
> on
> TCP Port 80, so I switched that TCP Port to port 81 -- this shouldn't be a
> problem should it.
> Thank you,
> Laurie
> --
> LaurieT|||Clint -- Thanks, I tried this and still got some errors (although different
than I was seeing before).
I got this error when trying http://localhost:81/Reports
"The XML page cannot be displayed
Cannot view XML input using XSL style sheet. Please correct the error and
then click the Refresh button, or try again later.
----
A name was started with an invalid character. Error processing resource
'http://localhost:81/Reports'. Line 1, Position 2
<%@. Page language="c#" Codebehind="Home.aspx.cs" AutoEventWireup="false"
Inherits="Microsoft.ReportingServices.UI.HomePag..."
Any ideas?
Thank you.
--
LaurieT
"Clint" wrote:
> What happens when you try going to http://localhost/?
> Have you tried http://localhost:81/Reports, since that's what you changed
> the port to?
> Clint
> "LaurieT" <LaurieT@.discussions.microsoft.com> wrote in message
> news:75CE650E-D235-4DDC-9408-802E8AE9312A@.microsoft.com...
> >I just installed SQL Server 2005 (Reporting Services) on my collegues
> >laptop
> > (Windows XP, SP2) and when we try to deploy the reports we get the
> > message:
> > "A connection could not be made with report server at
> > http://localhost/ReportServer"
> >
> > Everything is running (green checks) in the Reporting Services
> > configuration
> > manager. We get the error, "Page not found." when we just try to open
> > http://<machinename>/Reports or http://localhost/Reports. I see the
> > virtual
> > directories in IIS, all services seem to be running correctly.
> >
> > Please help! I have installed reporting services about 10 times and have
> > not run into this problem before. The only issue that we had initially
> > was
> > that the IIS default web site would not run because there was a conflict
> > on
> > TCP Port 80, so I switched that TCP Port to port 81 -- this shouldn't be a
> > problem should it.
> >
> > Thank you,
> > Laurie
> > --
> > LaurieT
>
>|||Sorry, I got nothing else. :) I'm pretty much an RS newbie. Hopefully
someone else can chime in for you.
Clint
"LaurieT" <LaurieT@.discussions.microsoft.com> wrote in message
news:71DB89B9-F5F4-445E-A480-95A635B73ECB@.microsoft.com...
> Clint -- Thanks, I tried this and still got some errors (although
> different
> than I was seeing before).
> I got this error when trying http://localhost:81/Reports
> "The XML page cannot be displayed
> Cannot view XML input using XSL style sheet. Please correct the error and
> then click the Refresh button, or try again later.
>
> ----
> A name was started with an invalid character. Error processing resource
> 'http://localhost:81/Reports'. Line 1, Position 2
> <%@. Page language="c#" Codebehind="Home.aspx.cs" AutoEventWireup="false"
> Inherits="Microsoft.ReportingServices.UI.HomePag..."
> Any ideas?
> Thank you.
> --
> LaurieT
>
> "Clint" wrote:
>> What happens when you try going to http://localhost/?
>> Have you tried http://localhost:81/Reports, since that's what you changed
>> the port to?
>> Clint
>> "LaurieT" <LaurieT@.discussions.microsoft.com> wrote in message
>> news:75CE650E-D235-4DDC-9408-802E8AE9312A@.microsoft.com...
>> >I just installed SQL Server 2005 (Reporting Services) on my collegues
>> >laptop
>> > (Windows XP, SP2) and when we try to deploy the reports we get the
>> > message:
>> > "A connection could not be made with report server at
>> > http://localhost/ReportServer"
>> >
>> > Everything is running (green checks) in the Reporting Services
>> > configuration
>> > manager. We get the error, "Page not found." when we just try to open
>> > http://<machinename>/Reports or http://localhost/Reports. I see the
>> > virtual
>> > directories in IIS, all services seem to be running correctly.
>> >
>> > Please help! I have installed reporting services about 10 times and
>> > have
>> > not run into this problem before. The only issue that we had initially
>> > was
>> > that the IIS default web site would not run because there was a
>> > conflict
>> > on
>> > TCP Port 80, so I switched that TCP Port to port 81 -- this shouldn't
>> > be a
>> > problem should it.
>> >
>> > Thank you,
>> > Laurie
>> > --
>> > LaurieT
>>|||laurie,
I had the same problem and Now it has been fixed.i looked online and
here is what i found:
1)The FIX
For IIS MMC: Right click My Computer...then click manage...under
services and applications....expand IIS
then right click the "reports" virtual directory, select property and
then under the
ASP.NET tab select asp.net version that belongs to the .NET framework
version 2.something. For some reason, after you installed reporting
services,
the version of the ASP.NET was removed from the asp.net tab. click ok
2)New Problem
Then you get this new problem when you go to http://localhost/Reports/
--my comment Failed to access IIS metabase.
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.Web.Hosting.HostingEnvironmentException:
Failed to access IIS metabase.
The process account used to run ASP.NET must have read access to the
IIS metabase (e.g. IIS://servername/W3SVC). For information on
modifying metabase permissions, please see
http://support.microsoft.com/?kbid=267904 .
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:
[HostingEnvironmentException: Failed to access IIS metabase.]
System.Web.Hosting.HostingEnvironment.MapPathCaching(String path)
+3609369 System.Web.CachedPathData.GetPathData(String path) +406
System.Web.Configuration.RuntimeConfigLKG.GetInternalSection
(String sectionName, Type type, ResultsIndex index) +134
2) The FIX
To correct the problem To repair IIS mappings for ASP.NET, run the
Aspnet_regiis.exe utlity. To do so, follow these steps:
Click Start, and then click Run.
Type cmd, and then click OK.
At the command prompt, type the following command, and then press
ENTER:
"\<Windows folder>\Microsoft.NET\Framework\<Version
Number>\aspnet_regiis.exe" -i
NOTE:Replace <Windows folder> with the name of the directory where the
operating system is installed and replace <Version Number> with the
.NET Framework version installed on your computer. Or you could do a
seach for the .exe file and locate the directory
You can find the above reference at
http://support.microsoft.com/default.aspx?scid=kb;en-us;325093
Now try going to http://computername/reports/
Hope it helps,
Sharan Doddakashi
LaurieT wrote:
> Clint -- Thanks, I tried this and still got some errors (although different
> than I was seeing before).
> I got this error when trying http://localhost:81/Reports
> "The XML page cannot be displayed
> Cannot view XML input using XSL style sheet. Please correct the error and
> then click the Refresh button, or try again later.
>
> ----
> A name was started with an invalid character. Error processing resource
> 'http://localhost:81/Reports'. Line 1, Position 2
> <%@. Page language="c#" Codebehind="Home.aspx.cs" AutoEventWireup="false"
> Inherits="Microsoft.ReportingServices.UI.HomePag..."
> Any ideas?
> Thank you.
> --
> LaurieT
>
> "Clint" wrote:
> > What happens when you try going to http://localhost/?
> >
> > Have you tried http://localhost:81/Reports, since that's what you changed
> > the port to?
> >
> > Clint
> >
> > "LaurieT" <LaurieT@.discussions.microsoft.com> wrote in message
> > news:75CE650E-D235-4DDC-9408-802E8AE9312A@.microsoft.com...
> > >I just installed SQL Server 2005 (Reporting Services) on my collegues
> > >laptop
> > > (Windows XP, SP2) and when we try to deploy the reports we get the
> > > message:
> > > "A connection could not be made with report server at
> > > http://localhost/ReportServer"
> > >
> > > Everything is running (green checks) in the Reporting Services
> > > configuration
> > > manager. We get the error, "Page not found." when we just try to open
> > > http://<machinename>/Reports or http://localhost/Reports. I see the
> > > virtual
> > > directories in IIS, all services seem to be running correctly.
> > >
> > > Please help! I have installed reporting services about 10 times and have
> > > not run into this problem before. The only issue that we had initially
> > > was
> > > that the IIS default web site would not run because there was a conflict
> > > on
> > > TCP Port 80, so I switched that TCP Port to port 81 -- this shouldn't be a
> > > problem should it.
> > >
> > > Thank you,
> > > Laurie
> > > --
> > > LaurieT
> >
> >
> >|||Sharan,
Thanks for the valuable solution. That was very helpful, precisely to
the point and it solved the issue.
Good Work!
Shailesh
HELP wrote:
> laurie,
> I had the same problem and Now it has been fixed.i looked online and
> here is what i found:
> 1)The FIX
> For IIS MMC: Right click My Computer...then click manage...under
> services and applications....expand IIS
> then right click the "reports" virtual directory, select property and
> then under the
> ASP.NET tab select asp.net version that belongs to the .NET framework
> version 2.something. For some reason, after you installed reporting
> services,
> the version of the ASP.NET was removed from the asp.net tab. click ok
> 2)New Problem
> Then you get this new problem when you go to http://localhost/Reports/
> --my comment Failed to access IIS metabase.
> 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.Web.Hosting.HostingEnvironmentException:
> Failed to access IIS metabase.
> The process account used to run ASP.NET must have read access to the
> IIS metabase (e.g. IIS://servername/W3SVC). For information on
> modifying metabase permissions, please see
> http://support.microsoft.com/?kbid=267904 .
> 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:
> [HostingEnvironmentException: Failed to access IIS metabase.]
> System.Web.Hosting.HostingEnvironment.MapPathCaching(String path)
> +3609369 System.Web.CachedPathData.GetPathData(String path) +406
> System.Web.Configuration.RuntimeConfigLKG.GetInternalSection
> (String sectionName, Type type, ResultsIndex index) +134
>
> 2) The FIX
> To correct the problem To repair IIS mappings for ASP.NET, run the
> Aspnet_regiis.exe utlity. To do so, follow these steps:
> Click Start, and then click Run.
> Type cmd, and then click OK.
> At the command prompt, type the following command, and then press
> ENTER:
> "\<Windows folder>\Microsoft.NET\Framework\<Version
> Number>\aspnet_regiis.exe" -i
> NOTE:Replace <Windows folder> with the name of the directory where the
> operating system is installed and replace <Version Number> with the
> .NET Framework version installed on your computer. Or you could do a
> seach for the .exe file and locate the directory
> You can find the above reference at
> http://support.microsoft.com/default.aspx?scid=kb;en-us;325093
> Now try going to http://computername/reports/
> Hope it helps,
> Sharan Doddakashi
>
> LaurieT wrote:
> > Clint -- Thanks, I tried this and still got some errors (although different
> > than I was seeing before).
> >
> > I got this error when trying http://localhost:81/Reports
> >
> > "The XML page cannot be displayed
> > Cannot view XML input using XSL style sheet. Please correct the error and
> > then click the Refresh button, or try again later.
> >
> >
> > ----
> >
> > A name was started with an invalid character. Error processing resource
> > 'http://localhost:81/Reports'. Line 1, Position 2
> >
> > <%@. Page language="c#" Codebehind="Home.aspx.cs" AutoEventWireup="false"
> > Inherits="Microsoft.ReportingServices.UI.HomePag..."
> >
> > Any ideas?
> >
> > Thank you.
> > --
> > LaurieT
> >
> >
> > "Clint" wrote:
> >
> > > What happens when you try going to http://localhost/?
> > >
> > > Have you tried http://localhost:81/Reports, since that's what you changed
> > > the port to?
> > >
> > > Clint
> > >
> > > "LaurieT" <LaurieT@.discussions.microsoft.com> wrote in message
> > > news:75CE650E-D235-4DDC-9408-802E8AE9312A@.microsoft.com...
> > > >I just installed SQL Server 2005 (Reporting Services) on my collegues
> > > >laptop
> > > > (Windows XP, SP2) and when we try to deploy the reports we get the
> > > > message:
> > > > "A connection could not be made with report server at
> > > > http://localhost/ReportServer"
> > > >
> > > > Everything is running (green checks) in the Reporting Services
> > > > configuration
> > > > manager. We get the error, "Page not found." when we just try to open
> > > > http://<machinename>/Reports or http://localhost/Reports. I see the
> > > > virtual
> > > > directories in IIS, all services seem to be running correctly.
> > > >
> > > > Please help! I have installed reporting services about 10 times and have
> > > > not run into this problem before. The only issue that we had initially
> > > > was
> > > > that the IIS default web site would not run because there was a conflict
> > > > on
> > > > TCP Port 80, so I switched that TCP Port to port 81 -- this shouldn't be a
> > > > problem should it.
> > > >
> > > > Thank you,
> > > > Laurie
> > > > --
> > > > LaurieT
> > >
> > >
> > >

A connection could not be made to the report server

installed MS SQL 2005 Express Advanced (with Reporting services). I built a
sample report using the wizard. When i click on 'deploy' i get the error as
below. There is an application with virtual name as 'ReportServer' in the
IIS 5.1 . What could be the possible reasons for this error ?
Regards,
Chak.
:-
TITLE: Microsoft Report Designer
--
A connection could not be made to the report server
http://localhost/ReportServer.
--
ADDITIONAL INFORMATION:
The attempt to connect to the report server failed. Check your connection
information and that the report server is a compatible version.
(Microsoft.ReportingServices.Designer)
--
The request failed with HTTP status 404: Not Found.
(Microsoft.ReportingServices.Designer)
--
BUTTONS:
OK
--I re-installed the Reporting server after checking the 'Apply default
settings' check box. Now the report seems to be deployable.
Regards.
"Chakravarthy" <r_chakravarthy@.hotmail.com> wrote in message
news:OHGSa16uGHA.2224@.TK2MSFTNGP06.phx.gbl...
> installed MS SQL 2005 Express Advanced (with Reporting services). I built
> a sample report using the wizard. When i click on 'deploy' i get the error
> as below. There is an application with virtual name as 'ReportServer' in
> the IIS 5.1 . What could be the possible reasons for this error ?
> Regards,
> Chak.
> :-
>
> TITLE: Microsoft Report Designer
> --
> A connection could not be made to the report server
> http://localhost/ReportServer.
> --
> ADDITIONAL INFORMATION:
> The attempt to connect to the report server failed. Check your connection
> information and that the report server is a compatible version.
> (Microsoft.ReportingServices.Designer)
> --
> The request failed with HTTP status 404: Not Found.
> (Microsoft.ReportingServices.Designer)
> --
> BUTTONS:
> OK
> --
>

A connection could not be established LOGIN FAILURE

A connection could not be established TO MYSERVER [SQL SERVER]
LOGIN FAILURE

I have just installed sql server 6.5 on windows nt server 4.0, the sql server services are running with no problems.

Now When I open the sql enterprise manager and I try do something like right click in my default data base I got this error.

It's my 2nd time installing this...

Please, any help is welcome..

thanks for your time...

Quote:

Originally Posted by SQLnewbie

A connection could not be established TO MYSERVER [SQL SERVER]
LOGIN FAILURE

I have just installed sql server 6.5 on windows nt server 4.0, the sql server services are running with no problems.

Now When I open the sql enterprise manager and I try do something like right click in my default data base I got this error.

It's my 2nd time installing this...

Please, any help is welcome..

thanks for your time...

You have to remove the SQL from your computer then reinstall it again
Dont forget to name your server

sql

A complete uninstall of SQL 2005

I recently re-built my entire system from ground up (new hard drives, OS, etc). I now have the problem of SQL 2005 installed partially, but no way to get the management tools installed. I get an "already installed message when I try". I've never encounted this before on any other SQL install.

Sequence of events. I installed VS 2005 Pro first, then followed by SQL 2005. Somewhere this install didn't work, and I was left with the MS installed thinking I suceeded, yet none of the functions of SQL were worked or more importantly accessable.

I tried to re-install after using the ADD/Remove App from the control panel (which was sucessfull). SQL thought it was still installed. So I uninstalled VS 2005 as well, and deleted any programs in the SQL directory. Then I checked ADD/Remove programs and nothing was showing. The re-install still did not work. My guess is that the registry is still loaded with now useless entries.

Is there any solution left that does not require me to hand delete any SQL registry entries, since that is always a great way to completely kill my system.

Thanks.

Please send email to me and I will forward a script to clean those installed components.

99Gb log file...help

Hello. We have had a new Win 2003 SBS Server installed 2 months ago. All has
bee ok for the last 2 months but today I have noticed that the d: drive 120Gb
partition only has just under a Gb of space left. On further inspection I
have found a 99Gb log file (log.ldf) This is under MSSQL$SHAREPOINT\Data.
Sharepoint is not even used atm.
My question is why is there a log file this large and also how do I go about
clearing it. I have read about truncation etc but a file this large seems
that there maybe something else wrong. I am fairly new to SQL etc so sorry if
not enough info but any help would be much appreciated.
Regards,
Tom.
Look at this.
http://groups.google.ch/group/micros...157c86a71bf8f9
It has all got to do with the recovery setting and if you backup your log or
not.
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Tom P via droptable.com" wrote:

> Hello. We have had a new Win 2003 SBS Server installed 2 months ago. All has
> bee ok for the last 2 months but today I have noticed that the d: drive 120Gb
> partition only has just under a Gb of space left. On further inspection I
> have found a 99Gb log file (log.ldf) This is under MSSQL$SHAREPOINT\Data.
> Sharepoint is not even used atm.
> My question is why is there a log file this large and also how do I go about
> clearing it. I have read about truncation etc but a file this large seems
> that there maybe something else wrong. I am fairly new to SQL etc so sorry if
> not enough info but any help would be much appreciated.
> Regards,
> Tom.
>
|||Tom,
Sounds like the database is in full recovery mode and has never been backed
up. I would truncate the log. Shrink it to something reasonable... say
500Mb. Set the recovery model on the database to simple. And even though
you don't use it today, go ahead and use the maintenance wizard to configure
and automatic backup of the database at least once per week. All of these
tasks can be done through the Enterprise manager GUI.
"Tom P via droptable.com" <forum@.droptable.com> wrote in message
news:5262B70E980A0@.droptable.com...
> Hello. We have had a new Win 2003 SBS Server installed 2 months ago. All
> has
> bee ok for the last 2 months but today I have noticed that the d: drive
> 120Gb
> partition only has just under a Gb of space left. On further inspection I
> have found a 99Gb log file (log.ldf) This is under MSSQL$SHAREPOINT\Data.
> Sharepoint is not even used atm.
> My question is why is there a log file this large and also how do I go
> about
> clearing it. I have read about truncation etc but a file this large seems
> that there maybe something else wrong. I am fairly new to SQL etc so sorry
> if
> not enough info but any help would be much appreciated.
> Regards,
> Tom.
|||Sorted it...Shrunk the log down to 56Mb from 99Gb...Will set a maintenance
program too.
Thnaks for all the help.
Danny wrote:[vbcol=seagreen]
>Tom,
>Sounds like the database is in full recovery mode and has never been backed
>up. I would truncate the log. Shrink it to something reasonable... say
>500Mb. Set the recovery model on the database to simple. And even though
>you don't use it today, go ahead and use the maintenance wizard to configure
>and automatic backup of the database at least once per week. All of these
>tasks can be done through the Enterprise manager GUI.
>[quoted text clipped - 14 lines]

99Gb log file...help

Hello. We have had a new Win 2003 SBS Server installed 2 months ago. All has
bee ok for the last 2 months but today I have noticed that the d: drive 120Gb
partition only has just under a Gb of space left. On further inspection I
have found a 99Gb log file (log.ldf) This is under MSSQL$SHAREPOINT\Data.
Sharepoint is not even used atm.
My question is why is there a log file this large and also how do I go about
clearing it. I have read about truncation etc but a file this large seems
that there maybe something else wrong. I am fairly new to SQL etc so sorry if
not enough info but any help would be much appreciated.
Regards,
Tom.Tom,
Sounds like the database is in full recovery mode and has never been backed
up. I would truncate the log. Shrink it to something reasonable... say
500Mb. Set the recovery model on the database to simple. And even though
you don't use it today, go ahead and use the maintenance wizard to configure
and automatic backup of the database at least once per week. All of these
tasks can be done through the Enterprise manager GUI.
"Tom P via SQLMonster.com" <forum@.SQLMonster.com> wrote in message
news:5262B70E980A0@.SQLMonster.com...
> Hello. We have had a new Win 2003 SBS Server installed 2 months ago. All
> has
> bee ok for the last 2 months but today I have noticed that the d: drive
> 120Gb
> partition only has just under a Gb of space left. On further inspection I
> have found a 99Gb log file (log.ldf) This is under MSSQL$SHAREPOINT\Data.
> Sharepoint is not even used atm.
> My question is why is there a log file this large and also how do I go
> about
> clearing it. I have read about truncation etc but a file this large seems
> that there maybe something else wrong. I am fairly new to SQL etc so sorry
> if
> not enough info but any help would be much appreciated.
> Regards,
> Tom.|||Look at this.
http://groups.google.ch/group/microsoft.public.sqlserver.programming/browse_thread/thread/a1f9700d9b8177b5/77157c86a71bf8f9?lnk=st&q=sql+transaction+log+large&rnum=5&hl=en#77157c86a71bf8f9
It has all got to do with the recovery setting and if you backup your log or
not.
--
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Tom P via SQLMonster.com" wrote:
> Hello. We have had a new Win 2003 SBS Server installed 2 months ago. All has
> bee ok for the last 2 months but today I have noticed that the d: drive 120Gb
> partition only has just under a Gb of space left. On further inspection I
> have found a 99Gb log file (log.ldf) This is under MSSQL$SHAREPOINT\Data.
> Sharepoint is not even used atm.
> My question is why is there a log file this large and also how do I go about
> clearing it. I have read about truncation etc but a file this large seems
> that there maybe something else wrong. I am fairly new to SQL etc so sorry if
> not enough info but any help would be much appreciated.
> Regards,
> Tom.
>|||Sorted it...Shrunk the log down to 56Mb from 99Gb...Will set a maintenance
program too.
Thnaks for all the help.
Danny wrote:
>Tom,
>Sounds like the database is in full recovery mode and has never been backed
>up. I would truncate the log. Shrink it to something reasonable... say
>500Mb. Set the recovery model on the database to simple. And even though
>you don't use it today, go ahead and use the maintenance wizard to configure
>and automatic backup of the database at least once per week. All of these
>tasks can be done through the Enterprise manager GUI.
>> Hello. We have had a new Win 2003 SBS Server installed 2 months ago. All
>> has
>[quoted text clipped - 14 lines]
>> Tom.

99Gb log file...help

Hello. We have had a new Win 2003 SBS Server installed 2 months ago. All has
bee ok for the last 2 months but today I have noticed that the d: drive 120G
b
partition only has just under a Gb of space left. On further inspection I
have found a 99Gb log file (log.ldf) This is under MSSQL$SHAREPOINT\Data.
Sharepoint is not even used atm.
My question is why is there a log file this large and also how do I go about
clearing it. I have read about truncation etc but a file this large seems
that there maybe something else wrong. I am fairly new to SQL etc so sorry i
f
not enough info but any help would be much appreciated.
Regards,
Tom.Look at this.
http://groups.google.ch/group/micro...7157c86a71bf8f9
It has all got to do with the recovery setting and if you backup your log or
not.
--
--
Mike Epprecht, Microsoft SQL Server MVP
Zurich, Switzerland
MVP Program: http://www.microsoft.com/mvp
Blog: http://www.msmvps.com/epprecht/
"Tom P via droptable.com" wrote:

> Hello. We have had a new Win 2003 SBS Server installed 2 months ago. All h
as
> bee ok for the last 2 months but today I have noticed that the d: drive 12
0Gb
> partition only has just under a Gb of space left. On further inspection I
> have found a 99Gb log file (log.ldf) This is under MSSQL$SHAREPOINT\Data.
> Sharepoint is not even used atm.
> My question is why is there a log file this large and also how do I go abo
ut
> clearing it. I have read about truncation etc but a file this large seems
> that there maybe something else wrong. I am fairly new to SQL etc so sorry
if
> not enough info but any help would be much appreciated.
> Regards,
> Tom.
>|||Tom,
Sounds like the database is in full recovery mode and has never been backed
up. I would truncate the log. Shrink it to something reasonable... say
500Mb. Set the recovery model on the database to simple. And even though
you don't use it today, go ahead and use the maintenance wizard to configure
and automatic backup of the database at least once per week. All of these
tasks can be done through the Enterprise manager GUI.
"Tom P via droptable.com" <forum@.droptable.com> wrote in message
news:5262B70E980A0@.droptable.com...
> Hello. We have had a new Win 2003 SBS Server installed 2 months ago. All
> has
> bee ok for the last 2 months but today I have noticed that the d: drive
> 120Gb
> partition only has just under a Gb of space left. On further inspection I
> have found a 99Gb log file (log.ldf) This is under MSSQL$SHAREPOINT\Data.
> Sharepoint is not even used atm.
> My question is why is there a log file this large and also how do I go
> about
> clearing it. I have read about truncation etc but a file this large seems
> that there maybe something else wrong. I am fairly new to SQL etc so sorry
> if
> not enough info but any help would be much appreciated.
> Regards,
> Tom.|||Sorted it...Shrunk the log down to 56Mb from 99Gb...Will set a maintenance
program too.
Thnaks for all the help.
Danny wrote:[vbcol=seagreen]
>Tom,
>Sounds like the database is in full recovery mode and has never been backed
>up. I would truncate the log. Shrink it to something reasonable... say
>500Mb. Set the recovery model on the database to simple. And even though
>you don't use it today, go ahead and use the maintenance wizard to configur
e
>and automatic backup of the database at least once per week. All of these
>tasks can be done through the Enterprise manager GUI.
>
>[quoted text clipped - 14 lines]

911 Help! Why can't I get a functional version of SQL installed on my machine?

Hello Everyone, I am trying to install SQL 2005 on my machine. All I want is the functionality that I enjoyed with SQL 2000- Query Analyzer and Enterprise Manager. For some reason, the version of SQL 2005 that I am installing is only giving me an option for the Configuration Manger which does not provide access to the Management Console. It is my understanding that I need the Management Console to create databases, look at tables in my databases, etc., etc. just like I did in Enterprise Manager. Is there anyone who can tell me what I'm doing wrong? Currently, the cd that I have says SQL Developer Edition. Thanks.

You have to expressly install the client tools. The default installation only installs the server.|||EM is replaced by SQL Server Management Studio, just for the case you are wondering where the EM is installed :-)

Jens K. Suessmeyer.

http://www.sqlserver2005.de|||Hello, your answer was very enlightening and I was able to find the client tools you referenced...another question...did you ever have installation issues? Now, everytime I try and run the installation routine with the client tools, the installation errors out before completing the installation. Any thoughts?|||

A lot of folks experience various kinds of errors.

Please post the errors you are receiving so we can better help you.

|||

Feel free to post any setup related questions to the setup & upgrade forum and include any specific error messages you are seeing.

Thanks,
Sam Lester (MSFT)

8 GB of RAM installed

SQL Server 2000 Enterprise Edition machine running Windows 2000 Advanced Server. The server has 8 GB of RAM installed but for some reason SQL Server is only utilizing less than 4 GB. What would the likely cause be?
Three thoughts:
You are not using /3GB /PAE within the boot.ini
You have not configured SQL Server to with the "awe enabled" option (exec
sp_configure).
Memory usage is being restricted by min server memory (MB) and max server
memory (MB) (exec sp_configure).
Keith
"Serverdba" <Serverdba@.discussions.microsoft.com> wrote in message
news:A4DAD1E0-5C6A-49D4-8631-6DE54777B44B@.microsoft.com...
> SQL Server 2000 Enterprise Edition machine running Windows 2000 Advanced
Server. The server has 8 GB of RAM installed but for some reason SQL Server
is only utilizing less than 4 GB. What would the likely cause be?
|||Are you using the /3GB in your boot.ini? Look in books online under
"Managing AWE Memory."
-John Oakes
"Serverdba" <Serverdba@.discussions.microsoft.com> wrote in message
news:A4DAD1E0-5C6A-49D4-8631-6DE54777B44B@.microsoft.com...
> SQL Server 2000 Enterprise Edition machine running Windows 2000 Advanced
Server. The server has 8 GB of RAM installed but for some reason SQL Server
is only utilizing less than 4 GB. What would the likely cause be?
|||All those option is set. Still same problem
"John Oakes" wrote:

> Are you using the /3GB in your boot.ini? Look in books online under
> "Managing AWE Memory."
> -John Oakes
> "Serverdba" <Serverdba@.discussions.microsoft.com> wrote in message
> news:A4DAD1E0-5C6A-49D4-8631-6DE54777B44B@.microsoft.com...
> Server. The server has 8 GB of RAM installed but for some reason SQL Server
> is only utilizing less than 4 GB. What would the likely cause be?
>
>
|||Did you reboot after changing boot.ini?
-John Oakes
"Serverdba" <Serverdba@.discussions.microsoft.com> wrote in message
news:188FFB29-DDE5-42B3-A802-DC671FC7B68A@.microsoft.com...[vbcol=seagreen]
> All those option is set. Still same problem
> "John Oakes" wrote:
Advanced[vbcol=seagreen]
Server[vbcol=seagreen]
|||You also need the /PAE set in the Boot.ini.
Andrew J. Kelly SQL MVP
"Serverdba" <Serverdba@.discussions.microsoft.com> wrote in message
news:188FFB29-DDE5-42B3-A802-DC671FC7B68A@.microsoft.com...[vbcol=seagreen]
> All those option is set. Still same problem
> "John Oakes" wrote:
Advanced[vbcol=seagreen]
Server[vbcol=seagreen]
|||Serverdba wrote:

> SQL Server 2000 Enterprise Edition machine running Windows 2000 Advanced Server. The server has 8 GB of RAM installed but for some reason SQL Server is only utilizing less than 4 GB. What would the likely cause be?
Hi,
The Account which starts the SQL Service must have the privilege "lock
pages in memory" - you can set this in the local policy settings

8 GB of RAM installed

SQL Server 2000 Enterprise Edition machine running Windows 2000 Advanced Ser
ver. The server has 8 GB of RAM installed but for some reason SQL Server is
only utilizing less than 4 GB. What would the likely cause be?Three thoughts:
You are not using /3GB /PAE within the boot.ini
You have not configured SQL Server to with the "awe enabled" option (exec
sp_configure).
Memory usage is being restricted by min server memory (MB) and max server
memory (MB) (exec sp_configure).
Keith
"Serverdba" <Serverdba@.discussions.microsoft.com> wrote in message
news:A4DAD1E0-5C6A-49D4-8631-6DE54777B44B@.microsoft.com...
> SQL Server 2000 Enterprise Edition machine running Windows 2000 Advanced
Server. The server has 8 GB of RAM installed but for some reason SQL Server
is only utilizing less than 4 GB. What would the likely cause be?|||Are you using the /3GB in your boot.ini? Look in books online under
"Managing AWE Memory."
-John Oakes
"Serverdba" <Serverdba@.discussions.microsoft.com> wrote in message
news:A4DAD1E0-5C6A-49D4-8631-6DE54777B44B@.microsoft.com...
> SQL Server 2000 Enterprise Edition machine running Windows 2000 Advanced
Server. The server has 8 GB of RAM installed but for some reason SQL Server
is only utilizing less than 4 GB. What would the likely cause be?|||All those option is set. Still same problem
"John Oakes" wrote:

> Are you using the /3GB in your boot.ini? Look in books online under
> "Managing AWE Memory."
> -John Oakes
> "Serverdba" <Serverdba@.discussions.microsoft.com> wrote in message
> news:A4DAD1E0-5C6A-49D4-8631-6DE54777B44B@.microsoft.com...
> Server. The server has 8 GB of RAM installed but for some reason SQL Serve
r
> is only utilizing less than 4 GB. What would the likely cause be?
>
>|||Did you reboot after changing boot.ini?
-John Oakes
"Serverdba" <Serverdba@.discussions.microsoft.com> wrote in message
news:188FFB29-DDE5-42B3-A802-DC671FC7B68A@.microsoft.com...[vbcol=seagreen]
> All those option is set. Still same problem
> "John Oakes" wrote:
>
Advanced[vbcol=seagreen]
Server[vbcol=seagreen]|||You also need the /PAE set in the Boot.ini.
Andrew J. Kelly SQL MVP
"Serverdba" <Serverdba@.discussions.microsoft.com> wrote in message
news:188FFB29-DDE5-42B3-A802-DC671FC7B68A@.microsoft.com...[vbcol=seagreen]
> All those option is set. Still same problem
> "John Oakes" wrote:
>
Advanced[vbcol=seagreen]
Server[vbcol=seagreen]|||Serverdba wrote:

> SQL Server 2000 Enterprise Edition machine running Windows 2000 Advanced Server. T
he server has 8 GB of RAM installed but for some reason SQL Server is only utilizing
less than 4 GB. What would the likely cause be?
Hi,
The Account which starts the SQL Service must have the privilege "lock
pages in memory" - you can set this in the local policy settings

701 error

We are experiencing the same errors and same "lock out" behavior. We have the same version/patch level of SQL installed but are in a 32 bit env. The box has 32GB of memory. Nether the bPool or VAS show any pressure when the "out of system memory error" occurs. Since this error usually indicates a VAS problem we tried increasing VAS to 1GB w/the -g flag. It made no difference. PSS has been working on the case for 3 weeks. They dont seem to be finding any evidince of memory pressure either. When I last spole to the escalation engineer yesterday it seemed that they are going to recommend reducing the number of databases on the server. I asked for clarification as to whether we are hitting a 32 bit barrior, an instance limitation, or both. I am awaiting the answer. How many databases do you have on your server? We had between 1700 and 1900 (the number varies) at times when the error occured. We are now at 1500, and have not had the error in the 2 days since reducing the number of databases...
EggHeadCafe.com - .NET Developer Portal of Choice
http://www.eggheadcafe.com
Steve,
Further comment.
I have been having the problem about once a month for several months and
have not had any joy in discovering what to do about it. Other notes on my
case:
- Once this starts, my CPU utilization will go to very close to 100%. If I
log out some heavy users, my CPU will dip to 70% or 80% for about 20
seconds, then climb back to near 100%.
- At this point, spid 1 is the busiest of the spids. (Which makes it seem
that the SQL Server is eating up its resources trying to find resources for
users.)
- Very Strange Discovery. One time I found that one workstation which had
been running a very large transaction, would, if turned off, drop the server
CPU to normal. But if I turned that workstation back on, even though I did
not access the server, the server workload would go back to 100%. It was as
if the SQL Server remembered the workstation and would try to do something
for it. (The next day this workstation did not have such an effect.) As I
said, Very Strange.
We also are on 32-bit using AWE memory, but only 12 GB. (We also only have
about 60 databases on the machine, nothing like your 1500+.) This weekend,
we are upgrading to 64-bit Windows 2003/SQL Server 2005. We will see if
this recurs, or whether it is an AWE flaw.
This thread from a Red Gate user suggests the problem is not free memory,
but free contiguous memory.
[url]http://www.red-gate.com/MessageBoard/viewtopic.php?p=15220&sid=9c1df0b8ddef4fc6745b1ce1 33f1e6b1[/url]
So, if very large queries and cursor usage are responsible for fragmenting
memory (per something I read elsewhere) I don't know what to do except to
schedule periodic restarts of the the SQL Server.
RLF
<steve> wrote in message news:200722311948sgoodwin@.autotask.com...
> We are experiencing the same errors and same "lock out" behavior. We have
> the same version/patch level of SQL installed but are in a 32 bit env. The
> box has 32GB of memory. Nether the bPool or VAS show any pressure when the
> "out of system memory error" occurs. Since this error usually indicates a
> VAS problem we tried increasing VAS to 1GB w/the -g flag. It made no
> difference. PSS has been working on the case for 3 weeks. They dont seem
> to be finding any evidince of memory pressure either. When I last spole to
> the escalation engineer yesterday it seemed that they are going to
> recommend reducing the number of databases on the server. I asked for
> clarification as to whether we are hitting a 32 bit barrior, an instance
> limitation, or both. I am awaiting the answer. How many databases do you
> have on your server? We had between 1700 and 1900 (the number varies) at
> times when the error occured. We are now at 1500, and have not had the
> error in the 2 days since reducing the number of databases...
> EggHeadCafe.com - .NET Developer Portal of Choice
> http://www.eggheadcafe.com

701 error

We are experiencing the same errors and same "lock out" behavior. We have th
e same version/patch level of SQL installed but are in a 32 bit env. The box
has 32GB of memory. Nether the bPool or VAS show any pressure when the "out
of system memory error" oc
curs. Since this error usually indicates a VAS problem we tried increasing V
AS to 1GB w/the -g flag. It made no difference. PSS has been working on the
case for 3 weeks. They dont seem to be finding any evidince of memory pressu
re either. When I last spol
e to the escalation engineer yesterday it seemed that they are going to reco
mmend reducing the number of databases on the server. I asked for clarificat
ion as to whether we are hitting a 32 bit barrior, an instance limitation, o
r both. I am awaiting the a
nswer. How many databases do you have on your server? We had between 1700 an
d 1900 (the number varies) at times when the error occured. We are now at 15
00, and have not had the error in the 2 days since reducing the number of da
tabases...
EggHeadCafe.com - .NET Developer Portal of Choice
http://www.eggheadcafe.comSteve,
Further comment.
I have been having the problem about once a month for several months and
have not had any joy in discovering what to do about it. Other notes on my
case:
- Once this starts, my CPU utilization will go to very close to 100%. If I
log out some heavy users, my CPU will dip to 70% or 80% for about 20
seconds, then climb back to near 100%.
- At this point, spid 1 is the busiest of the spids. (Which makes it seem
that the SQL Server is eating up its resources trying to find resources for
users.)
- Very Strange Discovery. One time I found that one workstation which had
been running a very large transaction, would, if turned off, drop the server
CPU to normal. But if I turned that workstation back on, even though I did
not access the server, the server workload would go back to 100%. It was as
if the SQL Server remembered the workstation and would try to do something
for it. (The next day this workstation did not have such an effect.) As I
said, Very Strange.
We also are on 32-bit using AWE memory, but only 12 GB. (We also only have
about 60 databases on the machine, nothing like your 1500+.) This weekend,
we are upgrading to 64-bit Windows 2003/SQL Server 2005. We will see if
this recurs, or whether it is an AWE flaw.
This thread from a Red Gate user suggests the problem is not free memory,
but free contiguous memory.
http://www.red-gate.com/MessageBoar...
b1ce133f1e6b1
So, if very large queries and cursor usage are responsible for fragmenting
memory (per something I read elsewhere) I don't know what to do except to
schedule periodic restarts of the the SQL Server.
RLF
<steve> wrote in message news:200722311948sgoodwin@.autotask.com...
> We are experiencing the same errors and same "lock out" behavior. We have
> the same version/patch level of SQL installed but are in a 32 bit env. The
> box has 32GB of memory. Nether the bPool or VAS show any pressure when the
> "out of system memory error" occurs. Since this error usually indicates a
> VAS problem we tried increasing VAS to 1GB w/the -g flag. It made no
> difference. PSS has been working on the case for 3 weeks. They dont seem
> to be finding any evidince of memory pressure either. When I last spole to
> the escalation engineer yesterday it seemed that they are going to
> recommend reducing the number of databases on the server. I asked for
> clarification as to whether we are hitting a 32 bit barrior, an instance
> limitation, or both. I am awaiting the answer. How many databases do you
> have on your server? We had between 1700 and 1900 (the number varies) at
> times when the error occured. We are now at 1500, and have not had the
> error in the 2 days since reducing the number of databases...
> EggHeadCafe.com - .NET Developer Portal of Choice
> http://www.eggheadcafe.com

64-bit SQL2000 on 32-bit OS

Will my SQL server work like 32-bit or 64-bit if I installed 64bit SQL2000 E
E on 32-bit Windows 2003 Enterprise server?Please do not multi-post. You cannot install a 64-bit app on a 32-bit
server.
Tom
---
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Columnist, SQL Server Professional
Toronto, ON Canada
www.pinnaclepublishing.com/sql
"Dipesh" <anonymous@.discussions.microsoft.com> wrote in message
news:B3C23FBD-BE47-4F5E-B464-905A1B94000A@.microsoft.com...
Will my SQL server work like 32-bit or 64-bit if I installed 64bit SQL2000
EE on 32-bit Windows 2003 Enterprise server?|||It will work like a rock. It will sit there and do nothing.
To run 64-bit, you need 64-bit hardware, 64-bit OS, and 64-bit applications.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Dipesh" <anonymous@.discussions.microsoft.com> wrote in message
news:B3C23FBD-BE47-4F5E-B464-905A1B94000A@.microsoft.com...
> Will my SQL server work like 32-bit or 64-bit if I installed 64bit SQL2000
EE on 32-bit Windows 2003 Enterprise server?
>

64-bit SQL Server 2005 Installation (Reporting Services)

Hi,

Trying to install 64-bit SQL Server 2005 RTM on Windows 2003 x64 Server. The Reporting services is not getting installed or the option is disabled. The server does have IIS installed, the .NET framework 2.0 is installed by SQL Server 2005 RTM itself. The server also has SQL Server 2000 (32bit).

Is the 32-bit SQL Server 2000 (32 bit) a problem ? But, it was working fine with the SQL Server 2005 CTP.

Can anyone help/suggest ?

Thanks in advance.remove other reporting services from your machine. and try again

64bit Server 32bit Client

I installed SQL 2005 on a 64bit server. Can I still use enterprise studio on a 32bit client machine?

The install CD's are 64bit and when I try to find the enterprise studio to install on my 32bit machine i get an error. Is there a place to download the 32bit enterprise studio? What are my options here?

Thanks in advance.

Mike

32 bit tools can happily talk to a 64 bit server.

64-Bit Installation of SQL Server 2005 on AMD Server

I have an 8-Processor AMD CPU box with Windows Server 2003 Enterprise (x64) R2 with SP1 installed.

How do I verify that I am installing the 64-Bit version of SQL Server 2005? I don't see any installer 'options' and when I view the list of SQL Server 2005 components in the Add/Remove program list there is nothing mentioned.

The source of my SQL Server 2005 installation code is the 'Ready Set Launch' DVD that Microsoft handed out when SQL Server 2005 was launched in 11/2005.

I haven't found any documentation to specifically details 64-bit installations.

Thank you.

...cordell...

The media itself must be the 64-bit version of SQL 2005. Since your AMD box will support both 32-bit and 64-bit versions, it's tough to tell what you're installing. After installing, the 64-bit versions have a "(64-bit)" tag on the end of them in Add/Remove Programs. My guess is that you have a copy of the 32-bit version.

Thanks,
Sam Lester (MSFT)

|||

Sam...

From what I can see I am installing the 32-bit versions of the SQL Server 2005 software on the AMD box.

I apologize for being pedantic here.....but I wanted to confirm that I will need to follow back up with my software vendor and order a 64-bit version of SQL Server 2005. (This is what I am concluding from your statements.)

After searching around the SKU I have is 228-05237 for this version...but I couldn't find anything in the SQL Server section of the MS website to confirm it. While I realize you are not in sales...what would the URL be for confirming the SKU on the media.

Thank you.

...cordell...

|||

No problem at all. You will need to contact your software vendor and specifically request the 64-bit version. I don't fully understand the licensing options for every situation, but I think this page will help you find the SKU/item number you are looking for. I have linked the Enterprise SKU's, but you can search for the others as well.

http://www.microsoft.com/PRODUCTS/info/product.aspx?view=22&pcid=d635228e-6aed-404b-9af1-7c27819c24e4&crumb=srch&qu=sql+server&gpid=c419977d-7963-4c38-8caf-95d3f779bed1

Example (make sure you pick the one that applies to you):

Full Version
Microsoft? SQL Server Enterprise Edition 2005 x64 English CD/DVD 25 Client
Item: 810-05188

Let me know if this is what you're looking for.

Thanks,
Sam

|||

Thank you Sam for the confirmation and assistance. That is what I was looking for.

...cordell...

64 bit ODBC Datasource

Hello together
I'm running Reporting Services on a 64 bit Windows 2003 R2 machine. I've
installed the MyOdbc 3.51 Drivers for MySql which I would like to use as the
Datasource for my reports. I configured and tested the ODBC connection
successfully using the odbcad32.exe in the windows\syswow64 folder.
But when I deploy a report which I designed on my 32 bit development machine
where all is running correctly, and I run the report on the server, it
cannot find the datasource.
I think it has the same reason why I cannot see the MyODBC driver in the
normal ODBC Configuration Manager in the Administrative Tools.
Is there a possiblity to do that anyway'
Thank you and greetings from Switzerland
ThomasHi Thomas,
Did you get a response to this question? I'm not using MySQL, but
I've spent most of today chasing this exact problem. I can tell you
that hacking the registry doesn't work, but I'd really like to know if
you heard from someone that had solved it, or if you found the answer
yourself.
Thanks in advance.
Dan
Thomas Bolt wrote:
> Hello together
> I'm running Reporting Services on a 64 bit Windows 2003 R2 machine. I've
> installed the MyOdbc 3.51 Drivers for MySql which I would like to use as the
> Datasource for my reports. I configured and tested the ODBC connection
> successfully using the odbcad32.exe in the windows\syswow64 folder.
> But when I deploy a report which I designed on my 32 bit development machine
> where all is running correctly, and I run the report on the server, it
> cannot find the datasource.
> I think it has the same reason why I cannot see the MyODBC driver in the
> normal ODBC Configuration Manager in the Administrative Tools.
> Is there a possiblity to do that anyway'
> Thank you and greetings from Switzerland
> Thomas|||Hi Dan,
Did you get anywhere with this? I'm in exactly the same position that you
were in August!
Any help would be very much appreciated.
Rob
"barnetted@.michigan.gov" wrote:
> Hi Thomas,
> Did you get a response to this question? I'm not using MySQL, but
> I've spent most of today chasing this exact problem. I can tell you
> that hacking the registry doesn't work, but I'd really like to know if
> you heard from someone that had solved it, or if you found the answer
> yourself.
> Thanks in advance.
> Dan
> Thomas Bolt wrote:
> > Hello together
> >
> > I'm running Reporting Services on a 64 bit Windows 2003 R2 machine. I've
> > installed the MyOdbc 3.51 Drivers for MySql which I would like to use as the
> > Datasource for my reports. I configured and tested the ODBC connection
> > successfully using the odbcad32.exe in the windows\syswow64 folder.
> > But when I deploy a report which I designed on my 32 bit development machine
> > where all is running correctly, and I run the report on the server, it
> > cannot find the datasource.
> >
> > I think it has the same reason why I cannot see the MyODBC driver in the
> > normal ODBC Configuration Manager in the Administrative Tools.
> > Is there a possiblity to do that anyway'
> >
> > Thank you and greetings from Switzerland
> > Thomas
>