Cannot edit jobs

i am get this error message every time I try to remove some old jobs that
were created on a different server:
error 14274: cannot add, update,or delete a job (or its step or
schedules) that originated from an msx server
What do I need to do to remove these jobs?
Either remove them from the master server. Or hack msdb..sysjobs (originating_server column to the
name for your server). Some info found here (adapt to your needs):
http://www.karaszi.com/SQLServer/inf...erver_name.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Takia" <Takia@.discussions.microsoft.com> wrote in message
news:527F2E42-BDF8-4968-B717-4BDA27347FDB@.microsoft.com...
>i am get this error message every time I try to remove some old jobs that
> were created on a different server:
> error 14274: cannot add, update,or delete a job (or its step or
> schedules) that originated from an msx server
> What do I need to do to remove these jobs?
>

Cannot edit jobs

i am get this error message every time I try to remove some old jobs that
were created on a different server:
error 14274: cannot add, update,or delete a job (or its step or
schedules) that originated from an msx server
What do I need to do to remove these jobs?Either remove them from the master server. Or hack msdb..sysjobs (originatin
g_server column to the
name for your server). Some info found here (adapt to your needs):
http://www.karaszi.com/SQLServer/in...server_name.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Takia" <Takia@.discussions.microsoft.com> wrote in message
news:527F2E42-BDF8-4968-B717-4BDA27347FDB@.microsoft.com...
>i am get this error message every time I try to remove some old jobs that
> were created on a different server:
> error 14274: cannot add, update,or delete a job (or its step or
> schedules) that originated from an msx server
> What do I need to do to remove these jobs?
>

Cannot edit jobs

i am get this error message every time I try to remove some old jobs that
were created on a different server:
error 14274: cannot add, update,or delete a job (or its step or
schedules) that originated from an msx server
What do I need to do to remove these jobs?Either remove them from the master server. Or hack msdb..sysjobs (originating_server column to the
name for your server). Some info found here (adapt to your needs):
http://www.karaszi.com/SQLServer/info_change_server_name.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Takia" <Takia@.discussions.microsoft.com> wrote in message
news:527F2E42-BDF8-4968-B717-4BDA27347FDB@.microsoft.com...
>i am get this error message every time I try to remove some old jobs that
> were created on a different server:
> error 14274: cannot add, update,or delete a job (or its step or
> schedules) that originated from an msx server
> What do I need to do to remove these jobs?
>

Cannot connect using sql authentication in query analyzer

I just moved a database from one sql server to another. Both use Windows
2000, sp4, build 2195. Both use SQL Server 7, but the old server uses
service pack 3 (7.00.961). the new server uses service pack 4 (7.00.1094).
I connect to the database in the old server without a problem. I connect to
the new server fine with NT authentication, or if I log in as sa with SQL
authentication, but if I log in as a different user with SQL authentication
on the new server, I get this message:
Unable to connect to server Enterprise3:
ODBC: Msg 0, Level 16, State 1
[Microsoft][ODBC SQL Server Driver][SQL Server]SqlDumpExceptionHandler:
Process 11 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOATION. SQL
Server is terminating this process.
Ooops - Just remembered one other piece that may be impartant: We were
swapping the two servers, so had to rename both. With SQL Server 7, that
means we had to do a mini-reinstall of the "corrupt" SQL Server. We've tried
to reapply the service packs and the hotfixes, but it will not allow it.
(Current installation is more recent.) This is not a problem with the SP3
server, but only with the sp4+ server.
"UWKC Admin" wrote:

> I just moved a database from one sql server to another. Both use Windows
> 2000, sp4, build 2195. Both use SQL Server 7, but the old server uses
> service pack 3 (7.00.961). the new server uses service pack 4 (7.00.1094).
> I connect to the database in the old server without a problem. I connect to
> the new server fine with NT authentication, or if I log in as sa with SQL
> authentication, but if I log in as a different user with SQL authentication
> on the new server, I get this message:
> Unable to connect to server Enterprise3:
> ODBC: Msg 0, Level 16, State 1
> [Microsoft][ODBC SQL Server Driver][SQL Server]SqlDumpExceptionHandler:
> Process 11 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOATION. SQL
> Server is terminating this process.
|||Hi
What do you call "mini-reinstall"? If you have problems, always do a full
install, anything else is not supported by Microsoft.
Regards
Mike
"UWKC Admin" wrote:
[vbcol=seagreen]
> Ooops - Just remembered one other piece that may be impartant: We were
> swapping the two servers, so had to rename both. With SQL Server 7, that
> means we had to do a mini-reinstall of the "corrupt" SQL Server. We've tried
> to reapply the service packs and the hotfixes, but it will not allow it.
> (Current installation is more recent.) This is not a problem with the SP3
> server, but only with the sp4+ server.
> "UWKC Admin" wrote:
|||Mike - Thanks for the question. When I say mini-reinstall, I mean the
reinstall that SQL Server demands we do after renaming a SQL Server 7.0
installation. It tells us something to the effect that that the
installstallation is bad and may have been tampered with, then tells us to
reinstall SQL Server. We do that, using the original SQL Server CD. I call
it a mini-install because it only takes a couple of minutes to complete.
"UWKC Admin" wrote:

> I just moved a database from one sql server to another. Both use Windows
> 2000, sp4, build 2195. Both use SQL Server 7, but the old server uses
> service pack 3 (7.00.961). the new server uses service pack 4 (7.00.1094).
> I connect to the database in the old server without a problem. I connect to
> the new server fine with NT authentication, or if I log in as sa with SQL
> authentication, but if I log in as a different user with SQL authentication
> on the new server, I get this message:
> Unable to connect to server Enterprise3:
> ODBC: Msg 0, Level 16, State 1
> [Microsoft][ODBC SQL Server Driver][SQL Server]SqlDumpExceptionHandler:
> Process 11 generated fatal exception c0000005 EXCEPTION_ACCESS_VIOATION. SQL
> Server is terminating this process.
|||Did you run sp_dropserver and sp_addserver after you
changed the server name and updated the registry with the
SQL Server CD (the process you refer to as a mini-reinstall
just updates the server name entries in the registry)?
e.g.
sp_dropserver 'YourOldServerName'
go
sp_addserver 'YourNewServerName', local
This part of the process just updates the server name in the
sysservers table. You should run in on both servers that you
renamed.
I'm not sure this will make any difference as I don't
remember anyone getting access violations if they miss any
of the steps in renaming a server...but worth a try.
-Sue
On Thu, 9 Dec 2004 11:33:06 -0800, "UWKC Admin"
<UWKCAdmin@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Mike - Thanks for the question. When I say mini-reinstall, I mean the
>reinstall that SQL Server demands we do after renaming a SQL Server 7.0
>installation. It tells us something to the effect that that the
>installstallation is bad and may have been tampered with, then tells us to
>reinstall SQL Server. We do that, using the original SQL Server CD. I call
>it a mini-install because it only takes a couple of minutes to complete.
>"UWKC Admin" wrote:

Cannot connect to sqlexpress from ssmse (ctp)

I have been using sqlexpress for several months and decided to upgrade the ssmse to the november ctp version. I uninstalled the old ssmse and installed the november release from ctp.

I verified that the tcp/ip and named pipes are enable in the config manager. I attempted using these connection strings:

\sqlexpress, (local)\sqlexpress, or server name\sqlexpress

All fail with the following message:

Cannot connect to WALLY1\sqlexpress

--
ADDITIONAL INFORMATION:

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=-1&LinkId=20476

BUTTONS:

OK

We need a little more information to troubleshoot your problem.

Are you running SSMSE and SQLExpress on the same machine? Are you able to connect to SQLExpress using SQLCMD?

Thanks,
Dan

|||Try to connect either with TCP/IP or named-pipes enabled and not with both the options enabled.
I have had this problem before and when used named-pipes alone it resolved the problem and ensure the ALIAS is defined properly and you can ping the server.|||

Are you running everything from the same machine or are you trying to connect to a remote SQL Server?

Cheers,
Dan