Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1723
  • Last Modified:

Microsoft OLE DB Provider for SQL Server error '80040e14': The request for procedure 'tblResultsIncoming' failed because 'tblResultsIncoming' is a table object.

A fraction of users receive this error when completing an ASP survey.  Is this a coding error, or have we reached our maximum user limit?  

We have about 200 users trying to access, and about 180 have no problem with this same page, but the rest get the error:

Microsoft OLE DB Provider for SQL Server error '80040e14'
The request for procedure 'tblResultsIncoming' failed because 'tblResultsIncoming' is a table object.

      ' create recordset object
      Set objRst = Server.CreateObject("ADODB.RecordSet")
            objRst.Open "tblResultsIncoming", dbCONN, 1,4

I'm a network geek, not a db expert, so please forgive if I've said anything dumb or left anything out.

We're running this on a fast dual-processor server with 1 GB memory.    Thanks!
0
ciscochica
Asked:
ciscochica
  • 4
  • 3
2 Solutions
 
Jim HornMicrosoft SQL Server Developer, Architect, and AuthorCommented:
(A wild guess)  Perhaps the database developer created a stored proc named tblResultsIncoming, and there is already a table named tblResultsIncoming, and ASP is confused over which one to call.
0
 
ciscochicaAuthor Commented:
Now that you mention it, that makes sense, but.... If that's the case, wouldn't it always fail?
0
 
Jim HornMicrosoft SQL Server Developer, Architect, and AuthorCommented:
You would think, yes.  I tend to prefix these things as 'wild guesses', as you never know.  
0
VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

 
Jim HornMicrosoft SQL Server Developer, Architect, and AuthorCommented:
Just a though... if this server has a whole lot of databases for a whole lot of applications, I might be a little nervous with an ASP app directly editing it as opposed to using a middle-tier COM component.
0
 
nmcdermaidCommented:
Try changing it to this:

objRst.Open "tblResultsIncoming", dbCONN, 1,4,2

a 2 on the end means the source you provided is a table name




You will find that if you change it to this:

objRst.Open "tblResultsIncoming", dbCONN, 1,4,4

It will always return with that error. 4 means its a stored procedure. Perhaps sometimes your parameters are getting mixed up and it thinks its a stored procedure
0
 
ciscochicaAuthor Commented:
The coder was able to resolve (knock on wood) by eliminating the stored object and calling the table directly.  Definitely a coding error.

Thanks for your help!!
0
 
Jim HornMicrosoft SQL Server Developer, Architect, and AuthorCommented:
Glad you were able to get a solution.  

Also, applying a naming convention to the database's objects would likely prevent this from happening.  I'd be a little leery about what else is going on in that db.  

Just my .02.
0
 
ciscochicaAuthor Commented:
:-)  I already am - but I'm just the network geek.
0

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now