MOSS 2007 Content DB used in transnational replication

Hello,
I have configured Transnational replication on Moss 2007 content DB over WAN, ?But it works well with small dbs of size 10-12 GB but with 40-60GB database sites are running in error like 404 Site not found....Checked in logs not luck found there also..
Any help guys.....
Regards,
Ashish

Hello,
To my knowledge only database mirroring and log shipping was supported with MOSS 2007. Log shipping is specially recommended for content
databases.
The following post talks about the benefits of using database mirroring vs log shipping:
http://blogs.msdn.com/b/mikewat/archive/2007/07/28/database-mirroring-and-log-shipping-which-is-better.aspx
To know more about these two high availability methods for MOSS 2007, please read the following article:
http://msdn.microsoft.com/en-US/library/ms179306(v=sql.90).aspx
http://msdn.microsoft.com/en-US/library/ms190640(v=sql.90).aspx
Hope this helps.
Regards,
Alberto Morillo
SQLCoffee.com
hello,
Thanks for the prompt reply, But would like to include the requirements as i need both end DB active so that can use application from both side and need to replicate to the point 24/7, that's why i had configure
1 way transnational replication.
And was successfully able to configure Replication for all varying size DBS but problem is that Site is not coming up for 50GBs Database, SO would like to ask if There any size limitation from Transnational replication with MOSS 2007.
Regards, Ashish

Similar Messages

MOSS 2007 Content DB Migration

Hi,
Is it possible to upgrade MOSS 2007 Content Database to SharePoint 2010 version Content Database without attaching the older Content Database to the SharePoint Farm?

Attaching the 2007 content database to a 2010 farm is how you upgrade the database. When the database attaches SharePoint recognizes it needs to be upgraded and upgrades it immediately.
Since you need to attach the database to the 2010 farm, you cannot upgrade it before this -- i.e. you cannot upgrade it to 2010 within a 2007 farm, nor can you upgrade it if the database is attached to no farms.
Jason Warren
@jaspnwarren
jasonwarren.ca
habaneroconsulting.com/Insights

MOSS 2007 Database Migration using SQL connection alias change throwing error

Hi Folks,
We are trying to move SharePoint SQL server from one DC to another DC.
Since we have made SQL server in new DC with other name so opted SQL server connection alias method to remap SQL mapping with existing farm.
After creating SQL alias we are able to browse central admin sites but could not able to browse any other sharepoint sites.
Event viewer showing below exception
SQL database login failed. Additional error information from SQL Server is included below.
Login failed for user 'computername$'.
Any view will be much appreciable.
Regards

First: Putting SQL Server on a domain controller is not recommended.
Are the two domain controllers in different domains? Is the SharePoint server in the same domain as the new SQL instance?
Do you have a SharePoint farm or a standalone installation? A
common cause of the error you're seeing is if the application pools are using Network Service or Local System which can be the case of a standalone installation.
Jason Warren
@jaspnwarren
jasonwarren.ca
habaneroconsulting.com/Insights

Rich Text Editor for Content Editor WPs (MOSS 2007) disappears using Office 2013/Win7/IE 11

We've upgraded our computers to Win7/IE 11 but now when I try to edit our MOSS 2007 Content Editor Web Parts, the option to choose either the Rich Text Editor or Source Editor is gone, and all I get is a tiny HTML window. What do I need to do to get back
the Rich Text edit option?

Glad that it worked. One thing you need to be aware of Compatibility View is that it adds the entire domain to the View not just the URL. So if your website is
http://sample.mycompany.com it adds entire mycompany.com to the list.
This implies if you have another site in the same domain http://onemoresite.mycompany.com , then Compatibility View is applicable even for that site. This might cause issues if your other 'breaks' when
rendered in Compatibility Mode.

While crawling content from Moss 2007 to Sp2013 its throwing error

hi,
When i am trying to crawl the Moss 2007 site content in SP2013 serach I am getting below Error in the Crawl error log.
I have provided owner access for the Moss 2007 content DB,to the user accout which i am using in SP2013 serach.And also provided read access for this account to the Moss 2007.But still i am unable to crawl.
1 The URL of the item could not be resolved. The repository might be unavailable, or the crawler proxy settings are not configured. To configure the crawler proxy settings, use Search Administration page.
2 This item could not be crawled because the repository did not respond within the specified timeout period. Try to crawl the repository at a later time, or increase the timeout value on the Proxy and Timeout page in search administration. You might
also want to crawl this repository during off-peak usage times.
3 The crawler could not communicate with the server. Check that the server is available and that the firewall access is configured correctly. If the repository was temporarily unavailable, an incremental crawl will fix this error.
4 Access is denied. Verify that either the Default Content Access Account has access to this repository, or add a crawl rule to crawl this repository. If the repository being crawled is a SharePoint repository, verify that the account you are using
has "Full Read" permissions on the SharePoint Web Application being crawled.
Thanks & Regards, Krishna

Try to use website as content source to crawl it
Create disableloopbackcheck registry on all sharepoint servers
Are you able to browse sharepoint sites from crawl server.
check
http://blogs.technet.com/b/josebda/archive/2007/03/19/crawling-sharepoint-sites-using-the-sps3-protocol-handler.aspx
http://sharepoint.stackexchange.com/questions/93691/using-sharepoint-2013-to-crawl-sharepoint-2007
If you are still struggling you can watch the requests by using Fiddler as a proxy for the crawl process. Then you can kick off the crawl and watch the requests and the response from the 2007 server.

Need to upgrade service providers of Moss 2007 to SharePoint 2013

I have upgraded the Moss 2007 Content database via native approach into SharePoint 2013. I am wondering how we can upgrade the service providers of Moss 2007 to SharePoint 2013 service applications.
Regards Restless Spirit

Hi Restless,
According to your description, my understanding is that you want to upgrade the service providers of MOSS 2007 to SharePoint 2013 service application.
Per my knowledge, you need to firstly upgrade the service providers of moss 2007 to SharePoint 2010 via database content, then upgrade SharePoint 2010 service applications to SharePoint 2013.
There are some useful articles for your reference:
MOSS 2007 upgrade - Shared-Services Provider SSP migration and my sites
MOSS SharePoint 2007 SSP migration to SharePoint 2010
Upgrade service applications to SharePoint 2013
Best Regards,
Wendy
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Wendy Li
TechNet Community Support

MOSS 2007; Manage Content & Structure = timeout & authentication request = 401

Hi,
I am having from time to time some issues with an older MOSS 2007 environment. Sometimes browsing to manage Content & Structure ends up in a long thinking process which ends with an authentication request. A Timeout seems to happen. Whatever a user enters...
it ends ip in a 401 error. That does not happen every time, but sometimes. The rest of Sharepoint works well.
Let me first describe the environment. The environment is fully virtualized. The content db is huge - the approx size is about 1 TB. There is only 1 site collection and quite a huge site structure.
The environment as such
2 WFE
1 IDX
1 SQL 2005 Cluster
We use Kerberos for authentication.
The w3wp processes grow to about 1-2 GB.
We have identified that when SQL Cluster fails from one node to the other.. this symptom disappears for a while. I have no clue what this can have to do with the described effects.
An IISRESET on all servers sometimes helps, too.
We cannot identify any errors, but the issue is really annoying.
Any thoughts?

Hi Sven,
I am trying to involve someone familiar with this topic to further look at this issue.
Thanks,
Daniel Yang
Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact [email protected]
Daniel Yang
TechNet Community Support

Cannot locate Orphaned Content in MOSS 2007 prior to updgrade to SharePoint 2010

I will soon be upgrading my MOSS 2007 farm to SP2010, so I had run the preupgradecheck command to check for any problems. It fails on "Issue: Orphan objects in Content Database" in 4 databases. It doesn't give Site IDs, only the SQL instance, the
database name and this "Integrated Security=True;Enlist=False;Connect Timeout=15" after the database name.
To try to resolve this problem, I have tried locating these using the stsadm databaserepair command, which brings back "OrphanedObjects Count="0"" for all the content databases. So after this, I tried using the enumallwebs command,
and exported this to a txt file, all fields for "InSiteMap" came back as "True" so there doesn't seem to be any orphaned site collections.
I've had a look around online, but the two options I've tried seem to be the way to locate them, and I can't find anything else.
Has anyone had this problem before? Is there another way that I can try to locate these orphaned objects? Are they likely to be sites, features, lists etc?
Thanks in advance for any help!

Content Database, this is most important stuff.
if you have mysite and User profiles then you need to move the SSP to 2010. check the below blog for steps and understanding:
http://blogs.msdn.com/b/alimaz/archive/2009/11/08/upgrading-moss-2007-ssp-user-profiles-and-mysite-content-to-sharepoint-server-2010-using-db-attach-method.aspx
Yes you dont need the Central admin.
Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog

MOSS 2007 Search - Crawling is taking longer than usual time since last month for same content sources

Hi all,
Off late we have discovered that content crawling is taking longer than expected also overlapping to next scheduled too. Literally no crawl logs seen for hours. No entry in crawl logs. Is there anyone out here having similar issue? Please share a solution
if any found.
My farm is implemented with MOSS 2007 SP2 Ver no 12.0.0.6554
There is not packet drop between index server, App and SQL server/Cluster
Thank you in advance,
Reach Ram
Ramakrishna Pulipati SharePoint Consultant, Bangalore, INDIA

I believe this is ready for submission for the Time Machine forum.
As noted, it does not cover diagnosis and correction of specific problems or errors, as that would seem to be better handled separately.
It also doesn't cover anything about Time Capsule, for the very good reason that I'm not familiar with them. If someone wants to draft a separate post for it, or items to add/update here, that would be great!
Thanks very much.

Data Migration from MOSS 2007 to SharePoint 2010

Hi,
We have done a migration project for one of our client.
This migration was done from MOSS 2007 to SharePoint Enterprise Server 2010.
After the migration was completed we developed lot of new webparts, lists ,application pages in this newly migrated farm in SharePoint Enterprise Server 2010.
However the entire project took around 1 year due to some unavoidable delays. During this one year our client was using MOSS 2007 sites for there work. hence the data in MOSS 2007 farm/sites was continuously updated.
Our client needs to go live in next month and also needs the sites/lists/libraries which are migrated in new SP 2010 farm to be updated as per the MOSS 2007 farm.
Kindly suggest best possible way to achieve this data migration since last 1 year from MOSS 2007 to newly migrated SharePoint Enterprise Server 2010 farm.
Kindly note we have done lot of customization and new developments in newly created SP 2010 farm.
Thanks and regards,
Amien

Hi there,
If you have already taken care of customization on SP2010 server. Then use any of the migration tools available in market to migrate data to target SP server.
Content Matrix gives free 25 GB to migrate your SharePoint data (https://www.metalogix.com/Resources/Promotions/Content-Matrix-Migration-Express-Download.aspx).
If you don't know what is changed in last 1 year, then best thing to do is add new content database and migrate your data into it.
Hope that helps.
Regards,
Tapan

Search not working in site collections migrated from MOSS 2007 to SharePoint Server 2013

I have few site collections migrated from MOSS 2007 to SharePoint Server 2013 using database attach (first to 2010 and then to 2013).
When I search for anything in these migrated sites, I get "Nothing here matches your search".
Checked the crawl log for these sites and see this error for all items.
The content processing component failed to process the security descriptor of the item. ( The input ACL is invalid (1210 / 2072).; ; SearchID =
Some-Random-GUID )
Search works fine in newly created sites in 2013 environment.
Please help.

Hello
Did you migrate your users to claims when you migrated the databases?
$wa = Get-SPWebApplication http://yourdom.com
$wa.MigrateUsers($true)
$wa.ProvisionGlobally()
I assume the sites that work and the migrated content are in the same database?
MCITP-EA | "Never test how deep the water is with both feet"

Migrating from Moss 2007 to SharePoint 2013

I am reaching out here as we require some inputs around migrating the SharePoint based application from MOSS 2007 to 2013.Please find more details from below
Requirement:
Migrating SharePoint site collection (which contains just 1 Top level site and 2 libraries with in it and no item level/library level permissions exists) which is on MOSS 2007 with size of 500GB to SharePoint 2013, hence we like to know your inputs in related
to this
Note:
1) The site collection has its own separate content database
2) There are nearly 200 thousand documents where the document with higher version is 90
3) The documents are stored in the libraries with up to third level of folder structure
4) The site collection is created based on custom site definition (created using visual studio)
Few things that I like to mention/ask here
a) Having 500GB data in one single content database inj the MOSS 2007 environment does it impacts the site performance?
b) Migrating the site collection as is onto single content database (all 500 GB into one content database) into destination SharePoint 2013, does it will be a good practice? Hope SharePoint 2013 content database limit is 200 GB, hence moving 500GB
as is into one database will it be good practice?
c) Does database attach and detach works for the databases which are of size 500GB?
d) Can we do database attach and detach directly from MOSS 2007 to directly onto SharePoint 2013, without hopping onto SharePoint 2010 in between and then later to SharePoint 2013?
e) If moving 500GB data into one content database will not be a good approach, can we split it onto multiple databases?
f) If database attach and detach doesn’t help for databases which are of size 500GB, should we go for any tool based approach? If yes, which tool does best fit?

a) Having 500GB data in one single content database inj the MOSS 2007 environment does it impacts
the site performance?
Inder: Yes, it will impact site performance at large extended, recommended is 200 gb only. Check it IO of your disk to analyze performance issue
b) Migrating the site collection as is onto single content database (all 500 GB into one content
database) into destination SharePoint 2013, does it will be a good practice? Hope SharePoint 2013 content database limit is 200 GB, hence moving 500GB as is into one database will it be good practice?
Inder:
Content database size (all usage scenarios)
4 TB per content database
Supported
Content databases of up to 4 TB are supported when the following requirements are met:
Disk sub-system performance of 0.25 IOPs per GB. 2 IOPs per GB is recommended for optimal performance.
You must have developed plans for high availability, disaster recovery, future capacity, and performance testing.
http://technet.microsoft.com/en-us/library/cc262787%28v=office.15%29.aspx#ContentDB
c) Does database attach and detach works for the databases which are of size 500GB?
Inder: Yes it does work
d) Can we do database attach and detach directly from MOSS 2007 to directly onto SharePoint 2013, without
hopping onto SharePoint 2010 in between and then later to SharePoint 2013?
Inder: No, you need to pass through 2010 and then 2013
e) If moving 500GB data into one content database will not be a good approach, can we split it onto
multiple databases?
Inder: you can go with 500 gb
f) If database attach and detach doesn’t help for databases which are of size 500GB, should we go for
any tool based approach? If yes, which tool does best fit
Inder: Below are few tools you can try
http://www.metalogix.com/Products/Content-Matrix.aspx
http://en.share-gate.com/
http://www.avepoint.com/sharepoint-migration-tools/
http://www.quest.com/sharepoint/migration.aspx
If this helped you resolve your issue, please mark it Answered

Losing out custom metadata info of few documents of a document librarby when migrated from MOSS 2007 to Sharepoint 2010

We have recently migrated from moss2007 to sharepoint 2010.We have a document library containing large no. of documents in it & for those documents there are some custom metadata columns apart from OOB library columns . We have user content DB attach
migration and after that we can see blank value under the custom columns for some records. However interesting point is we can see this metadata is showing for few documents.
Please suggest.

Hi,
What is your Office edition? When we create a managed metadata column in a Document Library, it will prompt that ‘Earlier versions of client programs might not support this type of column’. You should use Office 2010 to edit and create a document then save
to document library .
For detailed information ,please refer to this article:
http://rules.ssw.com.au/SoftwareDevelopment/RulesToBetterSharePoint/Pages/2010-Managed-Metadata-with-Office-2007.aspx
Beside, here are similar posts, you can use as a reference:
https://social.technet.microsoft.com/forums/sharepoint/en-US/1b115343-20e5-4962-af97-793194f07637/metadata-missing-when-revising-document
https://social.technet.microsoft.com/Forums/office/en-US/a65f9828-6e2f-4eb7-bde6-bd0600e3b1a2/migrating-documents-from-moss-2007-to-sharepoint-2010?forum=sharepointadminprevious
Best Regards,
Lisa Chen
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact
[email protected]

MOSS 2007- Migration Tools available for data extraction

Hi All,
I am working on MOSS 2007. I need export entire data from sharepoint portal to excel files. The data could be from Lists, Libraries, Content Types, Static Page data etc. The amount of data is huge.
1) Is there any migration tool available for such extraction? Kindly suggest.
2) Also is it possible to search for data in entire web site based on the content type?
Thanks.

Hi,
We don't have ready script, you might have to modify one.
Check below URL if they help you,
http://blogs.technet.com/b/heyscriptingguy/archive/2014/02/04/use-powershell-to-create-csv-file-to-open-in-excel.aspx
http://technet.weblineindia.com/web/export-data-to-excel-using-openxml-sdk/2/
https://support.office.com/en-us/article/Share-Excel-data-with-others-by-exporting-it-to-a-SharePoint-site-262ba5a9-d065-4ad6-9d92-c16a10ae8ac8?ui=en-US&rs=en-US&ad=US
https://selecteditemsexport.codeplex.com/
Regards
Prasad Tandel

Which databases are required to be moved in MOSS 2007 for upgrade to 2010?

Hi,
We are planning to upgrade MOSS 2007 environment to SharePoint 2010. As a next step, I have to move the following databases. Please correct me if we need to also move the Shared Services (SSP) content databases.
Content Databases of Main website (move required)
Content Databases of SSP (move required)
Content Databases of Central Admin. (move not required)
Thanks in advance!
LM

Content Database, this is most important stuff.
if you have mysite and User profiles then you need to move the SSP to 2010. check the below blog for steps and understanding:
http://blogs.msdn.com/b/alimaz/archive/2009/11/08/upgrading-moss-2007-ssp-user-profiles-and-mysite-content-to-sharepoint-server-2010-using-db-attach-method.aspx
Yes you dont need the Central admin.
Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog

MOSS 2007 Content DB used in transnational replication

Similar Messages

Maybe you are looking for