Errors creating push subscriptions...

Hi All,
Had to recreate our SQLServer instance after a rebulid of
the server. Unfortuantely I was not able to
recreate/reload a backup so had to create from scratch.
In trying to setup replication I have the following error
message trying to create a push subscriptions:
SQL Server Enterprise Manager encountered errors creating
push subscriptions for the following Subscribers:
'FHMYDATABSE: Error 14053: Cannot load the DLL
replincrementlsn extended procedure, or one of the DLLs it
references. Reason: 126(The specified module could not be
found.).
The subscription could not be updated at this time.
The subscription could not be created.'
Any ideas? I tried locating the extended proc mention but
no luck. Any help very much appreciated, as I've had this
problem for about 2 weeks now and the powers that bey want
a swift fix! Thanks...
Davej
Dave,
perhaps your service pack failed to fully install. Have a look at sqlsp.log
file from the c:\windows directory this might shed some light on any failed
actions during the sp installation.
HTH,
Paul Ibison
|||Thanks Paul for the note. I re-ran the sp update and it
must of cured something because the first error has gone
but I get the following!
FHMYDATABASE: Error 515: Cannot insert the value NULL
into column 'step_name', table 'msdb.dbo.sysjobsteps';
column does not allow nulls. INSERT fails.
why? any ideas?
Cheers...

>--Original Message--
>Dave,
>perhaps your service pack failed to fully install. Have a
look at sqlsp.log
>file from the c:\windows directory this might shed some
light on any failed
>actions during the sp installation.
>HTH,
>Paul Ibison
>
>.
>
|||Dave,do you have any remaining subscriptions/jobs from the previous
implementation of replication perhaps? You might try running
sp_remopvedbreplication on the databases involved prior to setting it up
again. If there are any orphaned records in the table
MSreplication_subscriptions on the subscriber database then these can be
deleted. After that, refresh the jobs folder and then implement as per
normal.
HTH,
Paul Ibison
|||Hi Paul,
Did what you suggested. Went right back to basics removing
replication from the database. Then went trough the
procedure using stored procs insetadt of EM. Came to
creating a push sub and got the following, bit more
detailed errors:
Server: Msg 515, Level 16, State 2, Procedure
sp_add_jobstep_internal, Line 129
Cannot insert the value NULL into column 'step_name',
table 'msdb.dbo.sysjobsteps'; column does not allow nulls.
INSERT fails.
The statement has been terminated.
Server: Msg 14266, Level 16, State 1, Procedure
sp_verify_jobstep, Line 46
The specified '@.step_id' is invalid (valid values are:
1..1).
Server: Msg 14070, Level 16, State 1, Procedure
sp_changesubstatus, Line 993
Could not update the distribution database subscription
table. The subscription status could not be changed.
Server: Msg 14057, Level 16, State 1, Procedure
sp_addsubscription, Line 971
The subscription could not be created.
the script is:
use qboard
go
/* adds a publication to the database*/
exec sp_addpublication @.publication = 'Q Published Data
(from Script)'
,@.sync_method = 'native'
,@.repl_freq = 'continuous'
,@.status = 'active'
,@.allow_push = 'true'
go
/* adds a subscription to the publication just defined */
exec sp_addsubscription @.publication = 'Q Published Data
(from Script)'
,@.subscriber = 'FHQDB'
,@.subscription_type = 'push'
go
Is there someting I'm missing?
Thanks for any insights...
Davej

>--Original Message--
>Dave,do you have any remaining subscriptions/jobs from
the previous
>implementation of replication perhaps? You might try
running
>sp_remopvedbreplication on the databases involved prior
to setting it up
>again. If there are any orphaned records in the table
>MSreplication_subscriptions on the subscriber database
then these can be
>deleted. After that, refresh the jobs folder and then
implement as per
>normal.
>HTH,
>Paul Ibison
>
>.
>
|||Davej,
there seems to be some parts of you script missing. Here is a script for
transactional replication of CustomerDemographics:
-- Enabling the replication database
use master
GO
exec sp_replicationdboption @.dbname = N'Northwind', @.optname = N'publish',
@.value = N'true'
GO
use [Northwind]
GO
-- Adding the transactional publication
exec sp_addpublication @.publication = N'Northwindcds', @.restricted =
N'false', @.sync_method = N'native', @.repl_freq = N'continuous', @.description
= N'Transactional publication of Northwind database from Publisher
PLL-DT-16.', @.status = N'active', @.allow_push = N'true', @.allow_pull =
N'true', @.allow_anonymous = N'false', @.enabled_for_internet = N'false',
@.independent_agent = N'false', @.immediate_sync = N'false', @.allow_sync_tran
= N'false', @.autogen_sync_procs = N'false', @.retention = 336,
@.allow_queued_tran = N'false', @.snapshot_in_defaultfolder = N'true',
@.compress_snapshot = N'false', @.ftp_port = 21, @.ftp_login = N'anonymous',
@.allow_dts = N'false', @.allow_subscription_copy = N'false',
@.add_to_active_directory = N'false', @.logreader_job_name =
N'PLL-DT-16-Northwind-4'
exec sp_addpublication_snapshot @.publication =
N'Northwindcds',@.frequency_type = 4, @.frequency_interval = 1,
@.frequency_relative_interval = 0, @.frequency_recurrence_factor = 1,
@.frequency_subday = 1, @.frequency_subday_interval = 0, @.active_start_date =
0, @.active_end_date = 0, @.active_start_time_of_day = 222700,
@.active_end_time_of_day = 0, @.snapshot_job_name =
N'PLL-DT-16-Northwind-Northwindcds-10'
GO
exec sp_grant_publication_access @.publication = N'Northwindcds', @.login =
N'BUILTIN\Administrators'
GO
exec sp_grant_publication_access @.publication = N'Northwindcds', @.login =
N'distributor_admin'
GO
exec sp_grant_publication_access @.publication = N'Northwindcds', @.login =
N'PLL-DT-16\xxx
GO
exec sp_grant_publication_access @.publication = N'Northwindcds', @.login =
N'domain\vvv'
GO
exec sp_grant_publication_access @.publication = N'Northwindcds', @.login =
N'sa'
GO
-- Adding the transactional articles
exec sp_addarticle @.publication = N'Northwindcds', @.article =
N'CustomerDemographics', @.source_owner = N'dbo', @.source_object =
N'CustomerDemographics', @.destination_table = N'CustomerDemographics', @.type
= N'logbased', @.creation_script = null, @.description = null,
@.pre_creation_cmd = N'drop', @.schema_option = 0x00000000000000F3, @.status =
16, @.vertical_partition = N'false', @.ins_cmd = N'CALL
sp_MSins_CustomerDemographics', @.del_cmd = N'CALL
sp_MSdel_CustomerDemographics', @.upd_cmd = N'MCALL
sp_MSupd_CustomerDemographics', @.filter = null, @.sync_object = null,
@.auto_identity_range = N'false'
GO
-- Adding the transactional subscription
exec sp_addsubscription @.publication = N'Northwindcds', @.article = N'all',
@.subscriber = N'PLL-DT-16', @.destination_db = N'testrep', @.sync_type =
N'automatic', @.update_mode = N'read only', @.offloadagent = 0,
@.dts_package_location = N'distributor'
GO
HTH,
Paul Ibison
|||Paul,
with these stored procs, do you need to specify all the
prameters or can some be defaulted? I'll use your example
as a template...
Thanx
davej
>--Original Message--
>Davej,
>there seems to be some parts of you script missing. Here
is a script for
>transactional replication of CustomerDemographics:
>-- Enabling the replication database
>use master
>GO
>exec sp_replicationdboption @.dbname = N'Northwind',
@.optname = N'publish',
>@.value = N'true'
>GO
>use [Northwind]
>GO
>-- Adding the transactional publication
>exec sp_addpublication @.publication = N'Northwindcds',
@.restricted =
>N'false', @.sync_method = N'native', @.repl_freq =
N'continuous', @.description
>= N'Transactional publication of Northwind database from
Publisher
>PLL-DT-16.', @.status = N'active', @.allow_push = N'true',
@.allow_pull =
>N'true', @.allow_anonymous = N'false',
@.enabled_for_internet = N'false',
>@.independent_agent = N'false', @.immediate_sync =
N'false', @.allow_sync_tran
>= N'false', @.autogen_sync_procs = N'false', @.retention =
336,
>@.allow_queued_tran = N'false', @.snapshot_in_defaultfolder
= N'true',
>@.compress_snapshot = N'false', @.ftp_port = 21, @.ftp_login
= N'anonymous',
>@.allow_dts = N'false', @.allow_subscription_copy =
N'false',
>@.add_to_active_directory = N'false', @.logreader_job_name =
>N'PLL-DT-16-Northwind-4'
>exec sp_addpublication_snapshot @.publication =
>N'Northwindcds',@.frequency_type = 4, @.frequency_interval
= 1,
>@.frequency_relative_interval = 0,
@.frequency_recurrence_factor = 1,
>@.frequency_subday = 1, @.frequency_subday_interval = 0,
@.active_start_date =
>0, @.active_end_date = 0, @.active_start_time_of_day =
222700,
>@.active_end_time_of_day = 0, @.snapshot_job_name =
>N'PLL-DT-16-Northwind-Northwindcds-10'
>GO
>exec sp_grant_publication_access @.publication =
N'Northwindcds', @.login =
>N'BUILTIN\Administrators'
>GO
>exec sp_grant_publication_access @.publication =
N'Northwindcds', @.login =
>N'distributor_admin'
>GO
>exec sp_grant_publication_access @.publication =
N'Northwindcds', @.login =
>N'PLL-DT-16\xxx
>GO
>exec sp_grant_publication_access @.publication =
N'Northwindcds', @.login =
>N'domain\vvv'
>GO
>exec sp_grant_publication_access @.publication =
N'Northwindcds', @.login =
>N'sa'
>GO
>-- Adding the transactional articles
>exec sp_addarticle @.publication = N'Northwindcds',
@.article =
>N'CustomerDemographics', @.source_owner = N'dbo',
@.source_object =
>N'CustomerDemographics', @.destination_table =
N'CustomerDemographics', @.type
>= N'logbased', @.creation_script = null, @.description =
null,
>@.pre_creation_cmd = N'drop', @.schema_option =
0x00000000000000F3, @.status =
>16, @.vertical_partition = N'false', @.ins_cmd = N'CALL
>sp_MSins_CustomerDemographics', @.del_cmd = N'CALL
>sp_MSdel_CustomerDemographics', @.upd_cmd = N'MCALL
>sp_MSupd_CustomerDemographics', @.filter = null,
@.sync_object = null,
>@.auto_identity_range = N'false'
>GO
>-- Adding the transactional subscription
>exec sp_addsubscription @.publication = N'Northwindcds',
@.article = N'all',
>@.subscriber = N'PLL-DT-16', @.destination_db = N'testrep',
@.sync_type =
>N'automatic', @.update_mode = N'read only', @.offloadagent
= 0,
>@.dts_package_location = N'distributor'
>GO
>
>HTH,
>Paul Ibison
>
>.
>
|||Dave,
the vast majority can be missed out - too many to mention, but details in
BOL (see sp_addpublication, sp_addarticle). You could get EM to generate the
script from another server if you restore your database and create the
publication there, and want to use scripts.
Regards,
Paul Ibison

errors 17825 17059

I have a box with three instances on it one instance is getting the following
messages,
2004-09-23 14:06:58.55 server Error: 17825, Severity: 18, State: 4
2004-09-23 14:06:58.55 server Could not close Net-Library ''..
2004-09-23 14:06:58.55 server Error: 17059, Severity: 18, State: 0
2004-09-23 14:06:58.55 server Operating system error 10093: Either the
application has not called WSAStartup, or WSAStartup failed...
It seems remote logins will not connect but local logins will work. The only
why I found to correct this is stop/start the sql service for the instance.
These errors have just recently started and I am not aware of any changes
made or software installed on this box. I have not found much information on
these errors. Has any seen this before? What did you do to correct?
Thanks,
Dave
I don't know anything specific about the last 2 errors. The first (10093)
indicates that "server" has a socket problem. Specifically, the instance
failed to initialize the winsock library prior to attempting to utilize any
socket functions. That would explain why remote users can't connect. Don't
know what the solution is - the problem appears to lie in the networking
layer (perhaps a configuration issue).
"daproud" <daproud@.discussions.microsoft.com> wrote in message
news:82D2DE52-6F07-4BBF-805C-9D7898D36F40@.microsoft.com...
> I have a box with three instances on it one instance is getting the
following
> messages,
> 2004-09-23 14:06:58.55 server Error: 17825, Severity: 18, State: 4
> 2004-09-23 14:06:58.55 server Could not close Net-Library ''..
> 2004-09-23 14:06:58.55 server Error: 17059, Severity: 18, State: 0
> 2004-09-23 14:06:58.55 server Operating system error 10093: Either the
> application has not called WSAStartup, or WSAStartup failed...
> It seems remote logins will not connect but local logins will work. The
only
> why I found to correct this is stop/start the sql service for the
instance.
> These errors have just recently started and I am not aware of any changes
> made or software installed on this box. I have not found much information
on
> these errors. Has any seen this before? What did you do to correct?
> Thanks,
> Dave

error:26 Error Locating Server/Instance Specified

I am having trouble connecting to Sql Server 2005 Express from asp.net
2.0 app on Windows Server 2003. I am using Sql Server Authentication,
and I tried the below article's suggestions a number of times. When I
login to to the machine, and login, I am able to get authenticated.
However, when I debug my application, I get the error below. Do I have
to give the sql server authenticaed account I created certain
permissions? Whould I set a port, and use the ipaddress rather than
the server name? Any suggestions would be greatly appreciated.
http://support.microsoft.com/kb/914277
My Error:
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)
My Connection String:
<add key="ConnectionString"
value="server=MyServerName;uid=MyUserName;pwd=MyPasswd;database=MyDB"/>On Feb 1, 5:20=A0pm, carlos <carlosubu...@.gmail.com> wrote:
> I am having trouble connecting to Sql Server 2005 Express from asp.net
> 2.0 app on Windows Server 2003. I am using Sql Server Authentication,
> and I tried the below article's suggestions a number of times. When I
> login to to the machine, and login, I am able to get authenticated.
> However, when I debug my application, I get the error below. Do I have
> to give the sql server authenticaed account I created certain
> permissions? Whould I set a port, and use the ipaddress rather than
> the server name? Any suggestions would be greatly appreciated.
> http://support.microsoft.com/kb/914277
> My Error:
> 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)
> My Connection String:
> =A0<add key=3D"ConnectionString"
> value=3D"server=3DMyServerName;uid=3DMyUserName;pwd=3DMyPasswd;database=3D=MyDB"/>
Update:
I changed the connection string to use the ipaddress, and a port that
I set in the TCPIP settings, and now i'm getting the below message:
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: TCP Provider, error: 0 - No connection could
be made because the target machine actively refused it.)
I'm thinking this may be a permission problem'|||Hi Carlos,
By default, SQL Server 2005 Express, Evaluation, and Developer editions
allow local client connections only. Enterprise, Standard, and Workgroup
editions also listen for remote client connections over TCP/IP.
you ned to enable Remote Connections option using
Surface Area Configuration for Services and Connections (Remote Connections)
- Database Engine
You must restart the Database Engine instance's service to apply changes.
Regards,
Amol R. Lembhe
"carlos" wrote:
> On Feb 1, 5:20 pm, carlos <carlosubu...@.gmail.com> wrote:
> > I am having trouble connecting to Sql Server 2005 Express from asp.net
> > 2.0 app on Windows Server 2003. I am using Sql Server Authentication,
> > and I tried the below article's suggestions a number of times. When I
> > login to to the machine, and login, I am able to get authenticated.
> > However, when I debug my application, I get the error below. Do I have
> > to give the sql server authenticaed account I created certain
> > permissions? Whould I set a port, and use the ipaddress rather than
> > the server name? Any suggestions would be greatly appreciated.
> >
> > http://support.microsoft.com/kb/914277
> >
> > My Error:
> >
> > 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)
> >
> > My Connection String:
> > <add key="ConnectionString"
> > value="server=MyServerName;uid=MyUserName;pwd=MyPasswd;database=MyDB"/>
> Update:
> I changed the connection string to use the ipaddress, and a port that
> I set in the TCPIP settings, and now i'm getting the below message:
> 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: TCP Provider, error: 0 - No connection could
> be made because the target machine actively refused it.)
> I'm thinking this may be a permission problem'
>