I'm using SQL Server 2008's Filestream functionality to store files. Our DB server is separate from our web server in production...
1. From time to time, we get this error : network path is not found.
2. This error does not happen in staging since we have our web and database on the same server.
3. I've put debug steps and I asked our hosting server if there's a network intermittent connectivity issue and they said there isn't.
4. Per this link, port 445 needs to be open and our hosting server said it's not open.
5. This is from our hosting server
After taking a look at your servers, there does not appear to be any networking related issues. We do see that your database server only has 3GB free on it. Once windows gets below 10% free, it can start to slow down while accessing the disk. Depending on timeouts, it could be affecting this procedure. The server started with 30 GB of storage. Windows and MsSQL will typically use 10-20 GB depending on options.
6. Should I ask the hosting server to do this?
Any ideas on what might be causing this? Should I have port 445 opened? I researched this a lot and I think Filestream is a good way to go. Not sure why we're getting the error from time to time. Is filestream good for same server? "FILESTREAM data can be stored only on local disk volumes"
The error is this:
at System.Data.SqlTypes.SqlFileStream.OpenSqlFileStream(String path, Byte transactionContext, FileAccess access, FileOptions options, Int64 allocationSize) at System.Data.SqlTypes.SqlFileStream..ctor(String path, Byte transactionContext, FileAccess access, FileOptions options, Int64 allocationSize) at System.Data.SqlTypes.SqlFileStream..ctor(String path, Byte transactionContext, FileAccess access) at UserControl_NonMemberFax.SaveLetterDatabase(Byte dataLetter, String fax, String patientId, Nullable`1 nonMemberProviderId) at UserControl_NonMemberFax.btnSubmit_onClick(Object sender, EventArgs e)========The network path was not found