Jump to content

ALFIE

Members
  • Content Count

    46
  • Joined

  • Last visited

About ALFIE

  • Rank
    Junior IT
  • Birthday 07/07/1976

Profile Information

  • Gender
    Male
  1. ALFIE

    WEB SERVER IS BUSY

    Σ ευχαριστώ Blackman. Το κακό είναι ότι δεν έχω ένα virtual περιβάλλον να το δοκίμαζα και να τελείωνα. Πάντως κι έγω με το ψάξιμο που έκανα έδειχνε οτι δεν είχε πρόβλημα με το attach. Απλά πρώτα θα κάνει την βάση σε recovery mode και μετά θα παίζει κανονικά. Αν βρείς κάτι παραπάνω μου το λές. Προς το παρόν τους έβαλα και έσβησαν 300 ΜΒ και ανάσανε λίγο η DB. Αλλά δεν θα το γλιτώσω στο τέλος.
  2. ALFIE

    WEB SERVER IS BUSY

    Αν μπορέσεις να το βρείς θα το εκτιμούσα πολύ. Περίεργα πράγματα χμ χμ.
  3. ALFIE

    WEB SERVER IS BUSY

    Blackman αφού το install θα γίνει πάνω στον Server που έχει τον SharePoint και το MSDE το machinename/sharepoint δεν θα είναι το ίδιο? Στην ουσία upgrade τον MSDE σε Sqwlexpress 2005 δεν θα κάνει? Οπότε γιατί ναμην παίξει το attach των βάσεων?
  4. ALFIE

    WEB SERVER IS BUSY

    Microsoft Office SharePoint Portal Server 2003 είναι σε MSDE και η ερώτησή μου είναι αν θα παίξει με SQLEXPRESS 2005.
  5. ALFIE

    WEB SERVER IS BUSY

    O sharepoint2003 παίζει με Sql Express 2005??
  6. ALFIE

    WEB SERVER IS BUSY

    Τα ρωτάω αυτά διότι με το ψάξε βρήκαι και αυτό : Guide to Reinstall - Migrate SPS 2003 to SQL 2005 (September Community Technology Preview) aka "fancy doubling/trebling the speed of your SPS installation?" Posted Saturday, October 22, 2005 9:51 AM από το μέλος dimitrisv Just succeeded in setting up Sharepoint Portal Server 2003 to run on SQL 2005 September CTP and I thought, due to the huge improvement in performance (2-3 times faster depending on the task), that it may be useful to many so I decided to share the process with you here. The task was to use the same kit of hardware and have SPS and SQL2005 on the same machine (clean install). Here is how it is done: 0. Because I dont want moaning and groaning for broken promises go and get yourself Microsoft ® Windows Server ™ 2003 Performance Advisor and measure your existing systems performance. 1. You run the BackUp and Restore Utility of SPS in order to back up your site and you save it in another server. 2. Remove the server from the domain. 3. Setup your Windows 2003 Server (preferably with SP1 included). If you have a six disk server go for: 2XRAID 1 (system), 3XRAID5 (data), 1XRAID0 (tempdb, SPS indexes). 4. Do join the domain during setup - long gone are the issues of not finding the domain etc (assuming that your DC is also W2k3 SP1) (4a. Follow the steps of your Hardware Manufacturer -HP in my case (i.e. the post installation steps of SmartStart 7.40) - and reboot) 5. Apply all the post SP1 patches (18 to date). 6. Add the role of application server to the server through the wizard - enabling ASP.NET but NOT the FrontPage extensions. 7. Make sure that you do not alter (for the time being) the default locale from English and you add other services that you may like i.e. SMTP etc. and do work such as setting the page file, process priority, formating your SQL data partition to disk allocation size of 64k (it really does improve performance!) and you reboot. 8. Set up your SQL 2005 Enterprise by selecting all default options - apart from the location of your data files (to that partition that you formated with that 64k allocation size which is the optimum) and following the completion of the setup you reboot (just to ensure that everything is up and running). It is worthwhile not to use SQL security - Just leave it to windows authentication and start the service to a local user account that you create in your system (SQL -depending on your logging- can be quite demanding on the AD if you use a domain account). Now alter the localle to that of your previews installation. Bear in mind that there are installation issues of the reporting services with non-english default localles so this is why I told you in step 7 of not altering your locale prior to SQL installation. It will spoil the RS installation. And here is the juicy part: 9. Download WSS WITH SP2 from here: http://www.microsoft.com/downloads/details.aspx?FamilyId=B922B28D-806A-427B-A4C5-AB0F1AA0F7F9&displaylang=en and install by selecting option two (member of a Server farm - do not install MSDE). In the web page based configurration wizzard that will start you just stop after the set up of the first page. i.e. the page that you select the application pool identity and the authentication type which MUST be KERBEROS . 10. Press next, cmd iisreset and OK. You have now finished with your WSS set up as far as its coexistance with SPS 2003 is concerned. 11. Go to your SQL 2005 and give full permissions to the user that is running the application pool you created before. This is the user that will be used to create and later to modify the config database. 12. Insert your WPS 2003 CD. It detects that you have WSS it will give you a warning about the unlinking of your existing sites (which you duly ignore) and then goes ahead with the installation of the core engine. 13. Needless to say that you wont choose MSDE installation and that you will point your installation to your SQL 2005 instance, that you will choose another partition for the Data and that you will use the user you created before in order to create the SPS_config Database (use the same user to be sure that you have the password right and that he has permissions to even be databasecreator. 14. The installation will finish and will present you with the first pages of set up of the portal. Go ahead to select the user that will run the application (the one you made earlier), define the email settings and choose the topology (i.e. index, site, search all in the same box). 15. Very crucial point here: You close your IE window right here and you apply the SPS 2003 SP2 which you can find here http://www.microsoft.com/downloads/details.aspx?FamilyId=171DC9A7-B4BA-4759-BD64-6B7D851A97EF&displaylang=en You are almost done. 16. Create in your IIS the site where your sharepoint site will sit (in case you dont use the default - as many paranoid people like myself avoid using from the times of IIS 5 and earlier) and your provide the appropriate host header. 17. Move your backup data from the server that you saved them (before the format of the original machine) to the partition that wont host your actuall server data (i.e. you copy it to C if on D is where your data will actually be placed - it is very important this as it will save you quite a few minutes). 18. Now you run the SPS Back Up and Restore tool and you restore your databases and the site setting to the very final detail (users, user sites everything gets migrated). Attention though here. If you have huge databases (in my case the site database was tens of Gigs) the restore of the database can take hours. In the first half an hour you may see the progress bar stuck in 0. You will also see that the SQL Data Folder the site database has claimed the space but it doesnot increases further but... you have to wait. Dont ruin here guys - watch it. You just wait and your take comfort from the fact that the hard disks are working like mad. Finally add rights to the databases that were just restored to the user in your new server. 19. After that you are... DONE! The database will reindex for a few more minutes (dont get nuts with the CPU in the 80s-100) and then you enjoy! You enjoy integration with reporting services of SQL 2005, you enjoy speed that lightening comperated to the SQL 2000 - well worth the effort.. 20. Run the performance advisor to validate your eyes (because you just wont believe your eyes with the improvement), make a tea and then move your SQL temp.db to another partition (either the RAID o or the systems but definately NOT in the same physical media as your data). That was my trouble-free experience. It may not be yours however. For that reason in order to be save you take backup of your 3 databases and also you detach them before you do the formating of your previous system and then migrate using the manual process (attach/restore to SQL and by specifing the database in the Portal Data Configuration Page). Dimitris Vayenas, MIEE. PS. If you deploy your Portal to the internet or to wireless users (with RADIUS-SSL) you may find this link extremely useful. I wrote it because during my off line demos had diffuculties in getting my SSL issued from my CA/IAS server. It also include the links to two of the most useful deployment articles you may see at Technet for all those interested in giving really secure Wireless Acceess in your company. PS2. Yes the installation is in a production environment and the server runs so fast that is worthwhile browsing/using from the internet. Sorry for not including the reports. Silly me I forgot to save the initial reports. If someone need the new ones please write a comment and will post them. PS3. In the new system I also used two fixed paging spaces of 4096 MB in the system and data disks.
  7. ALFIE

    WEB SERVER IS BUSY

    Σ ευχαριστώ για την άμμεση σου απάντηση. H sql express 2005 με τον sharepoint πιστεύεις οτι θα έχει κάποιο πρόβλημα?Δλδ απλό install, atttach τις databases και παίζουμε??
  8. ALFIE

    WEB SERVER IS BUSY

    Καλησπέρα, Έχω ένα server windows 2003 με στημένο Sharepoint Portal 2003 σε MSDE. Το πρόβλημα που παρατηρήθηκε είναι οτι στο checkin και checkout των documents βγάζει μήνυμα WebServer is Busy. Η database έχει φτάσει στα 2gb και μετά από έναν έλεγχο διαπίστωσα οτι το MSDE limitation είναι 2gb γι αυτό και το μήνυμα WebServer is Busy. Any suggestions?? Αν πάω σε SQL express 2005 θα λυθεί το πρόβλημα? Και η διαδικασία είναι install τον SQL express 2005 attached τις βάσεις και όλα οκ?Κάθε βοήθεια ευπρόσδεκτη!!!
  9. Σ ευχαριστώ Νίκο, τελικά έλανε restore το corrupted file το προγραμματάκι restore toolbox for excel, απλά έκανε 3 μέρες να το τελειώσει. Τέλος καλό όλα καλά λοιπόν
  10. Καλησπέρα! Ξέρει κανείς κάποιο πρόγραμμα free που δεν θέλει registration codes ή activations κτλ που να κάνει recovery-repair corrupted files σε Εxcel 2007? Ευχαριστώ!
  11. Autoexec the best of the best
  12. Έκανα την δουλειά με το PsInfo από SysInternals. Ζήτω ο Mark Rusinovitsh
  13. Σ ευχαριστώ αλλά και πάλι δεν βοηθάει διότι δεν δείχνει το συνολικό χρόνο που είναι up το PC αλλά τον χρόνο απο το restart ή το ξαφνικό κλείσιμο μέχρι που έγινε up and running. Θέλω τον συνολικό χρόνο που είναι up το PC από τότε που φτιάχτηκε μέχρι σήμερα. Αν μπορεί να το δείξει με κάποιο τρόπο.
  14. Που είναι η επικεφαλίδα System??????Windows Server 2003.Και το up time είναι απο την ωρα που ανοιξε. Εγω ενδιαφερομαι για τον συνολικο χρονο ζωης του. Ευχαριστω!
  15. Καλημέρα! Υπάρχει κάποιο utility η κάποιος τρόπος να βρώ στους servers πόσσες μέρες είναι up and running απο τότε που ανοίχτηκαν γιαπρωτη φορα?
×
×
  • Create New...