problem with aspnet_ "Could not find stored procedure"

I have developed an asp.net 2.0 web application that uses sql2000 and with storded procedures.
Everything has been working great untill i yesterday found that someone have put in new stored procedures
in the database. The procedures starts with "dbo.aspnet_" like dbo.aspnet_CheckSchemaVersion.
Because i din't create them and i surtenly not call them from the application, i deleted them all.

Now when i try to use my web application nothing works. The app, somehow calls the procedure and becuase they are deleted
an error message is thrown like: Could not find stored procedure 'dbo.aspnet_CheckSchemaVersion'.

But the strange thing is that the problem only accure when i publish the site on the web server.
if i would publish it to a local folder on my desktop ore just run in debug mode against the database there are no problems.

I don't want to use the aspnet procedures that probebly comes from aspnet_regsql.exe and that im not calling from the code but reacts somehow,
I just want it to tun as it was designed to do.
And if i need them, can someone explain why?

please help :)

Dude, the "aspnet_" stuff is from Microsoft... it's the Membership provider. To get it back run "aspnet_regsql' in c:\windows\microsoft.net\framework\v2.blah (or wherever your windows files are).

|||

Yo Dude :) I did what you said and of course it worked. But i don't know why aspnet_regsql.exe is suddenly needed and all of those procedures that comes along. It worked without it before.

thx :)

sql

Problem with asp page and ODBC on Windows 2003 SR 64 Bits

I have an Application developed on ASP, I got a few new servers 64bits, I installed microsoft WIN 2003 SR.
When I get in into the web site I receive this errors:

Microsoft OLE DB Provider for ODBC Driverserror '80004005'

[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified

/ConnectToDatabase.asp, line 17

I made some obvios checks, I checked that the ODBC really exists and we move the IIS 6.0 to run in 32bits mode as I found in some page.

Thanks you.

Ahmed

Hi,

could you please post your connection string right in here ? We can′t see if you use a DSN or a DSNless connection.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de
|||

You are likely using an ODBC driver that is not available for 64bits. See http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=20574&SiteID=1 for the relevnat discusion.

Can you connect to the odbc driver in question using ODBC driver manager. Start->Run->ODBCAD32.exe. Using odbc driver manager create a new dsn and test the connection.

Problem with asp page and ODBC on Windows 2003 SR 64 Bits

I have an Application developed on ASP, I got a few new servers 64bits, I installed microsoft WIN 2003 SR.
When I get in into the web site I receive this errors:

Microsoft OLE DB Provider for ODBC Drivers error '80004005'

[Microsoft][ODBC Driver Manager] Data source name not found and no default driver specified

/ConnectToDatabase.asp, line 17

I made some obvios checks, I checked that the ODBC really exists and we move the IIS 6.0 to run in 32bits mode as I found in some page.

Thanks you.

Ahmed

Hi,

could you please post your connection string right in here ? We can′t see if you use a DSN or a DSNless connection.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de|||

You are likely using an ODBC driver that is not available for 64bits. See http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=20574&SiteID=1 for the relevnat discusion.

Can you connect to the odbc driver in question using ODBC driver manager. Start->Run->ODBCAD32.exe. Using odbc driver manager create a new dsn and test the connection.

Problem with "SQL Server does not exist" error

I have a couple of databases developed and being used in MSDE. The
db's are used and maintained from a couple of programs written in
Visual Basic 6 (using an ADO connection) (these programs run on a
separate computer).
I've just set up a new computer and installed SQL Server Express 2005
on it. I copied the .MDF files from the MSDE unit and attached them to
SQLExpress.
Now, when I try to connect to the databases, I get the "SQL Server
does not exist or access is denied" error. I have, of course, modified
the connection string such that the Data Source property is using the
correct computer name.
I've looked at everything I can think of but obviously I'm missing
something fundamental here. Any suggestions as to what I might be
doing wrong?
Thanks.
On Mon, 20 Nov 2006 16:22:39 +0100, "Andrea Montanari"
<andrea.sqlDMO@.virgilio.it> wrote:

>hi Martin,
>Martin wrote:
>please verify the instance name is correct (in the form
>ComputerName\InstanceName), the remote computer can access the lan and the
>remote SQLExpress installed computer, firewall (both) have been set with the
>appropriate exception(s) allowing connectivity and trafic (both the DBEngine
>used port and the SQLBrowser, if used), the SQLExpress network protocols
>have been enabled, the Surface Area Configuration ahs been set to allow
>remote connections...
Thanks, Andrea. I've gone thru your list but still no luck.
* the name of the new computer is "CATServer" (it's not actually a
"server" - it's running WinXP Pro with all current service packs and
updates). I've tried setting the Data Source to both "CATSERVER" and
"CATSERVER\SQLEXPRESS". Neither way seemed to make any difference.
* the remote computer CAN access CATServer. I have one folder on
CATServer shared and it can be viewed in Windows Explorer. Also, I can
ping CATServer successfully.
* there are no firewalls running on either computer.
* the network protocols: Shared Memory, Named Pipes and TCP/IP are
enabled; VIA is not enabled.
* the Surface Area Configuration was something I did not know anything
about. Remote Connections were set to "Local Connections Only". I
changed that to "Local and Remote" (for both TCP/IP and Named Pipes)
and then stopped and restarted the server service. It made no
difference. I also re-booted the computer but that, too, made no
difference.
Any other thoughts?
|||On Mon, 20 Nov 2006 18:20:18 +0100, "Andrea Montanari"
<andrea.sqlDMO@.virgilio.it> wrote:

>hi Martin,
>Martin wrote:
>http://support.microsoft.com/default.aspx?scid=kb;en-us;328306&Product=sql
Thanks again. I've gone through that fairly well but still haven't
been able to get connected.
I did stumble on to something though: I started the "SQL Server
Browser". Now, when my VB6 program tries to connect, I'm getting a
different error message: "Login failed for user 'userid'" (where
userid is the userid that's in my connect string).
Does this mean that SQL Server Browser has to be running in order for
my program to connect?
Also, when I posted earlier, I was using msado 2.5 in my VB program.
One of the things in the page you referenced mentioned that I needed
at least version 2.6. I have 2.7 (and 2.8) on the machine where VB is
running so I changed the reference to 2.7. That did not seems to make
any difference however. Does that shed any light on the problem I
might be up against?
|||On Mon, 20 Nov 2006 07:58:39 -0700, Martin <martinvalley@.comcast.net>
wrote:

>I have a couple of databases developed and being used in MSDE. The
>db's are used and maintained from a couple of programs written in
>Visual Basic 6 (using an ADO connection) (these programs run on a
>separate computer).
>I've just set up a new computer and installed SQL Server Express 2005
>on it. I copied the .MDF files from the MSDE unit and attached them to
>SQLExpress.
>Now, when I try to connect to the databases, I get the "SQL Server
>does not exist or access is denied" error. I have, of course, modified
>the connection string such that the Data Source property is using the
>correct computer name.
>I've looked at everything I can think of but obviously I'm missing
>something fundamental here. Any suggestions as to what I might be
>doing wrong?
>Thanks.
I finally got this working - sorta...
I had to do three things: I added "\SQLExpress" to the Data Source
name in the client program's connection string. Also in the client
program, I upgraded to version 2.8 of MSADO. On the server side of
things, I added the Login that I was trying to use from the client
side.
With these changes, I am now able to access the data on the server as
needed from the client programs.
With one major exception:
After I got everything working, I recompiled one of the VB programs
and installed it on another computer (call it computer B for
reference). But, when I run it, it encounters the exact same error
condition that I had originally! IOW, this thing works from computer A
but not from computer B.
Yes, computer B has version 2.8 of MSADO on it (I downloaded and
installed a verification tool and checked it out). Computer B has
access to the server computer where SQL Express is running (they're
all on the same LAN).
I'm stumped. Anyone have any ideas what the problem might be?
|||>I finally got this working - sorta...
>I had to do three things: I added "\SQLExpress" to the Data Source
>name in the client program's connection string. Also in the client
>program, I upgraded to version 2.8 of MSADO. On the server side of
>things, I added the Login that I was trying to use from the client
>side.
>With these changes, I am now able to access the data on the server as
>needed from the client programs.
>With one major exception:
>After I got everything working, I recompiled one of the VB programs
>and installed it on another computer (call it computer B for
>reference). But, when I run it, it encounters the exact same error
>condition that I had originally! IOW, this thing works from computer A
>but not from computer B.
>Yes, computer B has version 2.8 of MSADO on it (I downloaded and
>installed a verification tool and checked it out). Computer B has
>access to the server computer where SQL Express is running (they're
>all on the same LAN).
>I'm stumped. Anyone have any ideas what the problem might be?
>
OK, got it going...
Apparently, I have to have the SQL Server Browser service running in
order to connect from computer "B".
Why the Browser service is not needed by computer "A", I have no idea.
|||On Thu, 23 Nov 2006 12:09:01 +0100, "Andrea Montanari"
<andrea.sqlDMO@.virgilio.it> wrote:

>hi Martin,
>Martin wrote:
>SQLBrowser is not needed for local connections as they are not resolved over
>the TCP/IP stack but via shared memory and the port is directly resolved via
>local access...
>try modifying the network protocol (SQL Server Management Studio Express,
>connection dialog, "Options", "Network Protocol" = TCP/IP... you will not
>ba able to connect from local client as well..
I assume by "local connections" you mean "on the same physical
computer where SQL Server is running"? If so, then that is NOT the
case here. Both computer "A" and computer "B" in my situation are
"remote" - that is, they are separate computers on the LAN.
Again, it would seem to me that if one can connect, then the other
should be able to also.

Problem VB6, Ms access crystal report 9

Hi,
We have developed an application using VB 6.0, Ms access 2000 and crystal report 9. I have distributed the application. But in one Pc, when i am going to view a report i am getting a message "Windows Encountered a problem while processing your request, Please try later". Only for one report i am getting this message. Remaining all r working fine.
Is there anybody to help me in this?
Ty, JimmanToo fiew details to get help... It could even be a matter of Cpu too busy...or of Os servicepack..or of licences...|||Thank you for your reply.
IF those kind of problem is there like licencing, or service pack, how it is affecting for a single report alone.
We r getting problem in a particular report only ? Is there anythign to be done with that particular report?
Thanking you,
Jimman.|||Can not swear on this, as many time passed, but it seems to me I already saw something like that, and it was a "deadlock" mattter. Look at queries you're making to be sure you're not trying to write to a temp table while it is locked...as it is written by a process that is waiting for your first one to end...
Something else - this too from deep, deep inside - makes me think the matter is more related to Crystal Report than to Access or Vb. This is why I moved your question here (but left a link in Vb forum, so anyone can see your matter and help if able)|||Thank you so much for your kind reply.

I was not able to solve the problem yet.
What I am going to do is , I am going to unistall the application once more and try installing again, It may work.
Thank you so much for your help.
Jimman