We had a job that an enterprise software vendor was running that failed on permissions denied. They asked us to open the file share to anyone without a password. Our awesome SQL Server DBA pushed back, thankfully. We came up with what is below to troubleshoot.<\/p>\n
This allowed us to reproduce the condition, the root cause of which was traced back to a subdomain issue. Quick POC’s like this enable you to troubleshoot much more quickly, even with monolithic enterprise apps. This is only true if you can mimic the “big picture” behavior of the app. In this case, it was read a file, write the file, and then insert it in the database from the same location you wrote the file on the client.<\/p>\n
\r\nusing System.IO;\r\nusing System;\r\nusing System.Data.SqlClient;\r\n\r\n\/\/C:\\Windows\\Microsoft.NET\\Framework\\v4.0.30319\\csc.exe \r\n\r\nclass WriteTextFile {\r\n static void Main() {\r\n string[] lines = { \"One\", \"Two\", \"Three\" };\r\n System.IO.File.WriteAllLines(@\"\\\\cmhfiler2\\amspromo\\sdh_poc.txt\", lines);\r\n SqlConnection conn = new SqlConnection(\"Data Source=dbserver;Initial Catalog=dbname;Integrated Security=True;\");\r\n conn.Open();\r\n SqlCommand command = new SqlCommand(\"select * from openrowset(bulk '\\\\\\\\cmhfiler2\\\\amspromo\\\\sdh_poc.txt', single_clob)\", conn);\r\n SqlDataReader rdr = command.ExecuteReader(); \r\n while (rdr.Read()) { \r\n Console.WriteLine(\"Line is \" + rdr[0]);\r\n } \r\n }\r\n}\r\n<\/pre>\n","protected":false},"excerpt":{"rendered":"We had a job that an enterprise software vendor was running that failed on permissions denied. They asked us to open the file share to anyone without a password. Our awesome SQL Server DBA pushed back, thankfully. We came up…<\/p>\n