(local) old db 4 sql server suddenly fails

Several DTS packages that use (local) as the server name
in the ms ole db providor for sql server suddenly broke.
They'd worked well for years. The existing connection
using (local) won't find the default instance on the
machine. A new connect using (local) works file. SQL
Server is 2k enterprise, sp 3a (818). OS is w2k
5.00.2195. Doesn't matter if the connection
authentication is W2k authenticated or standardHi,
It seems like the netbios name might have changed and connection still
resolving the (local) to old netbios.
Try using Select @.@.SERVERNAME and/or Select SERVERPROPERTY('servername')
thanks,
ashish
"bob b" <anonymous@.discussions.microsoft.com> wrote in message
news:6d6d01c3e69d$d7b3bac0$a401280a@.phx.gbl...

quote:

---

> Several DTS packages that use (local) as the server name
> in the ms ole db providor for sql server suddenly broke.
> They'd worked well for years. The existing connection
> using (local) won't find the default instance on the
> machine. A new connect using (local) works file. SQL
> Server is 2k enterprise, sp 3a (818). OS is w2k
> 5.00.2195. Doesn't matter if the connection
> authentication is W2k authenticated or standard

---

"An error occurred during local report processing" for Preview

My report worked fine for a while, but suddenly I started getting the following errors for Preview:

An error occurred during local report processing.

An error has occurred during report processing.

Index was outside the bounds of the array.

I restarted VS, then rebooted my machine and the problem persists.Everything including the report posted to the server works fine. It is just the Preview of this report does not work any more.Preview of other reports work fine.

Any tip to resolve this problem would be greatly appreciated.

Is this the same error that is found in the log?|||

Simone, sorry for my ignorance. Could you tell me which log you referred to?

|||

I renamed the report's *.rdl.data to *.rdl.data.old following a tip from another thread (http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=284496&SiteID=1) and the problem was solved.

I do not fully understand this. It seems the problem was caused by a VS bug.