Monday, March 26, 2012
push subscription: production environment
application which is accessing the database?
You can, but its not advisable. When you send your subscription the data in
the tables is replaced unless you are doing the nosync option. This
replacement can involve dropping the table and recreating it.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
"Robert A. DiFrancesco" <bob.difrancesco@.comcash.com> wrote in message
news:e8qmPZP%23EHA.1392@.tk2msftngp13.phx.gbl...
> may I push a subscription to a server while that 'machine' is running the
> application which is accessing the database?
>
push snapshot
networks. both machines can ping eachother using there machine names. I setup
the publication and the distributor on the push server and generate a
snapshot. I then run the distributor but it fails to connect to the
subscriber.
thanks for the help.
Mark
You need to ensure the @.@.servername of the subscriber is how the
publisher/distributor refer to it and vice versa. If you have to use IP
address, you can setup client side alias on the distributor that maps the IP
address to the @.@.servername of the subscriber
“This posting is provided "AS IS" with no warranties, and confers no rights.”
"ACDMark" wrote:
> Hi I'm trying to setup a push replication between 2 servers on different
> networks. both machines can ping eachother using there machine names. I setup
> the publication and the distributor on the push server and generate a
> snapshot. I then run the distributor but it fails to connect to the
> subscriber.
> thanks for the help.
> Mark
|||hi ,
be sure that your sql agent services is
running on a domain account
that has permission to your snapshot folder
and the database
thanks,
joey
"ACDMark" wrote:
> Hi I'm trying to setup a push replication between 2 servers on different
> networks. both machines can ping eachother using there machine names. I setup
> the publication and the distributor on the push server and generate a
> snapshot. I then run the distributor but it fails to connect to the
> subscriber.
> thanks for the help.
> Mark
Monday, March 12, 2012
Pull Subscription, Merge Replication
I was trying to pull a subscription to an MSDE machine(subscriber)
from a sql server 2000 machine acting as the publisher and
distributor. when I configure for the pull, it generates a snapshot
immediately which is successfully completed. But then, the pull
actually never happens and I get the message saying the pull
subscription has 'Never Started'. I found that, if the name of the job
exceeds 100 characters, then the problem arises, but my job name is
very small and hence, I dont think that is my problem. I tried to
manually start and reinitialize all the agents, but that does not
solve my problem.
Can someone suggest what else could be done?
Thanks
PS.
you will get long job names when you are using a pull subscription, and
short names when you are doing a push subscription.
can you enable logging to see what it reports. Follow the steps in this kb
article to enable logging.
http://support.microsoft.com/default...b;EN-US;312292
Hilary Cotter
Looking for a book on SQL Server replication?
http://www.nwsu.com/0974973602.html
"ps" <ps_sr2001@.yahoo.com> wrote in message
news:1a7be36d.0406131046.2aa8d35e@.posting.google.c om...
> Hi,
> I was trying to pull a subscription to an MSDE machine(subscriber)
> from a sql server 2000 machine acting as the publisher and
> distributor. when I configure for the pull, it generates a snapshot
> immediately which is successfully completed. But then, the pull
> actually never happens and I get the message saying the pull
> subscription has 'Never Started'. I found that, if the name of the job
> exceeds 100 characters, then the problem arises, but my job name is
> very small and hence, I dont think that is my problem. I tried to
> manually start and reinitialize all the agents, but that does not
> solve my problem.
> Can someone suggest what else could be done?
> Thanks
> PS.
|||Hi Hilary,
Thanks for the response. Well, I went to the agent, right clicked on
it and went to 'Agent Properties'. under 'Steps' tab, I found 'Run
Agent' for which I clicked on Edit and appended '-Output
C:\Repl_out.txt -Outputverboselevel 2'.
Upon starting the agent, I am not finding any such file or if I create
the file myself, the file is empty.
Also, I am getting an error in the subscriber under subscriptions
saying "The process could not connect to Distributor 'Name'. Login
failed for user". The subscriber is listed under the 'Remote Servers'
of the publisher. Is there anything else that could be done?
Thanks,
PS
"Hilary Cotter" <hilaryk@.att.net> wrote in message news:<#0A$ylbUEHA.4064@.TK2MSFTNGP11.phx.gbl>...[vbcol=seagreen]
> you will get long job names when you are using a pull subscription, and
> short names when you are doing a push subscription.
> can you enable logging to see what it reports. Follow the steps in this kb
> article to enable logging.
> http://support.microsoft.com/default...b;EN-US;312292
>
> --
> Hilary Cotter
> Looking for a book on SQL Server replication?
> http://www.nwsu.com/0974973602.html
>
> "ps" <ps_sr2001@.yahoo.com> wrote in message
> news:1a7be36d.0406131046.2aa8d35e@.posting.google.c om...
|||Hi,
From the verbose mode 2, I got this output. This is the last part of
the log:
A snapshot of 1 article(s) was generated.
Disconnecting from Publisher '********'
Microsoft SQL Server Snapshot Agent 8.00.760
Copyright (c) 2000 Microsoft Corporation
Microsoft SQL Server Replication Agent: *************-Repl-5
Connecting to Distributor '*********'
Connecting to Publisher '*************'
But in the subscriber database, under subscriptions, I got a message
stating:
"SQL Server Agent could not access the replication agent. Use the
DCOMCNFG utility".
I have SP3a installed on both publisher and subscriber, hence it
should not be the bug because of it.
Upon refreshing the same, I got a message stating - "The step did not
generate any output. The step failed".
Any ideas or suggestions will be greatly appreciated!
Thanks,
PS.
"Hilary Cotter" <hilaryk@.att.net> wrote in message news:<#0A$ylbUEHA.4064@.TK2MSFTNGP11.phx.gbl>...[vbcol=seagreen]
> you will get long job names when you are using a pull subscription, and
> short names when you are doing a push subscription.
> can you enable logging to see what it reports. Follow the steps in this kb
> article to enable logging.
> http://support.microsoft.com/default...b;EN-US;312292
>
> --
> Hilary Cotter
> Looking for a book on SQL Server replication?
> http://www.nwsu.com/0974973602.html
>
> "ps" <ps_sr2001@.yahoo.com> wrote in message
> news:1a7be36d.0406131046.2aa8d35e@.posting.google.c om...
pull subscription chaning identity seed/increment
table on the client machine with increment and seed as -1000 and -20.
The table is created fine. But when I execture the first synchrnoize
data from the client, the table is changed to be 1, 2, which is what the
server has. I am using SQL-DMO on the client with the following code:
With myMergeObj
.Distributor = inxRS.Globals.gServer
.DistributorLogin = "inxsql"
.DistributorPassword = "inxsql4u"
.DistributorSecurityMode = SECURITY_TYPE.DB_AUTHENTICATION
.DistributorNetwork = NETWORK_TYPE.TCPIP_SOCKETS
.DistributorAddress = inxRS.Globals.gServerIP
.Publisher = inxRS.Globals.gServer
.PublisherDatabase = in_comp
.Publication = Trim(in_comp) & "RS"
.PublisherLogin = "inxsql"
.PublisherPassword = "inxsql4u"
.PublisherSecurityMode = SECURITY_TYPE.DB_AUTHENTICATION
.PublisherNetwork = NETWORK_TYPE.TCPIP_SOCKETS
.PublisherAddress = inxRS.Globals.gServerIP
.Subscriber = Trim(Environment.MachineName)
.SubscriberDatabase = in_comp
.SubscriberSecurityMode = SECURITY_TYPE.NT_AUTHENTICATION
.SubscriptionType = SUBSCRIPTION_TYPE.ANONYMOUS
.SubscriptionName = Trim(in_comp) & "RS"
.HostName = Trim(inxRS.Globals.gLogin)
.ExchangeType = EXCHANGE_TYPE.BIDIRECTIONAL
.ReinitializeSubscription(false)
End With
myMergeObj.Initialize()
myMergeObj.Run()
myMergeObj.Terminate()
I can't tell if it is a problem in the pull or in how the publication
was/is setup.
Thanks.
Darin
*** Sent via Developersdex http://www.codecomments.com ***
I removed the reinit statement and I still have the same problem.
Darin
*** Sent via Developersdex http://www.codecomments.com ***
|||FIXED IT.
Darin
*** Sent via Developersdex http://www.codecomments.com ***
Friday, March 9, 2012
Publishing Web Application
Hello to everybody.
I got a problem like this:
I developped a project using Visual Studio 2005 Standard Edition on a XP pro x64 Machine using a developpemet data area on a SQL 2005 Express Edition.
Everything is ok, even the user and profile management. But when I try to publish my application on IIS (we're talking about a little Intranet), I get my problems. I think is important to say that the server is a Windows Server 2003 and data (database reproduced as a backup of the developpement one) are under an SQL 2005 Standard. The strange thing is that by publishing the "site" VS create a DB under SQL Std named with the path of local ASPNETDB.MDF.
I can reach everything, all data are ok, but when I pass the login page going to main menu on my web-application, I get this 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)
I think the problem is SQL STD and the fact that it's not "able" to manage MDF files.
I even tried to re-map the SQL DB (named simply as ASPNETDB on the SQL std) by adjusting the web.config file on connection type and user and password to reach the DB ASPNETDB but it does't work anyway.
Can anybody solve my problem?
Thank You
Can you post your connection string please|||This first is the original connection string in web.config defined in the developpement area:
<add name="ASPNETDBConnectionString1" connectionString="Data Source=.\SQLEXPRESS;AttachDbFilename=|DataDirectory|\ASPNETDB.MDF;Integrated Security=True;User Instance=True" providerName="System.Data.SqlClient"/>
This one is the connection to the server (SQL STD):
<add name="ASPNETDBConnectionString1" connectionString="Data Source=SERVER\SQLSERVER;Initial Catalog=ASPNETDB;Persist Security Info=True;User ID=user;Password=password" providerName="System.Data.SqlClient"/>
Thank You.
Mauro
Publishing reports to different versions
I have Visual Studio 2005 and Reporting Services 2005 on my client development machine.
I want to publish the reports to an SQL Server 2000 with Reporting Services 2000 server, is this possible?
I get the following error message:
The report definition is not valid. Please verify that the report definition uses the current report definition namespace (i.e. ‘http://schemas.microsoft.com/sqlserver/reporting/2003/10/reportdefinition’). (rsNotACurrentReportDefinition) Get Online Help
Thanks.
Bruce
Unfortunately, you will not be able to use the 2005 report designer to publish directly to a 2000 report server. This is due to the fact that the RDL's (Report Definitions) created are different between Report Server versions. You can however use the 2000 report designer to publish to a 2005 server, as it support auto-upgrade of the reports.
Thanks, Jon
Saturday, February 25, 2012
Publication script error
I am creating Publication through sql script. I have created Publication on
my machine using wizard and after that I created the script for the
publication. When I am running this script on another sql server it is giving
me an error saying Distributor not configured properly. What I need to do to
remove this error? Can this problem be solved by running some sql script?
Becoz I am creating all this through Installshield. So I need the script of
this. Please Help...
Sounds like replication is not installed on this server. Go to tools,
replication, enable replication and follow the prompts accepting the
defaults.
"Subin" <Subin@.discussions.microsoft.com> wrote in message
news:567DC900-D413-4769-916C-E24FF90B9A0E@.microsoft.com...
> Hello,
> I am creating Publication through sql script. I have created Publication
> on
> my machine using wizard and after that I created the script for the
> publication. When I am running this script on another sql server it is
> giving
> me an error saying Distributor not configured properly. What I need to do
> to
> remove this error? Can this problem be solved by running some sql script?
> Becoz I am creating all this through Installshield. So I need the script
> of
> this. Please Help...
Monday, February 20, 2012
Public key Token = b77a5c561934e089
I have installed my program and SQL server 2K5 on the server.
But when I try to run it (from he client machine)I get the following error :
It works fine on the SERVER
The appication attempted to perform an operation not allowed by the security policy.
The operation required the security Exception. To grant this application the required permission
please contact your systems Administrator or use the Microsoft .NET security policy administration tool.
If you click Bla,bla,bla
Request for the permision of type System.Data.SqlClient.SqlClient
Permission, System.Data Version - 1.0.5000.0. Cultre = neutral.
Public key Token = b77a5c561934e089
did you ever solve this as I now have the same issue|||
I've done some checking and this seems to be related to the fact that you're apparently running your application from a network share. When you run a managed application from the network, you need to either trust the network or trust the assembly by adjusting the security policy on the local computer. Check out the Code Access Security information for more details.
The alternative to adjusting the security policy is to install the application onto the local computer via either ClickOnce or MSI. More details on the these tools can be found at:
For .NET 1.1 see
Smart Client Architecture and Design Guide
Chapter 7 — Deploying and Updating Smart Client Applications
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnpag/html/scag-ch07.asp
For .NET 2.0 see
ClickOnce
http://msdn.microsoft.com/clickonce
Regards,
Mike Wachal
SQL Express team