In any system with moving parts, occasionally things go wrong. Sometimes it’s the SQL Server’s fault, sometimes it’s the version control system’s fault. Sometimes it’s your fault, sometimes it’s my fault. Below are some error messages you may encounter when things go less than perfectly, along with their causes and resolutions.
Articles
- Access is denied
- Authorization canceled operation
- Cannot connect to database when it is paused
- Cannot push because a reference that you are trying to update on the remote contains commits that are not present locally
- Cannot push non-fastforwardable reference
- Cannot open database requested by the login
- Could not load file or assembly ‘SharpSvn.dll’ or one of its dependencies. The specified module could not be found.
- Directory not found
- Error pushing: push declined due to email privacy restrictions
- Expected FS format between ‘1’ and ‘6’; found format ‘8’
- Failed to parse supported auth schemes: The operation identifier is not valid.
- Failed to send request: A connection with the server could not be established
- Failed to send request: The operation timed out
- Invalid URI: The format of the URI could not be determined
- Invalid URI: The URI is empty
- Invalid url, missing path
- Malformed URL
- No process is on the other end of the pipe
- Request failed with status code: 401
- Request failed with status code: 403
- Request failed with status code: 404
- The wait operation timed out
- Too many redirects or authentication replays
- Unable to load object definition. Object may be encrypted.
- Unable to open repository
- Unsupported URL protocol
- VIEW SERVER STATE permission was denied on object ‘server’, database ‘master’. The user does not have permission to perform this action.
- Write access denied