Re: ASP.net insists on using dbo. to call aspnet_* stored procedures

dbo is the schema used in SQL Server and, even if removed from queries, is technically still there. Unless, of course, you have created a new schema and own the objects in question. It sounds more like a permissions error or connectivity problem than a dbo problem.

Is SQL Server on the same box as your application? If not, turn on the SQL Browser service. If this is a default install, you may also have to turn on a protocol other than Managed Local (or whatever it is called). TCP/IP is a good one to turn on in most cases; you can also try named pipes.

--
Gregory A. Beamer
MVP; MCP: +I, SE, SD, DBA
http://gregorybeamer.spaces.live.com

*********************************************
Think outside the box!
*********************************************
"Pedro Vera" <pedro.vera@xxxxxxxxx> wrote in message news:1175261450.698261.35410@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
I am helping somebody setup one of the asp.net starter kits. I
converted it from sql express to sql server with no real issues, and I
got it running local perfectly.

On my first attempt to run it remotely I noticed that a lot of the
queries had dbo. hardcoded and that SQL server on the remote server
was not allowing my sql account access to these. I removed all
mentions of dbo. and again it still runs local. I have posted it to
the remote server once again, but I still get errors like this:

Could not find stored procedure 'dbo.aspnet_CheckSchemaVersion'

Now, the common sense answer here is that the remote database was not
primed properly with:

C:\WINDOWS\Microsoft.NET\Framework\v2.0.50727\aspnet_regsql.exe

But this is not true. The remote db was primed properly and I can run
aspnet_* stored procedures from enterprise manager logged in using the
same account used in the connection string.

Any idea how I can go around this? My worst case scenario is to grab a
clean copy of the starter kit and instead of removing dbo., changing
it from dbo. to mysqlusername. and see if that helps.

Thanks,

Pedro Vera
http://veraperez.com


.

Relevant Pages

  • ASP.net insists on using dbo. to call aspnet_* stored procedures
    ... I am helping somebody setup one of the asp.net starter kits. ... converted it from sql express to sql server with no real issues, ... queries had dbo. ... the remote server once again, but I still get errors like this: ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: DBO Best Practices
    ... lines of always owner qualifying objects... ... someone who are just "a" dbo. ... > doesn't explicitly reference the object's owner (because SQL Server will ... The startup account defines the ...
    (microsoft.public.sqlserver.security)
  • Re: DBO Best Practices
    ... If you let DBO own databases or objects then regular ... Please note that the DBO user is identified by the SQL Server process ... the SQL Server startup account (for the ... SQL Server process) controls SQL Server's ability to work with NT's objects ...
    (microsoft.public.sqlserver.security)
  • Re: ASP.net insists on using dbo. to call aspnet_* stored procedures
    ... No. mysql_login is one account and the dbo is another account, ... SQL Server 2000 developer in same machine. ... connection string is setup to use the sql login assigned to the ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: dbo qualified name error w Access 2003
    ... correctly, things ended up being owned by dbo, which is *not* ... One tool you should use is SQL Profiler. ... to see the calls between Access and SQL Server, ... >When I use an adp from Access 2000, this code executes successfully for all ...
    (microsoft.public.sqlserver.msde)