(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

---

%1 is not a valid WIN32 application

We've recently installed SQL SP4 on one of our servers and are experiencing
the following problem:
SQLSERVERAGENT fails to start after the service pack has been installed with
error:
%1 is not a valid WIN32 application
The system log reports pretty much the same error.
We had to resort to uninstalling SQL server completely. Reinstalling SQL
server (and applying sp3a) works fine and SQLSERVERAGENT starts without any
problems.
Applying sp4 (and rebooting) results in the same error.
Please let me know if you are able to assist with this.Hi
Did you check out:
http://support.microsoft.com/default.aspx?scid=kb;en-us;812486
John
"Reuben Rinquest" wrote:
> We've recently installed SQL SP4 on one of our servers and are experiencing
> the following problem:
> SQLSERVERAGENT fails to start after the service pack has been installed with
> error:
> %1 is not a valid WIN32 application
> The system log reports pretty much the same error.
> We had to resort to uninstalling SQL server completely. Reinstalling SQL
> server (and applying sp3a) works fine and SQLSERVERAGENT starts without any
> problems.
> Applying sp4 (and rebooting) results in the same error.
> Please let me know if you are able to assist with this.
>|||Thank you John, This solution worked
"John Bell" wrote:
> Hi
> Did you check out:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;812486
> John
> "Reuben Rinquest" wrote:
> > We've recently installed SQL SP4 on one of our servers and are experiencing
> > the following problem:
> >
> > SQLSERVERAGENT fails to start after the service pack has been installed with
> > error:
> > %1 is not a valid WIN32 application
> > The system log reports pretty much the same error.
> > We had to resort to uninstalling SQL server completely. Reinstalling SQL
> > server (and applying sp3a) works fine and SQLSERVERAGENT starts without any
> > problems.
> >
> > Applying sp4 (and rebooting) results in the same error.
> >
> > Please let me know if you are able to assist with this.
> >
> >

%1 is not a valid WIN32 application

We've recently installed SQL SP4 on one of our servers and are experiencing
the following problem:
SQLSERVERAGENT fails to start after the service pack has been installed with
error:
%1 is not a valid WIN32 application
The system log reports pretty much the same error.
We had to resort to uninstalling SQL server completely. Reinstalling SQL
server (and applying sp3a) works fine and SQLSERVERAGENT starts without any
problems.
Applying sp4 (and rebooting) results in the same error.
Please let me know if you are able to assist with this.
Hi
Did you check out:
http://support.microsoft.com/default...b;en-us;812486
John
"Reuben Rinquest" wrote:

> We've recently installed SQL SP4 on one of our servers and are experiencing
> the following problem:
> SQLSERVERAGENT fails to start after the service pack has been installed with
> error:
> %1 is not a valid WIN32 application
> The system log reports pretty much the same error.
> We had to resort to uninstalling SQL server completely. Reinstalling SQL
> server (and applying sp3a) works fine and SQLSERVERAGENT starts without any
> problems.
> Applying sp4 (and rebooting) results in the same error.
> Please let me know if you are able to assist with this.
>
|||Thank you John, This solution worked
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> Did you check out:
> http://support.microsoft.com/default...b;en-us;812486
> John
> "Reuben Rinquest" wrote:

%1 is not a valid WIN32 application

We've recently installed SQL SP4 on one of our servers and are experiencing
the following problem:
SQLSERVERAGENT fails to start after the service pack has been installed with
error:
%1 is not a valid WIN32 application
The system log reports pretty much the same error.
We had to resort to uninstalling SQL server completely. Reinstalling SQL
server (and applying sp3a) works fine and SQLSERVERAGENT starts without any
problems.
Applying sp4 (and rebooting) results in the same error.
Please let me know if you are able to assist with this.Hi
Did you check out:
http://support.microsoft.com/defaul...kb;en-us;812486
John
"Reuben Rinquest" wrote:

> We've recently installed SQL SP4 on one of our servers and are experiencin
g
> the following problem:
> SQLSERVERAGENT fails to start after the service pack has been installed wi
th
> error:
> %1 is not a valid WIN32 application
> The system log reports pretty much the same error.
> We had to resort to uninstalling SQL server completely. Reinstalling SQL
> server (and applying sp3a) works fine and SQLSERVERAGENT starts without an
y
> problems.
> Applying sp4 (and rebooting) results in the same error.
> Please let me know if you are able to assist with this.
>|||Thank you John, This solution worked
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> Did you check out:
> http://support.microsoft.com/defaul...kb;en-us;812486
> John
> "Reuben Rinquest" wrote:
>