Network Path Not Found

Question

0.00/5 (No votes)

See more:

Hi,

I have an internet hosted database I need to connect to.

SSMS connects and executes without any problems.

But .Net and SSRS all get "Network Path Not Found" when running code against the server.

Any thoughts on why there would be different behaviours for the various products?

Posted 27-Apr-15 21:53pm

Stephen Hewison

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

OriginalGriff · Answer 1 · 2015-04-27T22:04:00

Solution 1

Check your connection strings. Assuming you are testing all three apps on the same PC, that's the only real difference. If you are testing them on different PCs, then you need to look a lot more closely at exactly what each package is being asked to do!

Posted 27-Apr-15 22:04pm

OriginalGriff

Comments

Stephen Hewison 28-Apr-15 4:19am

If only it was that simple! Yes I'm testing on the same PC and the connection strings are fine. The server's recently been moved but the not NAT address hasn't changed and I copied the server/port from the same DB which drives the connection string on the .Net and SSRS side.

Stephen Hewison 28-Apr-15 4:35am

This problem was stemming from a seed of bad info. Found the bad info and the problem is now solved. Was not a technical issue.

OriginalGriff 28-Apr-15 4:46am

Don't you love it when that happens? :laugh: