Topic: Could not find server ' xxxxxxxx ' in sys.servers at start from dtsx a packet
There is a procedure on 1. Procedure addresses to the table allocated on 2. The link is adjusted like correctly, and
If to launch procedure with 1, it fulfills, no errors are present. And here from dtsx a packet through normal execute sql task she starts to swear that 2 in sys.servers is not present.
The most ridiculous that refers to the same server other procedure in the same packet which, truth, is launched through C# a step, and fulfills without abuse. To rewrite the given start similarly on # it is possible, but what for? Nobody faced? More low a screen of a falling step.