cant drop rowguid or msrepl_tran_version

sql2k sp3
Ive got these columns on a previously replicated table and
I cant get rid of them. I went so far as to disable
Publisheing from the box and still no luck. I also removed
the default values and the indexes from them. I also tried
sp_repldropcolumn. Any ideas?
TIA, ChrisR
Chris,
there is a stored procedure to do this called sp_MSunmarkreplinfo which
takes a tablename as a parameter. Alternatively, setting replinfo to 0 in
sysobjects for the particular table should do it. Finally, running
sp_removedbreplication can be used to remove all traces of replication in
the subscriber database, but obviously must only be done if this database is
not also configured as a publisher.
HTH,
Paul Ibison
|||I appreciate the help. I had already run the
sp_MSunmarkreplinfo. I have dropped the Subscription db's.
And I ran sp_removedbreplication on the Publisher. I still
cant drop them. Any other ideas?

>--Original Message--
>Chris,
>there is a stored procedure to do this called
sp_MSunmarkreplinfo which
>takes a tablename as a parameter. Alternatively, setting
replinfo to 0 in
>sysobjects for the particular table should do it.
Finally, running
>sp_removedbreplication can be used to remove all traces
of replication in
>the subscriber database, but obviously must only be done
if this database is
>not also configured as a publisher.
>HTH,
>Paul Ibison
>
>.
>

can't disable a job in sql2k

Hi all,
I have a job in sql2k box. After the box network name changed. I can't do
any modification to that job anymore.
It says, error 14274 can't update, add or delete a job(or steps or schedule)
that originated from an MSX server.the job was not saved.
ThanksThis problem could be attributable to the originating_server now differing
from the actual server name.
UPDATE msdb..sysjobs SET Originating_Server = Servername
The Microsoft KBase resolution is here :-
http://support.microsoft.com/defaul...b;en-us;Q281642
HTH. Ryan
"mecn" <mecn2002@.yahoo.com> wrote in message
news:evm1n0sEGHA.2320@.TK2MSFTNGP11.phx.gbl...
> Hi all,
> I have a job in sql2k box. After the box network name changed. I can't do
> any modification to that job anymore.
> It says, error 14274 can't update, add or delete a job(or steps or
> schedule) that originated from an MSX server.the job was not saved.
> Thanks
>|||Thats an easy one:
http://support.microsoft.com/defaul...kb;en-us;281642
HTH, jens Suessmeyer.|||It worked.
Thanks lot.
MECN
"Ryan" <Ryan_Waight@.nospam.hotmail.com> wrote in message
news:%23g%235A3sEGHA.216@.TK2MSFTNGP15.phx.gbl...
> This problem could be attributable to the originating_server now differing
> from the actual server name.
> UPDATE msdb..sysjobs SET Originating_Server = Servername
> The Microsoft KBase resolution is here :-
> http://support.microsoft.com/defaul...b;en-us;Q281642
> --
> HTH. Ryan
>
> "mecn" <mecn2002@.yahoo.com> wrote in message
> news:evm1n0sEGHA.2320@.TK2MSFTNGP11.phx.gbl...
>|||In addition to the other posts:
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/
Blog: http://solidqualitylearning.com/blogs/tibor/
"mecn" <mecn2002@.yahoo.com> wrote in message news:evm1n0sEGHA.2320@.TK2MSFTNGP11.phx.gbl...[v
bcol=seagreen]
> Hi all,
> I have a job in sql2k box. After the box network name changed. I can't do
> any modification to that job anymore.
> It says, error 14274 can't update, add or delete a job(or steps or schedul
e)
> that originated from an MSX server.the job was not saved.
> Thanks
>[/vbcol]

can't disable a job in sql2k

Hi all,
I have a job in sql2k box. After the box network name changed. I can't do
any modification to that job anymore.
It says, error 14274 can't update, add or delete a job(or steps or schedule)
that originated from an MSX server.the job was not saved.
Thanks
This problem could be attributable to the originating_server now differing
from the actual server name.
UPDATE msdb..sysjobs SET Originating_Server = Servername
The Microsoft KBase resolution is here :-
http://support.microsoft.com/default...;en-us;Q281642
HTH. Ryan
"mecn" <mecn2002@.yahoo.com> wrote in message
news:evm1n0sEGHA.2320@.TK2MSFTNGP11.phx.gbl...
> Hi all,
> I have a job in sql2k box. After the box network name changed. I can't do
> any modification to that job anymore.
> It says, error 14274 can't update, add or delete a job(or steps or
> schedule) that originated from an MSX server.the job was not saved.
> Thanks
>
|||Thats an easy one:
http://support.microsoft.com/default...b;en-us;281642
HTH, jens Suessmeyer.
|||It worked.
Thanks lot.
MECN
"Ryan" <Ryan_Waight@.nospam.hotmail.com> wrote in message
news:%23g%235A3sEGHA.216@.TK2MSFTNGP15.phx.gbl...
> This problem could be attributable to the originating_server now differing
> from the actual server name.
> UPDATE msdb..sysjobs SET Originating_Server = Servername
> The Microsoft KBase resolution is here :-
> http://support.microsoft.com/default...;en-us;Q281642
> --
> HTH. Ryan
>
> "mecn" <mecn2002@.yahoo.com> wrote in message
> news:evm1n0sEGHA.2320@.TK2MSFTNGP11.phx.gbl...
>
|||In addition to the other posts:
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/
Blog: http://solidqualitylearning.com/blogs/tibor/
"mecn" <mecn2002@.yahoo.com> wrote in message news:evm1n0sEGHA.2320@.TK2MSFTNGP11.phx.gbl...
> Hi all,
> I have a job in sql2k box. After the box network name changed. I can't do
> any modification to that job anymore.
> It says, error 14274 can't update, add or delete a job(or steps or schedule)
> that originated from an MSX server.the job was not saved.
> Thanks
>

can't disable a job in sql2k

Hi all,
I have a job in sql2k box. After the box network name changed. I can't do
any modification to that job anymore.
It says, error 14274 can't update, add or delete a job(or steps or schedule)
that originated from an MSX server.the job was not saved.
ThanksThis problem could be attributable to the originating_server now differing
from the actual server name.
UPDATE msdb..sysjobs SET Originating_Server = Servername
The Microsoft KBase resolution is here :-
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q281642
--
HTH. Ryan
"mecn" <mecn2002@.yahoo.com> wrote in message
news:evm1n0sEGHA.2320@.TK2MSFTNGP11.phx.gbl...
> Hi all,
> I have a job in sql2k box. After the box network name changed. I can't do
> any modification to that job anymore.
> It says, error 14274 can't update, add or delete a job(or steps or
> schedule) that originated from an MSX server.the job was not saved.
> Thanks
>|||Thats an easy one:
http://support.microsoft.com/default.aspx?scid=kb;en-us;281642
HTH, jens Suessmeyer.|||It worked.
Thanks lot.
MECN
"Ryan" <Ryan_Waight@.nospam.hotmail.com> wrote in message
news:%23g%235A3sEGHA.216@.TK2MSFTNGP15.phx.gbl...
> This problem could be attributable to the originating_server now differing
> from the actual server name.
> UPDATE msdb..sysjobs SET Originating_Server = Servername
> The Microsoft KBase resolution is here :-
> http://support.microsoft.com/default.aspx?scid=kb;en-us;Q281642
> --
> HTH. Ryan
>
> "mecn" <mecn2002@.yahoo.com> wrote in message
> news:evm1n0sEGHA.2320@.TK2MSFTNGP11.phx.gbl...
>> Hi all,
>> I have a job in sql2k box. After the box network name changed. I can't do
>> any modification to that job anymore.
>> It says, error 14274 can't update, add or delete a job(or steps or
>> schedule) that originated from an MSX server.the job was not saved.
>> Thanks
>|||In addition to the other posts:
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/
Blog: http://solidqualitylearning.com/blogs/tibor/
"mecn" <mecn2002@.yahoo.com> wrote in message news:evm1n0sEGHA.2320@.TK2MSFTNGP11.phx.gbl...
> Hi all,
> I have a job in sql2k box. After the box network name changed. I can't do
> any modification to that job anymore.
> It says, error 14274 can't update, add or delete a job(or steps or schedule)
> that originated from an MSX server.the job was not saved.
> Thanks
>

cant connect to SQL2K running on W2K3SVR but can connect to SQL2K running W2KSVR with same

Hi,
I can't connect using an OLE DB connection string to SQL2K Server (SP3)
running on a Windows2003 Server, but using the same connection string (with
the address changed of course), I can connect to SQL2K Server (SP3) running
on Windows2000 Server.
I figure it must be a security issue on the W2K3 box. The logins and users
were created correctly with the correct passwords as I can connect to the
W2K3 box via Enterprise Manager just fine. The connection is set to TCP/IP
on port 1433 (default).
an example of my connection string (it is in a web application running on a
different server):
Application("dbconnstring") ="Provider=sqloledb;Data
Source=10.10.10.1;Network Library=DBMSSOCN;Initial Catalog=mydatabase;User
ID=mylogin;Password=mypassword;"
The only thing that changed is the IP address of the Win2003 server. I can
ping the server from either direction. I can scan port 1433 just fine with
a port scanner.
I am new to 2003 server, so I figure there must be a security setting
somewhere, but I haven't a clue where to look!
Any help would be appreciated!
TIA
Dave
.Hi Dave
> I can't connect using an OLE DB connection string to SQL2K Server (SP3)
> running on a Windows2003 Server, but using the same connection string
(with
> the address changed of course), I can connect to SQL2K Server (SP3)
running
> on Windows2000 Server.
> I figure it must be a security issue on the W2K3 box. The logins and
users
> were created correctly with the correct passwords as I can connect to the
> W2K3 box via Enterprise Manager just fine. The connection is set to
TCP/IP
> on port 1433 (default).
> an example of my connection string (it is in a web application running on
a
> different server):
> Application("dbconnstring") ="Provider=sqloledb;Data
> Source=10.10.10.1;Network Library=DBMSSOCN;Initial Catalog=mydatabase;User
> ID=mylogin;Password=mypassword;"
> The only thing that changed is the IP address of the Win2003 server. I
can
> ping the server from either direction. I can scan port 1433 just fine
with
> a port scanner.
> I am new to 2003 server, so I figure there must be a security setting
> somewhere, but I haven't a clue where to look!
>
Are you sure EM is connecting using TCP?
Can you connect locally using isql or isqlw to 127.0.0.1 ? (check that the
SQL Server client network utility on the server has TCP/IP as an enabled
protocol).
By port scanner, what do you mean? Are you scanning it on the server or from
outside the machine? Can you show that the server is listening on port 1433?
Check the SQL Server server network utility is listening on port 1433. Use
"netstat -a -n" (or "netsh interface ip show tcpconn") to look for an entry
like...
TCP 0.0.0.0:1433 0.0.0.0:0 LISTENING
Try telnetting to the port, eg "telnet 127.0.0.1 1433". If it's listening on
port 1433 you should get a blank telnet screen. If it's not you'll get an
error like "Connecting To 127.0.0.1...Could not open a connection to host on
port 1434 : Connect failed"
Try the above from a remote machine to see if there's an issue with
connecting remotely.
Run the SQL Server Profiler and check the Security Audit->Audit Login, Audit
Login Failed, Audit Logout events.
Kind Regards, Howard|||Hi again,
I tried telnetting both on the server and remotely and I get the blank
screen. The problem is OLE-DB does not work on Win2003. I can connect my
.Net apps just fine though through the SQL connector and Enterprise Manager.
I enabled DTC on the Win2003 box to see if that would help (but it did not
help, as I figured) and rebooted.
Somehow, OLE-DB requests are being blocked by a security setting deep within
the bowels of Windows 2003.
I must not be alone on this problem as a staff of MCSEs & MCDBAs are
scratching their heads at the hosting company (name withheld)!
Whilest I wait for them to figure it out, where in SQL profiler is the
"security audit"?
Dave
"dammit Jim, I'm just a country programmer!"
--
"Howard Long" <howard@.howardlongxxx.com> wrote in message
news:camggl$gqh$1@.sparta.btinternet.com...
> Hi Dave
> > I can't connect using an OLE DB connection string to SQL2K Server (SP3)
> > running on a Windows2003 Server, but using the same connection string
> (with
> > the address changed of course), I can connect to SQL2K Server (SP3)
> running
> > on Windows2000 Server.
> >
> > I figure it must be a security issue on the W2K3 box. The logins and
> users
> > were created correctly with the correct passwords as I can connect to
the
> > W2K3 box via Enterprise Manager just fine. The connection is set to
> TCP/IP
> > on port 1433 (default).
> >
> > an example of my connection string (it is in a web application running
on
> a
> > different server):
> >
> > Application("dbconnstring") ="Provider=sqloledb;Data
> > Source=10.10.10.1;Network Library=DBMSSOCN;Initial
Catalog=mydatabase;User
> > ID=mylogin;Password=mypassword;"
> >
> > The only thing that changed is the IP address of the Win2003 server. I
> can
> > ping the server from either direction. I can scan port 1433 just fine
> with
> > a port scanner.
> > I am new to 2003 server, so I figure there must be a security setting
> > somewhere, but I haven't a clue where to look!
> >
> Are you sure EM is connecting using TCP?
> Can you connect locally using isql or isqlw to 127.0.0.1 ? (check that the
> SQL Server client network utility on the server has TCP/IP as an enabled
> protocol).
> By port scanner, what do you mean? Are you scanning it on the server or
from
> outside the machine? Can you show that the server is listening on port
1433?
> Check the SQL Server server network utility is listening on port 1433. Use
> "netstat -a -n" (or "netsh interface ip show tcpconn") to look for an
entry
> like...
> TCP 0.0.0.0:1433 0.0.0.0:0 LISTENING
> Try telnetting to the port, eg "telnet 127.0.0.1 1433". If it's listening
on
> port 1433 you should get a blank telnet screen. If it's not you'll get an
> error like "Connecting To 127.0.0.1...Could not open a connection to host
on
> port 1434 : Connect failed"
> Try the above from a remote machine to see if there's an issue with
> connecting remotely.
> Run the SQL Server Profiler and check the Security Audit->Audit Login,
Audit
> Login Failed, Audit Logout events.
> Kind Regards, Howard
>|||"Dave" <dave(delete_this)@.miraclecatDELETETHISTOO.com> wrote in message
news:%23NhiEGuUEHA.2356@.TK2MSFTNGP10.phx.gbl...
> Hi again,
> I tried telnetting both on the server and remotely and I get the blank
> screen. The problem is OLE-DB does not work on Win2003. I can connect my
> .Net apps just fine though through the SQL connector and Enterprise
Manager.
> I enabled DTC on the Win2003 box to see if that would help (but it did not
> help, as I figured) and rebooted.
> Somehow, OLE-DB requests are being blocked by a security setting deep
within
> the bowels of Windows 2003.
> I must not be alone on this problem as a staff of MCSEs & MCDBAs are
> scratching their heads at the hosting company (name withheld)!
> Whilest I wait for them to figure it out, where in SQL profiler is the
> "security audit"?
When Profiler has opened, File->New->Trace, enter your details. In the
Events tab, add the Security Audit /Audit Login & Audit Login failed. The
trace will help you identify the fault.
I was wondering if it is trying to use integrated security to connect. Try
setting up an AD account mylogin/mypassword on the W2K3 server and retrying.
Alternatively it could be the other way around, and you are using SQL Server
authentication, in which case you should check that the login exists in SQL
Server.
Any error messages?
Regards, Howard

Cant connect SQL2K named instance using OLE DB

Hi,

I am having a hard time trying to connect to a remote SQL Server 2000 named
instance using an OLE DB connection, the computer I am trying to connect
from has SQL Server 7 installed, but MDAC 2.6 SP1 (which should be
sufficient?). Errormsg below:

Microsoft OLE DB Provider for SQL Server error '80004005'

[DBNETLIB][ConnectionOpen (Connect()).]SQL Server does not exist or access
denied.

/asp/test.asp, line 5

The remote server is listening on TCP/IP, port 1434

I am using a sql-login. The remote server is in mixed mode.

I've tried connect using Query Analyzer in order to troubleshoot the
problem, and came to the following conclusion:

- If i add an alias for the server in Client Network Configuration,
and configure the connection to use TCP/IP, 1434, then I'm able to
connect to the remote server using Query Analyzer. However,
my asp-page still won't work.

- If i don't add an alias, but run Client Network Utility and add
TCP/IP (port 1434) as first protocol, and Named Pipes second
protocol... then I am not able to connect using Query Analyzer or
the asp-page. How come?

The code in test.asp looks like this:
<%
dim objC
dim rs
Set objC = Server.CreateObject("ADODB.Connection")
objC.Open "Provider='SQLOLEDB.1';" & _
"Persist Security Info=True;" & _
"User ID='myusername';" & _
"Password='mypassword';" & _
"Initial Catalog=mydatabase;" & _
"Server=REMOTESERVER\INSTANCE;" & _
"Data source=REMOTE SERVER\INSTANCE"
objC.Execute "SELECT * FROM [dbo].[EverybodyListens_Employee] WHERE CGid =
'aviklund'"
%>

Some rows of the code above are wrapped.
REMOTESERVER is the remote server,
and INSTANCE is the instance name.

Thanks!

// BjrnThis http://msdn.microsoft.com/isapi/gosupport.asp?Target=/support/kb/articles/Q169/3/77.asp (KB Article) gives much insight to resolve the issue.

HTH