Hi @IAA Dashboard here are a few things that might be worth re-checking (sometimes the root cause isn’t immediately apparent):
- make sure the account running the SQL Server service has explicit read access to both the file and its parent directory. The permissions needed are for the SQL service account, not your personal account
- If you’re using a local or network path, verify that the file is accessible from the SQL Server machine and that the path hasn’t changed. If you're accessing an Azure Blob, ensure any SAS tokens, access keys, or managed identity permissions are still valid and haven't expired or been rotated
- if there have been any recent updates to OS, group policy, antivirus, or firewall rules that might be affecting access
- the file isn’t open or being used by another process, which can sometimes cause access errors
- Make sure the SQL login being used has the necessary bulk operations permissions
- If this is running against Azure SQL Database (not SQL Server in a VM), direct file system access isn’t supported—use external data sources and make sure your authentication method is still valid