error creating publication

When I am in my publications folder and I attempt to add
a new publication, I get... 'Error 5: [SQL-DMO]Code
Execution exception: EXCEPTION_ACCESS_VIOLATION' after I
click next for the first time. If I click OK in the
error box, there are no publication databases listed.
HELP!!!!
Some times EM gets confused with all the caching it does.
Can you try to create the publication using the stored procedures?
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"larry" <anonymous@.discussions.microsoft.com> wrote in message
news:0af901c48b82$7daf3420$a501280a@.phx.gbl...
> When I am in my publications folder and I attempt to add
> a new publication, I get... 'Error 5: [SQL-DMO]Code
> Execution exception: EXCEPTION_ACCESS_VIOLATION' after I
> click next for the first time. If I click OK in the
> error box, there are no publication databases listed.
> HELP!!!!
>
sql

Error creating new push subscription after deleting the existing o

I created a transactional replication publication and pushed a subscriber,
and that works fine. I deleted existing push subscription in the publisher
with enterprise manager, and also deleted automatically generated replication
jobs related to that push subscription. I noticed that the push subscription
was not automatically deleted in the subscriber as it should. Moreover, when
I created a new push subscription with the same article, I encountered an
error. The error message is as following.
Subscriptions were created successfully at the following subscribers.
…
SQL Server Enterprise manager could not start the snapshot agent.
Error 14262:the specified @.job_id … does not exist.
Please help.
The error indicates that a replication agent job was deleted accidentally.
When this issue occurs, the most efficient way would be rebuilding the
replication from scratch.
Sincerely,
William Wang
Microsoft Online Partner Support
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
This posting is provided "AS IS" with no warranties, and confers no rights.

Error Creating a New Publication

When Attempting to set up replication on my SQL server 2005 server, I right
click and select new publication and imediately get the following error
message:
SQL Server is unable to connect to server 'spi-svr6'. (New Publication Wizard)
For help, click:
http://go.microsoft.com/fwlink?ProdN...t&LinkId=20476
===================================
SQL Server replication requires the actual server name to make a connection
to the server. Connections through a server alias, IP address, or any other
alternate name are not supported. Specify the actual server name,
'SPI-SVR203'. (Replication.Utilities)
Program Location:
at
Microsoft.SqlServer.Management.UI.ReplicationSqlCo nnection.CheckServerAlias(ServerConnection conn)
at Microsoft.SqlServer.Management.UI.ReplicationSqlCo nnection.Open()
at
Microsoft.SqlServer.Management.UI.CreatePublicatio nWizard.PrepareToShow()
The help link provides nothing on this and I have been unable to locate any
info on other user sites. I am at a loss on what the communication problem
may be as the replication wizzard does not even begin.
Any help would be appreciated
"Lance" wrote:

> When Attempting to set up replication on my SQL server 2005 server, I right
> click and select new publication and imediately get the following error
> message:
> SQL Server is unable to connect to server 'spi-svr6'. (New Publication Wizard)
> --
> For help, click:
> http://go.microsoft.com/fwlink?ProdN...t&LinkId=20476
> ===================================
> SQL Server replication requires the actual server name to make a connection
> to the server. Connections through a server alias, IP address, or any other
> alternate name are not supported. Specify the actual server name,
> 'SPI-SVR203'. (Replication.Utilities)
> --
> Program Location:
> at
> Microsoft.SqlServer.Management.UI.ReplicationSqlCo nnection.CheckServerAlias(ServerConnection conn)
> at Microsoft.SqlServer.Management.UI.ReplicationSqlCo nnection.Open()
> at
> Microsoft.SqlServer.Management.UI.CreatePublicatio nWizard.PrepareToShow()
> The help link provides nothing on this and I have been unable to locate any
> info on other user sites. I am at a loss on what the communication problem
> may be as the replication wizzard does not even begin.
> Any help would be appreciated
|||If you look at management studio and check the name of the server at the top
of the tree
that is the name under which the server is registered...
Also do a sp_helpserver query to determine the name corresponding to id 0
the registered name should be the same as that for id 0 (which normally is the
name of the server where SQL is installed.
"Lance" wrote:

> When Attempting to set up replication on my SQL server 2005 server, I right
> click and select new publication and imediately get the following error
> message:
> SQL Server is unable to connect to server 'spi-svr6'. (New Publication Wizard)
> --
> For help, click:
> http://go.microsoft.com/fwlink?ProdN...t&LinkId=20476
> ===================================
> SQL Server replication requires the actual server name to make a connection
> to the server. Connections through a server alias, IP address, or any other
> alternate name are not supported. Specify the actual server name,
> 'SPI-SVR203'. (Replication.Utilities)
> --
> Program Location:
> at
> Microsoft.SqlServer.Management.UI.ReplicationSqlCo nnection.CheckServerAlias(ServerConnection conn)
> at Microsoft.SqlServer.Management.UI.ReplicationSqlCo nnection.Open()
> at
> Microsoft.SqlServer.Management.UI.CreatePublicatio nWizard.PrepareToShow()
> The help link provides nothing on this and I have been unable to locate any
> info on other user sites. I am at a loss on what the communication problem
> may be as the replication wizzard does not even begin.
> Any help would be appreciated
|||Thanks for great help gopal!
"Lance" wrote:

> When Attempting to set up replication on my SQL server 2005 server, I right
> click and select new publication and imediately get the following error
> message:
> SQL Server is unable to connect to server 'spi-svr6'. (New Publication Wizard)
> --
> For help, click:
> http://go.microsoft.com/fwlink?ProdN...t&LinkId=20476
> ===================================
> SQL Server replication requires the actual server name to make a connection
> to the server. Connections through a server alias, IP address, or any other
> alternate name are not supported. Specify the actual server name,
> 'SPI-SVR203'. (Replication.Utilities)
> --
> Program Location:
> at
> Microsoft.SqlServer.Management.UI.ReplicationSqlCo nnection.CheckServerAlias(ServerConnection conn)
> at Microsoft.SqlServer.Management.UI.ReplicationSqlCo nnection.Open()
> at
> Microsoft.SqlServer.Management.UI.CreatePublicatio nWizard.PrepareToShow()
> The help link provides nothing on this and I have been unable to locate any
> info on other user sites. I am at a loss on what the communication problem
> may be as the replication wizzard does not even begin.
> Any help would be appreciated
|||gopal,
You are right on target. The helpserver SP returns the old server name.
Will the drop/add sp's fix this?
"gopal" wrote:
[vbcol=seagreen]
> If you look at management studio and check the name of the server at the top
> of the tree
> that is the name under which the server is registered...
> Also do a sp_helpserver query to determine the name corresponding to id 0
> the registered name should be the same as that for id 0 (which normally is the
> name of the server where SQL is installed.
> "Lance" wrote:
|||You can use the @.@.SERVERNAME global variable or the
SERVERPROPERTY('ServerName') function in SQL Server to find the network name
of the computer running SQL Server. The ServerName property of the
SERVERPROPERTY function automatically reports the change in the network name
of the computer when you restart the computer and the SQL Server service.
The @.@.SERVERNAME global variable retains the original SQL Server computer
name until the SQL Server name is manually reset.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)

Error Count not obtain information about Windows NT group/user

We receive an error as the server attempts to create a publication. The user
has permissions on both the server as an administrator and as an sa. This
conflict should not occur. Can anyone help to explain this? It has been
suggested we go to SP4. There are concerns about firmware and blue screening
on the primary server at this time may preclude sp4 as an option.
Regards,
Jamie
Is there a possibility that when an Enterprise 2005 version of SQL encounters
a Standard version 2000, that this error pops up?
Regards,
Jamie
"thejamie" wrote:

> We receive an error as the server attempts to create a publication. The user
> has permissions on both the server as an administrator and as an sa. This
> conflict should not occur. Can anyone help to explain this? It has been
> suggested we go to SP4. There are concerns about firmware and blue screening
> on the primary server at this time may preclude sp4 as an option.
> --
> Regards,
> Jamie