Merge Control Synchronization Problem

Hi Guys - I have been using the Merge Control ActiveX successfully for
some time. However, one client has found a problem synchronizing. Here is
the relavent piece of code:
agent.Publisher = "MyServer\InstanceName";
agent.Distributor = agent.Publisher;
agent.DistributorNetwork = TCPIP_SOCKETS;
agent.PublisherNetwork = TCPIP_SOCKETS;
agent.PublisherAddress = "192.168.1.100\InstanceName,2763";
agent.DistributorAddress =
"192.168.1.100\InstanceName,2763";
This is a Merge replication with pull anonymous subscriptions. The
Publisher and Distributor are on the same server.
I am using the PublisherAddress because I need to specify the port.
The error the client gets is the following:
[vbcol=seagreen]
If we try anything else for the publisher name such as
"192.168.1.100\InstanceName" or even the fully qualified name of the server,
it says:
[vbcol=seagreen]
valid Publisher'
Now, we checked and double-checked the settings. We can log in fine to
the publisher and subscribers. As a matter of fact, we were able to
subscribe just fine.
I tested the same scenario with my computers and it works fine for me.
What could cause it to say that The process could not connect to
Distributer?
Is the Publisher name always "ServerName\InstanceName"?
Any help will be apreciated,
Thanks,
Maer
I think you are having name resolution problems from this client. Can this
client ping the publisher/distributor by IP?
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Maer" <maer@.auditleverage.com> wrote in message
news:%23EO95jlPGHA.2080@.TK2MSFTNGP09.phx.gbl...
> Hi Guys - I have been using the Merge Control ActiveX successfully for
> some time. However, one client has found a problem synchronizing. Here is
> the relavent piece of code:
> agent.Publisher = "MyServer\InstanceName";
> agent.Distributor = agent.Publisher;
> agent.DistributorNetwork = TCPIP_SOCKETS;
> agent.PublisherNetwork = TCPIP_SOCKETS;
> agent.PublisherAddress = "192.168.1.100\InstanceName,2763";
> agent.DistributorAddress =
> "192.168.1.100\InstanceName,2763";
> This is a Merge replication with pull anonymous subscriptions. The
> Publisher and Distributor are on the same server.
> I am using the PublisherAddress because I need to specify the port.
> The error the client gets is the following:
>
> If we try anything else for the publisher name such as
> "192.168.1.100\InstanceName" or even the fully qualified name of the
> server, it says:
> valid Publisher'
> Now, we checked and double-checked the settings. We can log in fine to
> the publisher and subscribers. As a matter of fact, we were able to
> subscribe just fine.
> I tested the same scenario with my computers and it works fine for me.
> What could cause it to say that The process could not connect to
> Distributer?
> Is the Publisher name always "ServerName\InstanceName"?
> Any help will be apreciated,
> Thanks,
> Maer
>
>
>
|||Yes, he has pinged the IP and it responds ok. Also, we can connect fine
to SQL Server (through our application) on the publisher/distributor using
"MyServer\InstanceName" or "IP\InstanceName".
BTW, the publisher/distributor is running on a Windows 2003 Server.
Maer
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:%23gnkoQmPGHA.2912@.tk2msftngp13.phx.gbl...
>I think you are having name resolution problems from this client. Can this
>client ping the publisher/distributor by IP?
> --
> Hilary Cotter
> Director of Text Mining and Database Strategy
> RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
> This posting is my own and doesn't necessarily represent RelevantNoise's
> positions, strategies or opinions.
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "Maer" <maer@.auditleverage.com> wrote in message
> news:%23EO95jlPGHA.2080@.TK2MSFTNGP09.phx.gbl...
>

Merge cells vertically

Hello
Is it possible to merge cells of a table control vertically?
See the second column in this example:
+--+--+
| | |
+--+ |
| | |
+--+--+
Ciao,
JensJens,
I tried doing that a few times with no success, I don't believe it can
be done any simple way. Unless someone has some insider information :)

Merge Agent and ActiveX Parameters for Replication

Hi All,
I currently use the SQL Merge ActiveX control to perform synchronization
from my application. In SQL Enterprise Manager, you can configure the Merge
Agent Parameters (-KeepMessageAliveInterval, -QueryTimeout, etc.), but you
can also do this from the ActiveX control. My question is, which one takes
precedent? If I configure values in the Merge Agent's Parameters, then
configure different values in the ActiveX control, which are used? Does the
server take precedence? I would think the ActiveX control's parameters
would be used, but I just want to make sure.
Regards,
Brad
you can specify which profile you want to use. If you try to right click on
your agent, when it is created by an activeX control you will find that you
are unable to set these properties.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Brad M." <anonymous@.discussions.microsoft.com> wrote in message
news:OEZ57eopFHA.2504@.tk2msftngp13.phx.gbl...
> Hi All,
> I currently use the SQL Merge ActiveX control to perform synchronization
> from my application. In SQL Enterprise Manager, you can configure the
Merge
> Agent Parameters (-KeepMessageAliveInterval, -QueryTimeout, etc.), but you
> can also do this from the ActiveX control. My question is, which one
takes
> precedent? If I configure values in the Merge Agent's Parameters, then
> configure different values in the ActiveX control, which are used? Does
the
> server take precedence? I would think the ActiveX control's parameters
> would be used, but I just want to make sure.
> Regards,
> Brad
>

Memory leak when using ReportViewer control

If you create a form with nothing other than the ReportViewer control on it,
then open that form from another form and close it, about 50K appears to be
used each time. If you run an actual report in the control, then the memory
increases in relation to the size of the report. I have a report that when
run consumes about 130MB of memory. When I close the form, the memory usage
in my app only drops to about 80MB. If I then open the form again and run
the report again, the memory usage jumps up to over 170MB and when the form
is closed it drops back down to about 130MB. These numbers change depending
on the report you run and the amount of data and number of controls on the
report, but there is a definite leak when using the ReportViewer control.
Other people have seen the leak as well:
http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=449474&SiteID=1
I can not find an answer anywhere, someone at Microsoft really needs to
adress this issue.
Thank you!
BrianI wonder if it is a true leak. Memory management under dotnet can be quite
delayed.
I am using the control as well (winform), I'll do some looking into this.
--
Bruce Loehle-Conger
MVP SQL Server Reporting Services
"Brian Adams" <BrianAdams@.discussions.microsoft.com> wrote in message
news:1A9A0F7D-5BDF-491F-9851-2B48EEF6C244@.microsoft.com...
> If you create a form with nothing other than the ReportViewer control on
> it,
> then open that form from another form and close it, about 50K appears to
> be
> used each time. If you run an actual report in the control, then the
> memory
> increases in relation to the size of the report. I have a report that
> when
> run consumes about 130MB of memory. When I close the form, the memory
> usage
> in my app only drops to about 80MB. If I then open the form again and run
> the report again, the memory usage jumps up to over 170MB and when the
> form
> is closed it drops back down to about 130MB. These numbers change
> depending
> on the report you run and the amount of data and number of controls on the
> report, but there is a definite leak when using the ReportViewer control.
> Other people have seen the leak as well:
> http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=449474&SiteID=1
> I can not find an answer anywhere, someone at Microsoft really needs to
> adress this issue.
> Thank you!
> Brian
>|||Thanks Bruce. I even went so far as to call System.GC.Collect() and
System.GC.WaitForPendingFinalizers() to ensure the garbage collector ran and
memory was being cleaned up. It didn't have any effect on the results I was
seeing.
I had no references to the form left, and no references to any of the
objects the form referenced, so the calls to Collect should have been able to
clean up all memory because there were no remaining references to any of the
instantiated objects. The reports were all RDLC (client side) based, so
everything was completely disconnected and isolated to the form itself. When
it went away, so should have all the memory that was allocated during its
lifetime. Unless there is some caching going on in the runtime I'm not aware
of. If this were the case, I would have expected the memory usage to level
off at some point, but it seemed to continue climbing each time I created the
form/ran report/closed form. These results were based on initial Task
Manager observations, and then perfmon monitoring.
"Bruce L-C [MVP]" wrote:
> I wonder if it is a true leak. Memory management under dotnet can be quite
> delayed.
> I am using the control as well (winform), I'll do some looking into this.
> --
> Bruce Loehle-Conger
> MVP SQL Server Reporting Services
> "Brian Adams" <BrianAdams@.discussions.microsoft.com> wrote in message
> news:1A9A0F7D-5BDF-491F-9851-2B48EEF6C244@.microsoft.com...
> > If you create a form with nothing other than the ReportViewer control on
> > it,
> > then open that form from another form and close it, about 50K appears to
> > be
> > used each time. If you run an actual report in the control, then the
> > memory
> > increases in relation to the size of the report. I have a report that
> > when
> > run consumes about 130MB of memory. When I close the form, the memory
> > usage
> > in my app only drops to about 80MB. If I then open the form again and run
> > the report again, the memory usage jumps up to over 170MB and when the
> > form
> > is closed it drops back down to about 130MB. These numbers change
> > depending
> > on the report you run and the amount of data and number of controls on the
> > report, but there is a definite leak when using the ReportViewer control.
> >
> > Other people have seen the leak as well:
> > http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=449474&SiteID=1
> >
> > I can not find an answer anywhere, someone at Microsoft really needs to
> > adress this issue.
> >
> > Thank you!
> > Brian
> >
>
>