Issue with Dapper: Intermittent '@ParameterNames1 is not a parameter for procedure...' Error
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 18.4k
- Forks
- 3.7k
- Avg merge
- 5h 8m
- Merged PRs (30d)
- 1
Description
Hello,
I'm encountering an intermittent issue with Dapper. Occasionally, I receive the error message '@ParameterNames1 is not a parameter for procedure....' When I stop and restart the application using 'dotnet run', the error disappears, and everything works fine. However, after a while, the error reappears.
I've thoroughly checked the parameters I'm passing, and they are correct because the application runs without issues after restarting.
Could you please help me troubleshoot this issue?
Thank you.
P/s: Dapper 2.1.44 and .Net 8.0
``
using var con = new SqlConnection(_connectionString);
const string sql = "TestStore";
DynamicParameters para = new();
para.Add("@type", 1);
para.Add("@employeeID", employeeID);
var result = await con.QueryAsync<object>(sql, para, commandType: CommandType.StoredProcedure);
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the intermittent call in the provided C# snippet and inspect the SQL Server stored procedure named TestStore alongside its parameter definitions. Compare the failing and post-restart behavior, including the @type and @employeeID values; done means identifying why @ParameterNames1 is sent and documenting a reliable fix or reproduction.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp, sql
- Domain
- backend, database
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100