View Complete Post
I have a publication on SQL Server 2008 Standard Edition using merge replication. When I attempt to generate the initial snapshot, the snapshot agent appears to hang on the step "Setting up the publication for filtered articles." I
get a long (over 4 hour) series of messages: "The process is running and is waiting for a response from the server." I know something is happening server-side, as SQL Server and the snapshot agent use a lot of memory and max out one core's
This has me confused as the publication is not doing any filtering.
Even more confusing: I backed up the database and restored it onto my development-test system. I created the snapshot there, and it took under 10 minutes every time.
Any suggestions for investigating and resolving this?
I am using a Team Site template with a custom master page for my SharePoint site. I am now trying to setup a group of users that only have read access to the site. The site is not inheriting permissions from the parent site and the users are
setup with Site Visitor access on both the site and the customer master page. The problem I am running into is that when I try to access the site with one of the read only accounts, I receive an error that the current user's access is denied.
Am I missing some other areas where I should have changed permissions?
Is there a different way I should have done this?
Have I correctly understood that a snapshot is only required in a merge replication (pull) when the subscription is first created or reinitialized?
And that the publisher is re-generating those snapshots on some schedule, only to speed up to process if some subscribers need to be reinitialized?
I'm asking this because I intend to download the snapshot via ftp manually (inorder to use passive FTP-SSL, merge replication itself only supports active FTP). Since the MergeSubscriptionAgent.IsSnapshotRequired() method takes ages to return a result
(more than a minute ove local LAN), I'd like to skip that part and simply go ahead and download the snapshot when the subscription has not been created or is marked for reinitialization.
I need answers to the questions above, so that if I go down this route -> a couple of weeks in production I wouldn't run into trouble, because SQL requires a new snapshot to say validate data or something...
Here is the complete scenario :- SBS 2003 running Sql Server 2005 Standard, Merge Replication and Push Subscription. Connection Via VPN. Subscribers are SQL SERVER 2005 express..
Sometimes due to some structural changes, snapshot is to be re-applied. This is rare but is possible in our case.. On some subscribers snapshot applying goes on for hours and days with no sucess.
Are there any step by step instructions on how we can reintialize or reapply the snapshot on those subscribers manually i.e. maybe by copying the replication folder manually to subscriber and applying manually..
We have a web server set up on the DMZ that talks to a SQL 2005 server on the company domain.
The issue is, we are trying to install this CMS engine that requires a domain account from the SQL server to access a share on the web server that is in the DMZ.
Is there a way to trust a domain account to have access to a share on the DMZ server? I have heard of "read only" and one way trusts. Is that secure and if so how would we go about setting that up?
Basically I want to avoid at all costs of putting the SQL Server on the DMZ server but need a seamless way to access a file share from the trusted SQL Server.
Just want to share my "findings" the prerequisites of enabling replication over internet
1) if subcriber's computer name is ABC, make sure you add alias ABC in distributor machine. the alias HAS to be
same name. and make sure u add alias in both 32bit and 64bit
section of sql configuration manager
2) in subscriber machine, make sure you enable Named Pipes protocol for both 32bit and 64bit sectoin of sql configuration manager
(1) solved the problem with "bla bla bla NOT SUPPORTED" error, and (2) solved my problem with "concurrent snapshot for publication bla bla bla is not available"
I've searched far and wide, and so far have not been able to find any reference to this issue.
There is a merge replication setup on a SQL 2008 server, setup to replicate to SQL 2008 Express edition. We have similar setups in SQL 2005 AND SQL 2008 without issues. The setup is that the current merge replication snapshot file location is
\\<ServerName>\Repldata\UNC\<SERVER_PUBLICATION>\20101229112828 which represents the file location of the latest snapshot which was just generated due to an obsolete snapshot.
The issue comes in when attempting to replicate against the server. The replication says that the schema script could not be propogated to the subscriber. Under normal circumstances I would say it's due to security issues with being able to read to the above
folder, however this is not the case. The additional error that comes up is stating that it could not read the file along with an OS error 3 (The system cannot find the path specified).
What is unique about this, is that the subscriber is trying to download the snapshot from an old and now non-existent snapshot folder. Here is an copy of the error, noting the file location of "20091121130613" which no longer exists and is from an old snapshot.
I run a simple .aspx website on a Windows Server 2008 machine.
There is NO impersonation, and
System.Security.Principal.WindowsIdentity.GetCurrent().Name returns NT
AUTHORITY\NETWORK SERVICE, which it the account which the application
pool runs. In my web.config, I have <authentication mode="Forms">.
I tried to test the security of the
application and server by removing file permissions to the .aspx files. I
was greatly worried when the website continued to run without problem
(it should not have been able to read the .aspx files).
on file level auditing, I discovered that the .aspx files were being
read by the machine$ account (if the machine is called Serv1, then the
files would be read by the Serv1$ account, which seems to have access to
all files on the local machine).
Is this a security breach or is this behaviour by design ?
Please can somebody assist, as I am worried.
Our search is not working. The crawl log indicates following error: "Access is denied. Check that the Default Content Access Account has access to this content, or add a crawl rule to crawl this content. (The item was deleted because it was either not found or the crawler was denied access to it.)".
If I check the event viewer, it indicates following error: "Login failed for user 'NT AUTHORITY\NETWORK SERVICE'. [CLIENT: <local machine>]"
My default content access account is another one than this NT AUTHORITY\NETWORK SERVICE account. The content access account password is correct. Apparently this content access account is translated to the NETWORK SERVICE account upon a crawl. And this network service account doesn't has the appropriate rights on database level. How can I fix this?
Our client has a SharePoint (moss2007) site on Windows 2008, SQL2008 R2 Enterprise, and Reporting service is integrated with SharePoint
The authentication on the share point integration is set to windows, else the authentication for the SSAS datasource gives and error
The extranet zone ( forms) and intranet (Customer Forms) and default (Windows) zones are all access from inside the firewall and the reports render in each with no issues, as the datasources are configured to pass a sql username and password.
However, report rendering is a problem from the internet (external site), the following error is displayed:
We are accessing our sharepoint services 3.0 document library through outlook 2007.
We can open the files in word/excel etc, but when we go to check-in the document the application tells us that we only have read access to the document, and cant check the document back in to the server.
It works fine via the browser, the read only problem is only when checking out through outlook.
I have given all users full access and design access to the doc library.
Any help would be greatly appreciated.