Hello Dears System Admins,
I have a problem with my application within Win server 2008
, when it is work well within Win server 2003
when I try to use my app with win_ser2008 get the following error message:
Server Error in '/yyy' Application.
ORA-00161: طول فرع الحركة 90 غير مشروع (العدد الأقصى المسموح64 )
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details: System.Data.OracleClient.OracleException: ORA-00161: طول فرع الحركة 90 غير مشروع (العدد الأقصى المسموح64 )
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
I'd make an image and deploy that, making users responsible for backing up their own files to a server somewhere. Although, with all the "windows geniuon" b.s. it's probably not as easy as it used to be to deploy images of an OS.
P.S. oh, and I'm also assuming that most of the computers are the same, i.e. same drivers will be required, but with that many computers, it's probably not the case.
namely I have to configure it to fix with different driver, right?
If you have different hardware, you pretty much have to do a complete install on each computer... there may be tools to help in this process but I don't know about them since I've never had the need to update that many machines.
More important part, is there any configuration i have to customize on my machines to meet windows 7 requirement?
Tips/tricky parts for transferring files back? for update outlook? etc.
This really depends on what applications people are using and where they're storing their files, you could write scripts to automate all the backups but problem is that people have a tendency of storing files all over the drive instead of just in their directories (major pain). With outlook you pretty much have the same problem, if people left their mail on the server, then it's not an issue, but if they downloaded the data (made data files), it could be anywhere in the system (i.e. wherever each user configured it to be).
also I was told that before updating, user has to backup their own data, is it the only way? automated updating without ruining files/data not gonna happen, right?
Like I said above, you could automate things, but you're bound to find that people stored files where you didn't expect and end up losing files for some. Maybe you can break up the upgrade into small groups of computers (let's say ten), run your backup scripts that should back up all the files that are in expected locations (user folders) then make images of their hard drives before doing the upgrade. Once you upgrade the systems, run scripts to put the files back. The users can then go look at their system to see if all of their files are there, give them a timeframe (say a week) to verify, if they're missing files you can go to the images of the old drive to look for the files. This will make the process slow but at least you won't piss off as many people.
I Change the language for the database in Sql Server 2008 ( To Arabic_CI_AS )via the optional tab in database proprieties .
but when i Insert new record( have Arabic Text) in any table the text change to ???? .
Mac OSX and Windows NTFS are incompatible file systems, so in order to make one work with the other as you describe:
* You must partition the storage medium with two or more partitions and provide for a dual-boot system.
* One of the operating systems must provide intrinsic support for the other - an emulation tool, native drivers or provide a shell.
* One of the operating systems must provide a tool that permits re-provisioning and co-location.
Since you already have Windows loaded on your machine, re-partitioning would be destructive. Sure, there's dual-boot tools and even some that claim non-destructive re-partitioning, but YMMV and rule #33 of Mike's rules of happy computing is don't trust 3rd party hacks when it comes to your boot sector.
Windows doesn't intrinsically support OSX. OTOH, OSX does have intrinsic support for windows. The problem, as stated, is that the egg came before the chicken in this instance.
There are no tools I know of for Windows that permit re-provisioning the partition/boot sector/OS load and file system to play paddy-cakes with a Mac OS, so your options are hence somewhat limited.
The madman is not the man who has lost his reason; the madman is the man who has lost everything except his reason.
After posting this question, I continued my previously fruitless search and finally came up with this[^] piece of software.
I may give it a try after a complete backup.
If it works, great! Otherwise... I hope my backups work.