Showing posts with label connection. Show all posts

Tuesday, March 27, 2012

A Different Login failed for user sa problem

Hello,

I know there are already topics on the "Login failed for user 'sa'. Reason: Not associated with a trusted SQL Server connection" problem but I think this one might be different.

I am working with 2 servers, both running Windows Server 2003 with 1 running SQL Server 2000 and the other acting as a Web Server, and a PC running Windows XP Pro as a development machine - all of which are on the same domain.

I am developing a couple of ASP.NET web applications, and this is where the problem occurs. If I try to connect to the SQL database with the web application running on the development PC I get the "Login failed for user 'sa'. Reason: Not associated with a trusted SQL Server connection" error message.

This is where it gets interesting. If I take a copy of the code that is running on the development PC and run it on the Web Server, it is able to connect to the SQL database without any problems.

The Authentication mode is set to SQL Server and Windows. I have tried several different things with our Techs and we get the same problem.

Any ideas or suggestions would be greatly appreciated as we are totally stumped.

Thanks,
AlHowdy

Never, ever, ever, ever has NT authentication on SQL been bullet proof...then mix that with multiple versions of VB & SQL & W2K & W2K3 and....aw man...game over.....

Worth trying using plain SQL authentication ( if thats acceptible in your environment ) and see how that goes - at least it will get your app working initially. Then work on the NT authentication bit.

You may wind up having to wait for the next SP for everything if its a bug.

Cheers,

SG.|||All I am using at the moment is SQL authentication and I have absolutely no interest in using NT or Windows Authentication.

Thanks anyway,
Al|||Howdy,

Sounds like connection thinks it is using a trusted connection...can you force it to be sure its using straight SQL authentication? I have seen similar errors with sql configured apps trying to use ODBC connections configured fro NT authentication.

HTH

Cheers,

SG|||Go to the enterprise manager, right click on the server, in the properties, select security tab and select the first option(SQL Server and Windows NT) in the Authentication.

Now try connecting from your application.

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.

Exception Details:System.Data.SqlClient.SqlException: Procédure stockée 'dbo.aspnet_CheckSchemaVersion' introuvable.

Source Error:

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

Sunday, March 25, 2012

A couple of questions on Remote connection to SQL Server 2005 database

I have a SQL Server 2005 database (called BDHSE) in a PC which i call PC1. I have a second PC (PC2) and both are within a network (a WLAN).

What i want is to have access to BDHSE from an application in VB6 (APP1) running in PC2. All the INSERT, DELETE, UPDATE records process is done through APP1.

APP1 ia currently running in PC1 and is to be installed on PC2.

I have these questions:

1. What do i need to install in PC2 since all the INSERT, DELETE, and UPDATE is done using APP1? I guess i only have to install the Microsoft SQL Native Client (with all the prerequisites of course) but i am not sure.

2. In the APP1 made in VB6, do i have to change the connectionstring since i am accesing the database which physically is at PC1 and the APP1 will be used in PC2?

3. Any advice you can give me on doing this will be well received.

Thanks in advance,

BSc Fernando Martinez

1. If you do not want to use any new features of the SQL Server 2k5, you can also install the MDAC stack. You don′t need to install the SNAC drivers. If you install the SNAC drivers and want to use them, make sure that you change your connectionstring (samles can be found on the site www.connectionstrings.com).

2. I don′t get your throught here, but you will have to point the connectionstring of the application to the server where the database is actually hosted.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de|||thanks, i found out the problem.

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

Hi All,

When i'm trying to access a sql server from a different pc,i'm getting the following error..

Plz help me how to fix this..

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

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=64&LinkId=20476

Server Name: 10.11.144.145
Error Number: 64
Severity: 20
State: 0

Program Location:

at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParserStateObject.ReadSniError(TdsParserStateObject stateObj, UInt32 error)
at System.Data.SqlClient.TdsParserStateObject.ReadSni(DbAsyncResult asyncResult, TdsParserStateObject stateObj)
at System.Data.SqlClient.TdsParserStateObject.ReadPacket(Int32 bytesExpected)
at System.Data.SqlClient.TdsParserStateObject.ReadBuffer()
at System.Data.SqlClient.TdsParserStateObject.ReadByte()
at System.Data.SqlClient.TdsParser.Run(RunBehavior runBehavior, SqlCommand cmdHandler, SqlDataReader dataStream, BulkCopySimpleResultSet bulkCopyHandler, TdsParserStateObject stateObj)
at System.Data.SqlClient.SqlInternalConnectionTds.CompleteLogin(Boolean enlistOK)
at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject)
at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart)
at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup)
at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
at System.Data.SqlClient.SqlConnection.Open()
at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplorer.ValidateConnection(UIConnectionInfo ci, IServerType server)
at Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()

Regards,

Sailendra.

Hi ,

This problem generally occurs in windows 2003 server with service pack 1.

Solution is :-

Steps

1. regedit

2. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\\Parameters

3. Add Dword value with name “SynAttackProtect” and set value “00000000 “in hexdecimal.

Regards
Rajesh

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 during the

Hi All,

When i'm trying to access a sql server from a different pc,i'm getting the following error..

Plz help me how to fix this..

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=64&LinkId=20476

Server Name: 10.11.144.145
Error Number: 64
Severity: 20
State: 0

Program Location:

Regards,

Sailendra.

Hi ,

This problem generally occurs in windows 2003 server with service pack 1.

Solution is :-

Steps

1. regedit

2. HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\\Parameters

3. Add Dword value with name “SynAttackProtect” and set value “00000000 “in hexdecimal.

Regards
Rajeshsql

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

I get the following error when trying to view my page.

Can someone please help me with this error. What does it mean and what is the solution to it? Here is the complete error message. -

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.)

See following post:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=962333&SiteID=1

HTH

Ming.

|||

Please check these two posts see whether it solves your problem

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=597008&SiteID=1
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=354716&SiteID=1

Otherwise, please check your errorlog file see if there is any abnormal.

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

I get the following error when trying to view my page.

Can someone please help me with this error. What does it mean and what is the solution to it? Here is the complete error message. -

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.)

See following post:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=962333&SiteID=1

HTH

Ming.

|||

Please check these two posts see whether it solves your problem

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=597008&SiteID=1
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=354716&SiteID=1

Otherwise, please check your errorlog file see if there is any abnormal.

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!!!

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 to the report server failed

Hello,

I am getting extremely frustrated with this situation. I have two machines that are both connected to the domain and I am logged into both. I also have a W2K3 Server that is hosting SQL Server 2005 Standard. Both desktop machines have SSMS and all machines including server are now SP1. On one machine I can connect to reporting services just fine, but on the other I am getting the following error:

TITLE: Connect to Server
Cannot connect to MEDUSA.

ADDITIONAL INFORMATION:
A connection to the report server failed. Most likely, you do not have permission to connect to the computer. You should either try to connect using report server URL for the Server name, or if the Distributed COM Users group exists on the remote computer, verify that you are a member. (Microsoft.SqlServer.Management.UI.RSClient)

Now I can use the machine that cannot connect to this particular server and connect to my other machine just fine and vice versa. I am also having to enter login information each time I am trying to deploy new reports, which wasn't the case before. This happened out of the blue and I have not been able to find a reason for it. I can't connect through using the url either it gives me a 401 unauthorized error. I need to find an answer to this as soon as possible as this is causing me a multitude of issues. I hope someone can help me....thanks in advanced!

For those who are interested the solution is that your profile is corrupt. I tried everything I possibly could until I created a new profile on the machine I was having troubles connecting with. As soon as I did this it worked fine. Something must get funky with the authentication and somehow that is tied to the profile.|||

I was also having the problem of connecting from my xp machine sql management studio to a win2k3 reporting services 2005 and was getting

"can not connect to Report server from SQL SERVER 2005 Management studio error" although if a term served into another machine it would connect just fine and I am a domain admin.

In the end I found and removed the server from my user accounts. At some point i must have added the server to my user accounts under a different name for testing and it was connecting using that account instead of my login account.

Just another place to look if you are having problems connecting.

Hope this helps!!

A connection to the report server failed

Hello,

TITLE: Connect to Server
Cannot connect to MEDUSA.

ADDITIONAL INFORMATION:
A connection to the report server failed. Most likely, you do not have permission to connect to the computer. You should either try to connect using report server URL for the Server name, or if the Distributed COM Users group exists on the remote computer, verify that you are a member. (Microsoft.SqlServer.Management.UI.RSClient)

I was also having the problem of connecting from my xp machine sql management studio to a win2k3 reporting services 2005 and was getting

"can not connect to Report server from SQL SERVER 2005 Management studio error" although if a term served into another machine it would connect just fine and I am a domain admin.

Just another place to look if you are having problems connecting.

Hope this helps!!

sql

A connection remains open after calling Disconnect

Hi,

I would like to be able to connect to a SQL Server using SMO and then reconnect using a different login username and password.

In the following sample code I call svr.ConnectionContext.Disconnect. After the Disconnect call an attempt to change the timeout or any Login properties gives error:

Connection properties cannot be changed after connection has been made

Regards,

Joginder Nahil
www.starprint2000.com

Dim objServer As Server
objServer = New Server()
With objServer.ConnectionContext
.NonPooledConnection = True
.ConnectTimeout = 30
.LoginSecure = True
.Connect()

MsgBox("Connected. Database : " & objServer.Databases(0).Name)

.Disconnect()

' The following line gives error: Connection properties cannot be changed after connection has been made
.ConnectTimeout = 60
.LoginSecure = False
.Login="me"
.Password="pppp"

.Connect()
End With

Hi,

I have found a solution. You have to set the server object to nothing before the ConnectionContext is released and can be re-used as shown below:

Regards,
Joginder Nahil
www.starprint2000.com

Dim objServer As Server
objServer = New Server()

With objServer.ConnectionContext
.NonPooledConnection = True
.ConnectTimeout = 30
.LoginSecure = True
.Connect()

MsgBox("Connected. Database : " & objServer.Databases(0).Name)
.Disconnect()
End With

' Release the Server object only then the Connection is released
objServer= Nothing
objServer = New Server

With objServer.ConnectionContext
.ConnectTimeout = 60
.LoginSecure = False
.Login="me"
.Password="pppp"
.Connect()
End With

a connection error

Hi,
I have an error on my Application Server, it uses
analysis services and a SQL Server databases.
When I try to obtain information from the OLAP databases
it send me the next error:
Error Type:
ADODB.Connection(0x800A0E7A)
Provider cannot be found, It may not be properly
installed
Do you help me?
ThanksCheck to make sure you have MDAC installed properly on your app server

A connection could not be made with report server at https://webse

Hi,
My report server and report manager was working fine till yesterday. But
suddenly today when i tried to deploy a report i got error: "A connection
could not be made with report server at https://webserver1/ReportServer "
So when i tried to browse the report manager from IIS, I get error:"Could
not establish trust relationship with remote server."
I think its someting to do with SSL. Please help me with that 'czo out of
the blue today I have started getting this error.
--
pmudLook in the event log at the server machine for SSL errors.
Regards,
Martin

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 with report server

I am new in SQL Server 2005. I am practicing report services and I got
following error:
"A connection could not be made with report server at
https://localhost/ReportServer "
Can anyone help?
DarrenIs SSL set up for the ReportServer virtual directory? What happens
when you connect to http://localhost/reportserver? What happens when
you navigate to http://<machinename>/ReportServer?
Andy Pottersql

A connection could not be made to the reporting server http://localhost/reportserver

Hi all,

When I build a simple project using the report wizard project.

When i deploy the report i get the following error.

TITLE: Microsoft Report Designer

A connection could not be made to the report server http://localhost/ReportServer.

ADDITIONAL INFORMATION:

Client found response content type of 'text/html; charset=utf-8', but expected 'text/xml'.
The request failed with the error message:
--
<?xml version="1.0" ?>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN" "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" >
<head>
<title>Server Unavailable
</title>
</head>
<body>
<h1><span style="font-family:Verdana;color: #ff3300">Server Application Unavailable
</span></h1>

<span style="font-family:Verdana;">
The web application you are attempting to access on this web server is currently unavailable. Please hit the "Refresh" button in your web browser to retry your request.
</span>

<b>Administrator Note:
</b> An error message detailing the cause of this specific request failure can be found in the application event log of the web server. Please review this log entry to discover what caused this error to occur.

</body>
</html>

--. (Microsoft.ReportingServices.Designer)

BUTTONS:

Could some one come to my rescue.

Thanx in advance.

Ronald

Is Reporting services installed on the machine you are designing on? If not, go to the project properties and change the report server url to the machine where Report Server is installed on.|||

I'm getting the exact same error, but I'm working off of the same machine. To clarify, SQL and MS Visual Studio are on the same machine -- I've created the report and tried to deploy in MSVS.

Note that this machine is part of a network governed by a file & print server.

I can get a valid web page at http://localhost that changes to http://localhost/default.aspx and displays a Home page to a Team Web Site.

But when I try http://lolcalhost/reportsserver, I get the following errors:

Server Error in '/ReportServer' Application.

Configuration Error

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

Parser Error Message: Could not load file or assembly 'Microsoft.BusinessFramework' or one of its dependencies. The system cannot find the file specified. (c:\inetpub\wwwroot\web.config line 77)

Source Error:

Line 75: <add name="WindowsAuthentication" type="System.Web.Security.WindowsAuthenticationModule" /> Line 76:  Line 77: <add name="EnterpriseInitializationModule" type="Microsoft.BusinessFramework.Security.EnterpriseInitializationModule,Microsoft.BusinessFramework" /> Line 78: <add name="BPAdminRedirectModule" type="Microsoft.BusinessFramework.Portal.Administration.BPAdminRedirectModule,Microsoft.BusinessFramework.Portal" /> Line 79: <add name="BPHomeRedirectModule" type="Microsoft.BusinessFramework.Portal.Shell.BPHomeRedirectModule,Microsoft.BusinessFramework.Portal" />

Source File: c:\inetpub\wwwroot\web.config Line: 77

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

Can you help?

A connection could not be made to the reporting server http://localhost/reportserver

Hi all,

When I build a simple project using the report wizard project.

When i deploy the report i get the following error.

TITLE: Microsoft Report Designer

A connection could not be made to the report server http://localhost/ReportServer.

ADDITIONAL INFORMATION:

</body>
</html>

--. (Microsoft.ReportingServices.Designer)

BUTTONS:

Could some one come to my rescue.

Thanx in advance.

Ronald

Is Reporting services installed on the machine you are designing on? If not, go to the project properties and change the report server url to the machine where Report Server is installed on.

A connection could not be made to the report server http://localhost/reportServer..

hi,

I got this error when I was trying to deploy the reporting into IIS..

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)

I am not able to solve it please help.

Thanks.

Are you able to browse to http://localhost/reportServer using IE?|||

No,

I am not able to browse to http://localhost/reportServer using IE The page cannot be found is shown I have mentioned the error above that I got when I am trying to deploy the reporting into IIS..

Thanks

|||

Then that means that either your virtual directories have been created with a different name (not the default) or have not been created at all.

Have you run the reporting services confirguration tool?

|||

Raina - I was having the exact same problem and eventually resolved it this way:

I discovered that the Reporting Services Configuration Manager was incorrectly showing green check-marks indicating my Report Server and Report Manager Virtual Directories were set up, when in fact they were not (what tipped me off to this is when I went to Control Panel -> Administrative Tools -> Internet Information Services, there were no Report Server or Reports folder branches under my Default Web Site tree). So in the Reporting Services Configuration Manager, I clicked the New button to create the default Report Server and Report Manager Virtual Directories ((this was the 2nd time I did this, which may have been necessary because I uninstalled and reinstalled IIS after instaling SSRS). This time the IIS manager showed Report Server and Reports folder branches under my Default Web Site tree, and I was able to successfully browse to http://localhost/reportserver, AND deploy my SSRS project to the web server. Note that I am running a named instance of SQL Server 2005 (the default instance is SQL Server 2000), and even though I have seen posts suggesting the correct URL for a named instance would be http://localhost/reportserver$<named_instance>, this did NOT work for me ... http://localhost/reportserver DOES work.

|||

jbrauer wrote:
Note that I am running a named instance of SQL Server 2005 (the default instance is SQL Server 2000), and even though I have seen posts suggesting the correct URL for a named instance would be http://localhost/reportserver$<named_instance>, this did NOT work for me ... http://localhost/reportserver DOES work.

Well I have to disagree. I am also running a named instance, so the URL that works for me is
http://localhost/reportserver$<named_instance

When you create a new report model project its deploy URL by default is http://localhost/reportserver So i had to change that , through project properties, to the named instance one.

Good Luck !!|||Yes jbrauer, this was exactly the solution for me too, thankyou.

A connection could not be made to the report server http://localhost/reportServer..

hi,

I got this error when I was trying to deploy the reporting into IIS..

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)

I am not able to solve it please help.

Thanks.

Are you able to browse to http://localhost/reportServer using IE?|||

No,

Thanks

|||

Then that means that either your virtual directories have been created with a different name (not the default) or have not been created at all.

Have you run the reporting services confirguration tool?

|||

Raina - I was having the exact same problem and eventually resolved it this way:

|||

jbrauer wrote:
Note that I am running a named instance of SQL Server 2005 (the default instance is SQL Server 2000), and even though I have seen posts suggesting the correct URL for a named instance would be http://localhost/reportserver$<named_instance>, this did NOT work for me ... http://localhost/reportserver DOES work.

Well I have to disagree. I am also running a named instance, so the URL that works for me is
http://localhost/reportserver$<named_instance

When you create a new report model project its deploy URL by default is http://localhost/reportserver So i had to change that , through project properties, to the named instance one.

Good Luck !!

Tuesday, March 27, 2012

A Different Login failed for user sa problem

a DB connection Problem

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

Server Error in '/Rec_Web' Application.

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

Sunday, March 25, 2012

A couple of questions on Remote connection to SQL Server 2005 database

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

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

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

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

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.)

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

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.)

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

A connection to the report server failed

A connection to the report server failed

A connection remains open after calling Disconnect

a connection error

A connection could not be made with report server at https://webse

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

A connection could not be made with report server

A connection could not be made to the reporting server http://localhost/reportserver

Server Error in '/ReportServer' Application.

Configuration Error

A connection could not be made to the reporting server http://localhost/reportserver

A connection could not be made to the report server http://localhost/reportServer..

A connection could not be made to the report server http://localhost/reportServer..

3G ram for SQL server

Blog Archive

About Me