-
Notifications
You must be signed in to change notification settings - Fork 36
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Messages are not sent when database name includes periods or other special characters #1453
Comments
Hello @rhysgodfrey, Thank you for raising this with us. We have raised the bug internally. Unfortunately, I can't give you any firm ETA on when this will be taken care of, but we will keep you in the loop on this issue. |
we hit the same problem, but with a diff error message
|
We have a hyphen "-" in our and get the following error: SqlException: Incorrect syntax near '-'. |
A fix will be release in 8.1.6. Should be released soon. |
"soon" is such a relative term. can we get something more definitive ? |
8.1.6 and 7.0.8 have been released which fixes this. |
Describe the bug
Description
With version 7.0.7 of NServiceBus.Transport.SqlServer package when a message is moved or created by the endpoint it fails with a "Failed to send messsage" error, if the database name contains periods, for example
CompanyName.Project.Async.Transport
.This includes registering the endpoint with ServiceControl and Monitoring, or moving a message to the error queue.
Expected behavior
The endpoint is correctly registered with ServiceControl and Monitoring, and errored messages are moved to the error queue.
Actual behavior
Endpoint is not registered with ServiceControl and Monitoring, and errored messages aren't moved to error queue. Succesful messages are still processed.
Versions
NServiceBus.Transport.SqlServer - 7.0.7
Steps to reproduce
Create an endpoint with a database with a name containing periods for example
CompanyName.Project.Async.Transport
, upgrade to version 7.0.7 of the transport package, and configure it to register with ServiceControl, Monitoring, or to process a message that will fail.Relevant log output
Additional Information
Possible solutions
The error seems to suggest the problem is with this line, potentially adding square brackets around the database name would fix this? for example
FROM [{0}].sys.columns c
The text was updated successfully, but these errors were encountered: