Microsoft SQl Server 2000 Desktop Engine

Hello Folks,

Just installed Microsoft SQl Server 2000 Desktop Engine
as instructed bySams Teach Yourself ASP.NET
After trying to connect to the database in the Connect
to database dialog box. Got this error message
"Unable to connect to the database. Login failed for user 'sa'.
Not associated with trusted SQL Server Connection."
The desktop server is on my home computer.
How to I solve this?
Thanks for any help,
Student33Hi,

What is the connection string you're using to connect to the database?

Don

microsoft sql database (*.mdf) using help ?

Hi

I use visual std. 2005 and I create a asp.net web page after >add item> sql database > I added my project *.mdf file when I make project my project is runnig with visual studio 2005 but I sent my hostting (internet server )I cant use this mdf file . Are we register this mdf file sqlserver ? can we use this mdf file like access file (mdb ) . What kind of thing I do to use this mdf file .

Thanks

I know some hosts don't support SQL 2005, FastHosts in the UK for exampe have no plans to allow the user of the SQL Express MDF files so it cannot work like an Access MDB file. They say that this is down to performance and security implications.|||

prokurs:

Are we register this mdf file sqlserver ? can we use this mdf file like access file (mdb ) . What kind of thing I do to use this mdf file .

No, you must have a SQL instance on the host to use mdf files. Although in VS2005 you can create mdf files and use them by attaching them to a SQL Express Instance (specified in the Data Source property in your connection string), you still need a SQL Instance to which you have access. So you must have a SQL2005/Express instance on the hosting machine, and then add proper permissions to your account.

|||

hi can you look my mistake this mistake's source ishttp://www.prokurs.com/e/loginana.aspx you can enter this page after write random user name and passwors after then I have got a this mistake please help ?

Server Error in '/' Application.

---

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)

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: An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)

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): An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)] System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) +735091 System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) +188 System.Data.SqlClient.TdsParser.Connect(Boolean& useFailoverPartner, Boolean& failoverDemandDone, String host, String failoverPartner, String protocol, SqlInternalConnectionTds connHandler, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection owningObject, Boolean aliasLookup) +820 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) +130 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

---

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

|||

It is a connection failure, if you're using SQL2000 you need to make sure TCP/IP and Named Pipes network libraries are enabled on the SQL2000 instance via Server Network Utility; in case of SQL2005/Express you can enable the remote connecitons using SQL Server Surface Area. Then rewrite your connection string to point to the correct SQL instance.

If you're using built-in Login Controls (membership provider) in .NET 2.0, you can customize the database connections as mentioned in this article:

http://weblogs.asp.net/scottgu/archive/2005/08/25/423703.aspx

sql

Microsoft SQL 2005 Licensing & ASP.NET applications

I am having a nightmare getting an answer about what type of licensing I will need for the standard addition of SQL Server 2005 for my asp.net application and wonder if anyone has any advice.

As I see it its very simple, I have a web app that makes a connection to SQL via a connection string using a single username and password, no impersonation just straight SQL authentication.

For this simple scenario I figured I would need to get a SQL 2005 license and then 1 Client access license (CAL), this being a nice affordable way of doing things BUT I am being told by different sources, that I may need to license on a per processor basis as any user of my web application, anonymous or otherwise needs a client access license and given that I don't know how many users are going to access my website I would need to go for the larger outlay and purchase two standard processor license (my sql server is a dual processor machine).

Can anyone tell me if this is the case, is a connection from a ASP.Net website to a SQL server for my website visitors regarded as a new client and therefore needs a client access license or the large investment of a per processor license?

I would stick with SQL Express but at 4gigs max it won't do the job.

Thanks in advance.

SQL Server license since 2000 is per processor not CAL and I cannot understand how you think you need just one CAL when you know Express 4gig is too small for your needs. Hope this helps.|||

No it doesn't help...

Microsoft advertise CAL as a licensing option along side the processor option and given its a web app with just one connection doing all the work why wouldn't I think I only need one CAL, do you have anything else to add?

|||The only way you can use one CAL is you have only one user, your other choice is to use the Smallbusiness Server SQL Server but I think you will get more from Express because the Smallbusiness Server comes with SQL Server 2000.|||

The small business server is overkill; it's a simple website using sql 2005 as the database.

Just to go over it again. I have a public internet facing website that creates a connection to SQL 2005, in my mind this is a single user, the website is the only user of the SQL server so in that case I need just one CAL, what do you think, that has to be correct doesn't it?

SQL 2005 isn't any use due to the 4gig limit.

|||

I have been in a shop with 68 SQL Servers trust me if 4gig is not enough for you, then you need a per processor license. And the Smallbusines server is not an over kill because you can choose to use only the SQL Server and it will cost you less than $1000 and 75 concurrent users.

|||

SBS is not an ideal for a single N-Tier application so we can forget that. 4gig isnt enough so we can discount Express. Now given we have cut through the dead wood and are now look at the heart of the matter, i will reiterate it just one more time:

If i have an ASP.NET application connecting to an SQL Server via a single connection am I able to use a single CAL?

If you are unsure of the answer please dont mention SBS or Express again otherwise we could be here all night :-)

|||The answer is no.|||Why?|||The answer is your single connection is just for the Asp.net worker process not a live user, and if you send email that is another user. The best thing to do is call your local Microsoft office and have a SQL Server local resource contact you.|||

So what you are saying is you dont know?

If the .net worker process connects and returns data I agree that's one client access, the SQL server isn't sending email or doing anything other than being a database so hence I conclusion that I only need to purchase a single CAL. The reason for my posting is because my Microsoft Office here seems unsure themselves!

|||No I am not telling you I don't know the number of cal you use depends on your write users how many will write in the database. So count your INSERT and UPDATE users and you will have an idea of how many cals you need and I don't think it will be one.|||

Why would it not be one user? In web application development it would be foolhardy to develop an application that allowed for multiple read write accounts when a website traditionally allows anonymous access. If you read most Microsoft best practices you will find that they specify a web application user account that allows for the execution of stored procedures and that's it no other accounts, no insert account or update account or a special forgotten sa account that lets Mr foobar hacker traverse directories via a script injection.

So given we hope that most web applications have minimal sql accounts do you agree that I need the bare minimum CAL's or do you have any other thoughts?

|||

No I don't the shop with 68 SQL Servers and one Oracle was a bank and every account is a write user. SQL injection is not permission related my MCDBA was when there are no books on SQL Server 7.0. The link below is one of the oldest software retailers online most of your questions are answered. Stored proc execution through DBO(database owner) is not related to write permissions. And SQL Server permissions are implemented by Microsoft but defined by ANSI SQL.

http://www.provantage.com/sql-server-standard-edition-32-bit-windows~220152612.htm

|||

Ok we are off the topic now and you kind of asked for this so sorry in advance...

SQL injection can relate to permissions, if you don't have the correct permissions you are susceptible to all sorts of injection if your web application allows it. You clearly have no experience of SQL in the environment that I entitled my original post and without descending into the kind of flaming exercise I have seen on many other forums, can i just say that roaming around posting glib answers may give you a large number at the end of your screen name but it isn't helping anyone and its making you look a little silly.

Oh and if had wanted the advice of a retailer I would of gone to my local supermarket and asked on of the chaps behind the till the question.

There I said it and now that this post has sunk to this level i guess I will need to ask my question else where!

Microsoft OLEDB Provider Error (with SQL server and ASP)

Dear all,

Still i am having problem with connecting sql server with ASP (Intranet).

Following is the code which i am using for the connection now,

Set conn=Server.CreateObject("ADODB.Connection")
conn.open "DSN=aspfirst;Uid=;PWD=;"

The error mesage , generated by this code is attached with this mail. Please check the attachment and hel me in the same

Gracesonhttp://support.microsoft.com/default.aspx?scid=kb;en-us;q306518 To resolve.

HTH|||Thank you so much.

I could resolve the problem.

It was just add user IUSR_mechinename fromuser list.

Good finishing for a marathon...

bye

Thank you

gracesonsql

Microsoft OLE DB Provider for SQL Server error '80040e37'

I get Microsoft OLE DB Provider for SQL Server error '80040e37'

Invalid object name '#t_testTemp484883646'.
when I run the following ASP code:

Code is below

<!#Include File="../includes/adovbs.inc" -->

<HTML>
<HEAD>
<META NAME="GENERATOR" Content="Microsoft Visual Studio 6.0">
<TITLE></TITLE>
</HEAD>
<BODY>

<%
'-- Setup database connection
Set DataCmd = Server.CreateObject("ADODB.Connection")
Set rsData = Server.CreateObject("ADODB.RecordSet")
Dim varTempTableName
DataCmd.Open Application("DB")
'-- Use a Temp Table so that it gets destroyed automatically in case the page times out
'-- Use a Global Temp Table so that it is available across scopes when I open the record set below
'-- Append a semi unique number to the end because its global it could conflict with another browser running the same report
'varTempTableName = "##t_TestTemp" & Minute(Now()) & Second(Now())
varTempTableName = "#t_TestTemp" & Session.SessionID

strSQL = "Create Table " & varTempTableName & "(TestColumn2 int)"
DataCmd.Execute strSQL

strSQL = "select * from t_Test"
rsData.Open strSQL, DataCmd, adOpenForwardOnly,adLockReadOnly

Do While Not rsData.EOF
varTestColumn2 = rsData("TestColumn2")

'Error occurs when I place the following insert statement. Code works with the global variable

strSQL = "Insert into " & varTempTableName & " (TestColumn2) values (" & varTestColumn2 & ")"
DataCmd.Execute strSQL

rsData.MoveNext
Loop
rsData.Close

strSQL = "Drop Table " & varTempTableName
DataCmd.Execute strSQL

Set rsData = Nothing
Set DataCmd = Nothing
%>
</BODY>
</HTML>

If you have connection pooling enabled you will get *one* of the connection which *could* be actually not the same connection as this which created the temp table. So either use global temp tables (## instead of #) or disable connection pooling.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de

Microsoft OLE DB Provider for SQL Server error '80004005' - Unspecified error

Hi,
I have an ASP code that calls a stored procedure. I use a Command
object to execute the stored procedure. The Stored procedure returns
data when executed in Query analyser. But it takes around 1 minute for
this. The stored procedure involves querying a huge amount of data.
When I try to open the ASP page, I get the following error :
Microsoft OLE DB Provider for SQL Server error '80004005'
Unspecified error
Any suggestions?
TIA,
AnishyaHi
Have you checked with SQL Profiler that the procedure is being called? Check
that the login/user you are using has the correct permissions. If this has
timed out then I would expect that a TIMEOUT error message. You may also want
to check http://www.aspfaq.com/show.asp?id=2009
John
"Ani" wrote:
> Hi,
> I have an ASP code that calls a stored procedure. I use a Command
> object to execute the stored procedure. The Stored procedure returns
> data when executed in Query analyser. But it takes around 1 minute for
> this. The stored procedure involves querying a huge amount of data.
> When I try to open the ASP page, I get the following error :
> Microsoft OLE DB Provider for SQL Server error '80004005'
> Unspecified error
> Any suggestions?
> TIA,
> Anishya
>|||Hi,
The procedure is being called in the Profiler. I tried executing the
same stored procedure call in query analyser and saw that it works
fine. The only problem is that it takes around 1 minute. So I am sure
this is why the ASP page gives the error. The stored proc makes the use
of a temporary table. I tried executing the stored proc by using a
permanent table instead of the temporary table. It doesnt take much
time. But doesn't permanent tables involve more performance overheads
than temporary tables? I am trying to find another alternative. Is
there any way that I could increase the timeout period for ASP pages?
Thanks,
Anishya|||Hi
You could be seeing contention on tempdb if a lot of people are
simulataneously creating temporary tables, see
http://support.microsoft.com/kb/328551. You should see if the temporary table
is really necessary or possibly use a table variable as an alternative.
You may also want to change the timeout on your command object
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/ado270/htm/mdprocommandtimeout.asp
John
"Ani" wrote:
> Hi,
> The procedure is being called in the Profiler. I tried executing the
> same stored procedure call in query analyser and saw that it works
> fine. The only problem is that it takes around 1 minute. So I am sure
> this is why the ASP page gives the error. The stored proc makes the use
> of a temporary table. I tried executing the stored proc by using a
> permanent table instead of the temporary table. It doesnt take much
> time. But doesn't permanent tables involve more performance overheads
> than temporary tables? I am trying to find another alternative. Is
> there any way that I could increase the timeout period for ASP pages?
> Thanks,
> Anishya
>

Microsoft OLE DB Provider for SQL Server error 80004005

Hi friends,

Can anyone help me in connecting sql server and asp.
Wheneever try to do the connection, I am getting following error. All the connection string which i am using are correct.

can you help me.

Following are the error line

--------------------

Microsoft OLE DB Provider for SQL Server error '80004005'

Invalid connection string attribute

/MAsteringASP/global.asa, line 17

Microsoft OLE DB Provider for SQL Server error '80004005'

Invalid connection string attribute

/MAsteringASP/test2.asp, line 21
----------------

Please ckeck my code which I am using for connection

Thank you

Graceson MAthew

--------------------
<%@. Language =VBScript %>
<% option explicit %>

<Html>
<head>
<title> Database Connection </title>
</head>
<body>
<%

<!-- #INCLUDE FILE="adovbs.inc" -->

dim conn
dim sql
dim r
dim aConnectionString

Set conn=Server.CreateObject("ADODB.Connection")

conn.Mode=adModeReadWrite
conn.Open="Provider=SQLOLEDB;UID=Administrator;Password=passw d;Initial Catalog=nrth;Datasource=server ip;Port Number= 80"

Response.Write (" Database Connectivity")

%>
</body>
</html>try this type of connection string

driver={SQL Server};server=Server ip\DontForgetTheInstanceName;uid=Administrator;pwd =password;Database=nrth|||Also KBA (http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/Q169/3/77.asp&NoWebContent=1) to detail the connection between ASP & SQL Server.

HTH|||I don't recall Port NMumber being used in a connection string. Maybe if you took that part out?|||Ensure SQL uses that port and enabled on server or that port is not used by any other application.|||oh gosh, can't believe nobody saw this one!

replace uid with user id

:D :D :D :D :D|||Hehe. I guess that would be a problem for SQLOLEDB. Was UID phased out with the previous driver? Can't even remember what it was called. MSQL something-or-other.|||MSDASQL|||Dear karolyn,

Thank you for your reply, i attended the problem i the way you suggested .But now i am getting some other error, which is also could not rectify me,

now error is in following way
------
Microsoft OLE DB Provider for ODBC Drivers error '80004005'
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied.

//global.asa, line 17

Microsoft OLE DB Provider for ODBC Drivers error '80004005'

[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied.

/test2.asp, line 21

----------------------

Will you please help me .

graceson


Originally posted by Karolyn
try this type of connection string

driver={SQL Server};server=Server ip\DontForgetTheInstanceName;uid=Administrator;pwd =password;Database=nrth|||http://support.microsoft.com/default.aspx?scid=kb;EN-US;Q328306 to deal the issue.|||i think you're trying to use windows authentication. in this case you need to try this:

conn.Open="Provider=SQLOLEDB;Integrated Security=SSPI;Initial Catalog=nrth;Datasource=server ip;Port Number= 80"

also, i noticed that if this is your "exact" connection string, you need to know the ip address of the server, as well as the actual port it's listening on. confirm it's port 80, otherwise the default is 1433 (port 80 is the default for http)

Microsoft OLE DB Provider for ODBC Drivers error 80004005

Hi everybody
My problem with sql server is the following one:
I've got my backoffice manager application done with asp technology
that works on sql server installed on Win2000 and running on IIS5.
what I've done is simply doing a backup of my db and moving the asp
application on another server: Windows 2003 with IIS6 and sql server
vers.8.
Then I tried to set up everything as in the beginning on the previous
machine(Win2K), but I'm getting this error:

Microsoft OLE DB Provider for SQL Server error '80004005'
[DBNETLIB][ConnectionOpen (Connect()).]Server SQL inesistente o accesso
negato.
(translated would be "SQL Server doesn't exist or access denied")
/sitowebsite/bom/login.asp, line 13

...where in the line 13 is set the connection to the database:
Conn.Open Application("DBsource")

which should be driven by what is set inside the global.asa file:
Application("DBsource")="Provider=SQLOLEDB;server=127.0.0.1;database=db_nam e;uid=db_uid;pwd=db_pwd;"
Application("WS_DB_TYPE") = ( "SQLSERVER" )

I tried to restore the database just not losing information and nothing
happens.
I tried also to create a new user and modify the properties as it
should be from the previous settings in the db(db_owner,...etc), still
nothing.

any clue is appriciated.
many thanks in advance.ziottt (t.giommi@.gmail.com) writes:

Quote:

Originally Posted by

My problem with sql server is the following one:
I've got my backoffice manager application done with asp technology
that works on sql server installed on Win2000 and running on IIS5.
what I've done is simply doing a backup of my db and moving the asp
application on another server: Windows 2003 with IIS6 and sql server
vers.8.
Then I tried to set up everything as in the beginning on the previous
machine(Win2K), but I'm getting this error:
>
Microsoft OLE DB Provider for SQL Server error '80004005'
[DBNETLIB][ConnectionOpen (Connect()).]Server SQL inesistente o accesso
negato.
(translated would be "SQL Server doesn't exist or access denied")
/sitowebsite/bom/login.asp, line 13

This error message that the application cannot reach the SQL Server
you are trying to connect to. Thus, users or backups have no importance,
because you don't reach that far.

Quote:

Originally Posted by

...where in the line 13 is set the connection to the database:
Conn.Open Application("DBsource")
>
which should be driven by what is set inside the global.asa file:
>
>Application("DBsource")="Provider=SQLOLEDB;server=127.0.0.1;database=db_nam
>e;uid=db_uid;pwd=db_pwd;"

And SQL Server is running on the same server as the web server? Have you
verified that SQL Server is actually running?

Diclaimer: I don't know ASP, so if there are any problems with that
global.asa, I can't tell.

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx

Microsoft OLE DB Provider for Analysis Services error 80004005

Hello

I get the following error message in one of my ASP applications:
--------------------------
Microsoft OLE DB Provider for Analysis Services error '80004005'
Cannot connect to the server '172.16.103.14'. The server is either not started or too busy.
--------------------------
The IIS server is on a different machine to the MSOLAP server.

When I change the ASP code to point the 'localhost' it runs fine so Im fairly confident the necessary db conn libraries are installed on the IIS server.

There does not appear to be any traffic between the IIS/MSOLAP servers. Although all TCP ports are open. Interestingly, there are other pages on the same site that access a SQL Server resident on the MSOLAP servers & there are no issues.

Any assistance on this matter would be greatly appreciated. (I am a relative novice re: ASP/MSOLAP/IIS etc)Howdy

Talk to your networking guys & check the Default Gateway setting for TCPIP on the server. Sounds like it cant find the server.

Can you ping the IP address from a dos window on the server?

Cheers

SG|||You should check client-library/server-library settings. You prolly have named pipes only and no TCP-IP connection set-up.|||Originally posted by sqlguy7777
Howdy

Talk to your networking guys & check the Default Gateway setting for TCPIP on the server. Sounds like it cant find the server.

Can you ping the IP address from a dos window on the server?

Cheers

SG

Everything seems to be in order on this front. You will note that connectivity to a SQL Server database on the application/database server from the ASP pages on the web server function OK.|||Originally posted by beyond cool
You should check client-library/server-library settings. You prolly have named pipes only and no TCP-IP connection set-up.

Everything seems to be in order on this front. Note that connectivity to a SQL Server database on the application/database server from the ASP pages on the web server function OK...unless im missing something here....|||Howdy kalaa,

Can you confirm you can do these things :

(1) Ping the SQL box by name from the web server from a dos window on the web server e.g. ping <SQL_Server_name>. This will test if you have connectivity to the SQL box from the web server and more importantly confirm the SQL box is recognised in DNS.

(2) you have a valid SQL user ID set up on the SQL box, and that user ID has at least read access in the required database on the SQL box.
This is the user ID that the web application will use to talk to the SQL box.

Cheers,

SG

Microsoft ASP Licensing Program for SQL Server

I own and run a small ASP that provides membership management services to
non-profit organizations. Currently I host my application on a dedicated
Windows Server 2003 machine at a hosting provider. The application is
..NET-based and makes use of SQL Server databases on a shared SQL Server
machine at said hosting provider.
I have recently been encountering limitations with this usage of SQL
databases on a shared machine. I am ready to purchase my own SQL Server
license. It looks like a per-processor license is the way to go. Because I am
a small operation, I cannot afford outright purchase of SQL Server Enterprise
Edition ($19,000-plus for 1 processor) or SQL Server 2000 Standard Edition
($4,700-plus for 1 processor).
It looks like the program for me may be the Microsoft ASP Licensing Program,
which appears to offer a monthly bill for a SQL Server per-processor license.
But I'm not getting good answers on this program from the published
materials. In particular, my questions are:
1) Is my company eligible for this program? We are a Registered Member in
the Empower Program for ISVs. (Microsoft's "ASP Strategy Whitepaper" says a
company must be a Microsoft Certified Solution Provider to buy from the ASP
Licensing Program. Is this a hoop I need to jump through to buy SQL Server on
the ASP plan?)
2) What is the pricing for this program?
Any help you can offer on these questions would be appreciated.
rxsullivan wrote:
> I own and run a small ASP that provides membership management
You should contact Microsoft directly for this question.
David Gugick
Imceda Software
www.imceda.com
|||I agree that you should contact your local MS office for this. In
Australiia, this particular area is looked after by a "Regional Hosting
Specialist", but he's mainly interested in the SPLA licensing you're
referring to. Make sure you look up what's available to you through your ISV
contacts as my experience is that in some cases, these guys can sometimes
save you more money than through SPLA, especially if you're a leading
product in your field.
What country are you in? I'd be happy to ping my local contact to see if I
can help get you connected.
Regards,
Greg Linwood
SQL Server MVP
"rxsullivan" <rxsullivan@.discussions.microsoft.com> wrote in message
news:A6B1CA2D-E162-477E-A1E9-B2E9EBBEE40A@.microsoft.com...
>I own and run a small ASP that provides membership management services to
> non-profit organizations. Currently I host my application on a dedicated
> Windows Server 2003 machine at a hosting provider. The application is
> .NET-based and makes use of SQL Server databases on a shared SQL Server
> machine at said hosting provider.
> I have recently been encountering limitations with this usage of SQL
> databases on a shared machine. I am ready to purchase my own SQL Server
> license. It looks like a per-processor license is the way to go. Because I
> am
> a small operation, I cannot afford outright purchase of SQL Server
> Enterprise
> Edition ($19,000-plus for 1 processor) or SQL Server 2000 Standard Edition
> ($4,700-plus for 1 processor).
> It looks like the program for me may be the Microsoft ASP Licensing
> Program,
> which appears to offer a monthly bill for a SQL Server per-processor
> license.
> But I'm not getting good answers on this program from the published
> materials. In particular, my questions are:
> 1) Is my company eligible for this program? We are a Registered Member in
> the Empower Program for ISVs. (Microsoft's "ASP Strategy Whitepaper" says
> a
> company must be a Microsoft Certified Solution Provider to buy from the
> ASP
> Licensing Program. Is this a hoop I need to jump through to buy SQL Server
> on
> the ASP plan?)
> 2) What is the pricing for this program?
> Any help you can offer on these questions would be appreciated.

Microsoft ASP Licensing Program for SQL Server

I own and run a small ASP that provides membership management services to
non-profit organizations. Currently I host my application on a dedicated
Windows Server 2003 machine at a hosting provider. The application is
.NET-based and makes use of SQL Server databases on a shared SQL Server
machine at said hosting provider.
I have recently been encountering limitations with this usage of SQL
databases on a shared machine. I am ready to purchase my own SQL Server
license. It looks like a per-processor license is the way to go. Because I am
a small operation, I cannot afford outright purchase of SQL Server Enterprise
Edition ($19,000-plus for 1 processor) or SQL Server 2000 Standard Edition
($4,700-plus for 1 processor).
It looks like the program for me may be the Microsoft ASP Licensing Program,
which appears to offer a monthly bill for a SQL Server per-processor license.
But I'm not getting good answers on this program from the published
materials. In particular, my questions are:
1) Is my company eligible for this program? We are a Registered Member in
the Empower Program for ISVs. (Microsoft's "ASP Strategy Whitepaper" says a
company must be a Microsoft Certified Solution Provider to buy from the ASP
Licensing Program. Is this a hoop I need to jump through to buy SQL Server on
the ASP plan?)
2) What is the pricing for this program?
Any help you can offer on these questions would be appreciated.rxsullivan wrote:
> I own and run a small ASP that provides membership management
You should contact Microsoft directly for this question.
--
David Gugick
Imceda Software
www.imceda.com|||I agree that you should contact your local MS office for this. In
Australiia, this particular area is looked after by a "Regional Hosting
Specialist", but he's mainly interested in the SPLA licensing you're
referring to. Make sure you look up what's available to you through your ISV
contacts as my experience is that in some cases, these guys can sometimes
save you more money than through SPLA, especially if you're a leading
product in your field.
What country are you in? I'd be happy to ping my local contact to see if I
can help get you connected.
Regards,
Greg Linwood
SQL Server MVP
"rxsullivan" <rxsullivan@.discussions.microsoft.com> wrote in message
news:A6B1CA2D-E162-477E-A1E9-B2E9EBBEE40A@.microsoft.com...
>I own and run a small ASP that provides membership management services to
> non-profit organizations. Currently I host my application on a dedicated
> Windows Server 2003 machine at a hosting provider. The application is
> .NET-based and makes use of SQL Server databases on a shared SQL Server
> machine at said hosting provider.
> I have recently been encountering limitations with this usage of SQL
> databases on a shared machine. I am ready to purchase my own SQL Server
> license. It looks like a per-processor license is the way to go. Because I
> am
> a small operation, I cannot afford outright purchase of SQL Server
> Enterprise
> Edition ($19,000-plus for 1 processor) or SQL Server 2000 Standard Edition
> ($4,700-plus for 1 processor).
> It looks like the program for me may be the Microsoft ASP Licensing
> Program,
> which appears to offer a monthly bill for a SQL Server per-processor
> license.
> But I'm not getting good answers on this program from the published
> materials. In particular, my questions are:
> 1) Is my company eligible for this program? We are a Registered Member in
> the Empower Program for ISVs. (Microsoft's "ASP Strategy Whitepaper" says
> a
> company must be a Microsoft Certified Solution Provider to buy from the
> ASP
> Licensing Program. Is this a hoop I need to jump through to buy SQL Server
> on
> the ASP plan?)
> 2) What is the pricing for this program?
> Any help you can offer on these questions would be appreciated.

Microsoft ASP Licensing Program for SQL Server

I own and run a small ASP that provides membership management services to
non-profit organizations. Currently I host my application on a dedicated
Windows Server 2003 machine at a hosting provider. The application is
.NET-based and makes use of SQL Server databases on a shared SQL Server
machine at said hosting provider.
I have recently been encountering limitations with this usage of SQL
databases on a shared machine. I am ready to purchase my own SQL Server
license. It looks like a per-processor license is the way to go. Because I a
m
a small operation, I cannot afford outright purchase of SQL Server Enterpris
e
Edition ($19,000-plus for 1 processor) or SQL Server 2000 Standard Edition
($4,700-plus for 1 processor).
It looks like the program for me may be the Microsoft ASP Licensing Program,
which appears to offer a monthly bill for a SQL Server per-processor license
.
But I'm not getting good answers on this program from the published
materials. In particular, my questions are:
1) Is my company eligible for this program? We are a Registered Member in
the Empower Program for ISVs. (Microsoft's "ASP Strategy Whitepaper" says a
company must be a Microsoft Certified Solution Provider to buy from the ASP
Licensing Program. Is this a hoop I need to jump through to buy SQL Server o
n
the ASP plan?)
2) What is the pricing for this program?
Any help you can offer on these questions would be appreciated.rxsullivan wrote:
> I own and run a small ASP that provides membership management
You should contact Microsoft directly for this question.
David Gugick
Imceda Software
www.imceda.com|||I agree that you should contact your local MS office for this. In
Australiia, this particular area is looked after by a "Regional Hosting
Specialist", but he's mainly interested in the SPLA licensing you're
referring to. Make sure you look up what's available to you through your ISV
contacts as my experience is that in some cases, these guys can sometimes
save you more money than through SPLA, especially if you're a leading
product in your field.
What country are you in? I'd be happy to ping my local contact to see if I
can help get you connected.
Regards,
Greg Linwood
SQL Server MVP
"rxsullivan" <rxsullivan@.discussions.microsoft.com> wrote in message
news:A6B1CA2D-E162-477E-A1E9-B2E9EBBEE40A@.microsoft.com...
>I own and run a small ASP that provides membership management services to
> non-profit organizations. Currently I host my application on a dedicated
> Windows Server 2003 machine at a hosting provider. The application is
> .NET-based and makes use of SQL Server databases on a shared SQL Server
> machine at said hosting provider.
> I have recently been encountering limitations with this usage of SQL
> databases on a shared machine. I am ready to purchase my own SQL Server
> license. It looks like a per-processor license is the way to go. Because I
> am
> a small operation, I cannot afford outright purchase of SQL Server
> Enterprise
> Edition ($19,000-plus for 1 processor) or SQL Server 2000 Standard Edition
> ($4,700-plus for 1 processor).
> It looks like the program for me may be the Microsoft ASP Licensing
> Program,
> which appears to offer a monthly bill for a SQL Server per-processor
> license.
> But I'm not getting good answers on this program from the published
> materials. In particular, my questions are:
> 1) Is my company eligible for this program? We are a Registered Member in
> the Empower Program for ISVs. (Microsoft's "ASP Strategy Whitepaper" says
> a
> company must be a Microsoft Certified Solution Provider to buy from the
> ASP
> Licensing Program. Is this a hoop I need to jump through to buy SQL Server
> on
> the ASP plan?)
> 2) What is the pricing for this program?
> Any help you can offer on these questions would be appreciated.

Method not found: Void Microsoft.Reporting.WebForms.ReportViewer.Reset().

After using this Reset method on my asp RV control, now the page issues this error:

Exception Details:System.MissingMethodException: Method not found: 'Void Microsoft.Reporting.WebForms.ReportViewer.Reset()'.

I tried downloading ReportViewer.exe 2005 Redistr. from the MS site and installed at the server but still get same error.

Is there a newer redist somewhere that I haven't found? Or do I need to regasm some files?

Fixed it. Even after running the ReportViewer.exe 2005 Redistr. on the server machine, nothing changed. Looks like that Redist from MS is not up to date.

I ended up copying my local files(Common, WebForms) to the server then running gacutil -i on them. All better.

|||

I'm glad you posted a solution to this error. I'm having the exact same problem when I transfer my application to our Windows Server 2003 box. What local files exactly did you transfer? I searched for both "Common" and "WebForms" on my workstation but was unable to find them. Thanks!

Regards,
David Gardner

|||

These are the files you need to use Reset():

Microsoft.ReportViewer.Common.dll 8.0.50727.762

Microsoft.ReportViewer.WebForms.dll 8.0.50727.762

|||

Alright. I'm having the same problems.

I installed the Visual Studio 2k5 SP1 as well as the ReportingViewer.exe redist. and nothing seems to work

Everytime I try to call reportviewer.reset() in code, it gets a blue squiggly underneath it and says "reset is not a member of Microsoft.Reporting.WebForms.ReportViewer"

I have tried to remove the references to the Microsoft.Reporting dlls and adding them back in but nothing has worked.

Anything else I can try?

|||

I'm having the same problem.

How do I use the gacutil? Can someone please send me the syntax for it?

Basically on my development machine I have VS2005 SP1 installed. When i'm deploying my application onto the staging server, I keep getting the following error message:

method does not exist: 'Void Microsoft.Reporting.WebForms.ReportViewer.Reset()'

Someone please help!!!

|||

Eric,

Can you send me the syntax for the gacutil please?

I'm having the same issues as the others are having, where it works on my development machine but not on the staging server.

I'll appreciate it.

|||

Eric,

I am also facing the same problem. After installating report viewer redistributable service pack it got solved in local machine. But after uplaoding to server, an empty alert with no message is showing.

I have tried to copy local files i.e common & webform from c:\winnt\assembly, MMS but its not allowing. From where should i copy these files.

Thanks In Advance.

Regards,

Vijay Kumar

|||

A better solution is to install the ReportViewer 2005 Redistributable SP1:
Microsoft Report Viewer Redistributable 2005 SP1 (Upgrade)

If you haven't installed the original redistributable, you can do the full SP1 install:
Microsoft Report Viewer Redistributable 2005 SP1 (Full Installation)

Note: you'll need to install Windows Installer 3.1 on your server if you want to use the Upgrade patch.