JSPtechserv
asked on
Workflow Server (2008) can not access shares on File Server (2003)
Hello,
My workflow server (running Server 2008) continually has issues connecting to shared folders on my file server (running Server 2003).
The workflow server has one of the shared folders from the file server mapped. Then, suddenly, it can not longer access it. I get this error:
"(\\servername\shared folder) is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions. NO MORE INTERNAL FILE IDENTIFIERS AVAILABLE."
My administrative account DOES have access to this server/share/folder and I do not get this message when accessing our secondary file server (also running Server 2003). After restarting the workflow server, I can access the shared folder/drive for a while and then suddenly I can not and get the above error. I have checked the Event Logs on both servers and see nothing out of the ordinary and not warnings or errors (well, the usual for print spoolers but nothing else).
Please provide some assistance and if you need anything further I will provide it quickly. Thanks!
My workflow server (running Server 2008) continually has issues connecting to shared folders on my file server (running Server 2003).
The workflow server has one of the shared folders from the file server mapped. Then, suddenly, it can not longer access it. I get this error:
"(\\servername\shared folder) is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions. NO MORE INTERNAL FILE IDENTIFIERS AVAILABLE."
My administrative account DOES have access to this server/share/folder and I do not get this message when accessing our secondary file server (also running Server 2003). After restarting the workflow server, I can access the shared folder/drive for a while and then suddenly I can not and get the above error. I have checked the Event Logs on both servers and see nothing out of the ordinary and not warnings or errors (well, the usual for print spoolers but nothing else).
Please provide some assistance and if you need anything further I will provide it quickly. Thanks!
ASKER
Hello alkhalighi,
1 - The servers use DNS to connect
2 - I just restarted the server so I can not tell you this piece of information yet but a ping is possible (tried that before)
3 - Again, I just restarted but I will try this if/when the problem occurs again
4 - No, no other machines have the same problem connecting to the file server, only my workflow server. It appears to be an issue ONLY between my workflow server and my primary file server.
Would clearing the DNS cache on the workflow server accomplish anything? Initially it appears to be either a problem with DNS or DFS
1 - The servers use DNS to connect
2 - I just restarted the server so I can not tell you this piece of information yet but a ping is possible (tried that before)
3 - Again, I just restarted but I will try this if/when the problem occurs again
4 - No, no other machines have the same problem connecting to the file server, only my workflow server. It appears to be an issue ONLY between my workflow server and my primary file server.
Would clearing the DNS cache on the workflow server accomplish anything? Initially it appears to be either a problem with DNS or DFS
ASKER
Hello again,
The error occurred again.
I can not connect to any shares on the file server using windows explorer HOWEVER using an IP address in windows Explorer I can access the shares! I can also ping the file server. I can also Remote Desktop Connect to the File server from the workflow server.
I will be restarting the server service on the file server tomorrow morning to see if that resolves any issues. Right now it appears to be a DNS issue. Keep in mind that other servers can see and access my primary file server shares just fine. It is only the workflow server that sometimes can not (quid pro quo: This workflow server has been online for six months and has not had this error before).
The error occurred again.
I can not connect to any shares on the file server using windows explorer HOWEVER using an IP address in windows Explorer I can access the shares! I can also ping the file server. I can also Remote Desktop Connect to the File server from the workflow server.
I will be restarting the server service on the file server tomorrow morning to see if that resolves any issues. Right now it appears to be a DNS issue. Keep in mind that other servers can see and access my primary file server shares just fine. It is only the workflow server that sometimes can not (quid pro quo: This workflow server has been online for six months and has not had this error before).
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Marek1712,
Yes, we are running Enfocus Switch on our workflow server. This program heavily relies on DNS and opens/moves several files at once. It does this by "chopping" each file up and renaming the parts and then reassembling them at the destination. I will check with their maintenance team to see if this could cause FID issues. Thanks!
Alkhalighi,
I restarted the Server Service on our file server and that seemed to do the trick right away. I am monitoring it to make sure the DNS connection between the two does not drop again but that may have been the solution.
Yes, we are running Enfocus Switch on our workflow server. This program heavily relies on DNS and opens/moves several files at once. It does this by "chopping" each file up and renaming the parts and then reassembling them at the destination. I will check with their maintenance team to see if this could cause FID issues. Thanks!
Alkhalighi,
I restarted the Server Service on our file server and that seemed to do the trick right away. I am monitoring it to make sure the DNS connection between the two does not drop again but that may have been the solution.
ASKER
Hello All,
It appears that restarting the Server Service fixes the issues for about three hours or so and then it reverts back to not being able to see the shared folder.
Marek1712,
What am I looking for in ProcMon that would show a memory leak?
It appears that restarting the Server Service fixes the issues for about three hours or so and then it reverts back to not being able to see the shared folder.
Marek1712,
What am I looking for in ProcMon that would show a memory leak?
Maybe not a memory leak, but number of files being opened. But since you know the application that MAY BE responsible I'd wait for the support's response. In the meantime I'd set a scheduled task to restart the service hourly.
Another thing to check is HANDLE.EXE - it should show you all the open handles (the same can be achieved in ProcExp).
Another thing to check is HANDLE.EXE - it should show you all the open handles (the same can be achieved in ProcExp).
hmm ... there is one more thing .. do you have the same issue with explorer from a different machine once your workflow server fails to connect ?
as a temporary workaround , could you use IP address instead of DNS name in your application ?
as a temporary workaround , could you use IP address instead of DNS name in your application ?
do you run Symantec anti virus on File server ? any security application ?
ASKER
Yes, but Symantec is not causing the issue.
I have used the IP as a temporary work around.
I do not have the same error on any other machine using Explorer, only the workflow server
I have used the IP as a temporary work around.
I do not have the same error on any other machine using Explorer, only the workflow server
Okay , then .. next question ; when the issue happens , are you able to ping DNS name ? if not .. what is DNS setting on workflow server , is it connecting to the same DNS server as other machines ?
It's possible that for some reason DNS server blocks this machine every once in a while. have you check DNS server log files ? do you have security applications on DNS servers ?
as a troubleshooting step ; you can change host file on workflow server and hard code DNS name and IP address of your file server in there so that workflow server doesn't go to DNS server to resolve that name and it always refers to local host file . this will tell you if something goes wrong with DNS handling .
It's possible that for some reason DNS server blocks this machine every once in a while. have you check DNS server log files ? do you have security applications on DNS servers ?
as a troubleshooting step ; you can change host file on workflow server and hard code DNS name and IP address of your file server in there so that workflow server doesn't go to DNS server to resolve that name and it always refers to local host file . this will tell you if something goes wrong with DNS handling .
ASKER
It was a memory leak on Switch 11 Upgrade 3 as noted by the manufacturer. I rolled back to Switch 11 U2 and it is working fine. THanks!
1- does your workflow server use IP address or DNS name to connect to 2003 ?
2- when it fails to connect , before you restart the service , are you able to connect to the same share using windows explorer ? can you access using IP address ? can you ping 2003
from 2008 when share is not accessible ?
3- next time this issue happens , try restarting "server service " on 2003 machine.
4- Any other machine\server has the same issue connecting to 2003 server ?