That looks a lot like a website - so this won't work:
Process.Start("C:/erp_documents/local/daily process/uploaddocuments/2016/6/UPLF1606230135.pdf")
It may appear to in development, but it won't in production.
C# code is always executed on the Server, not the Client, and only has access to Server disks, never the Client HDD. So depending on where you are storing the PDF it may not be possible at all.
Because the
Process.Start
code is executed on the Server, the process is started on the Server - so it attempts to use the system default file association to open the file and display it at the Server - the Client can't see it. It appears to work in development because they are the same machine, and you can't tell which started the process. But in production it fails.
The second problem is that even if the file is located on the server, your website may not have access to the folder containing it: IIS does not run under your user id, so it does not "inherit" your user access permissions. You need to check the folder chain and ensure that the correct privileges have been given.
You can display a PDF at the client (depending on the client and which browser he uses, some may treat it as a download rather than a page) by using the Response object:
Response.ClearHeaders();
Response.ContentType = "application/pdf"
Response.Clear()
Response.AppendHeader("Content-Disposition", "inline")
Response.TransmitFile(pathToFile)
Response.End()