Hi @inivasDL
Data upload problems are usually the first indicator of some configuration problem after a new Galaxy is first started up.
That said, sometimes odd errors, including this one, are produced when a file is not completely uploaded (new server or not). There could be many reasons for that with a local Galaxy server. A local Galaxy needs some admin configuration to be used without problems coming up. Some of this we can help with and some of this will be specific to your computer/network that we can’t help with (since it is private) but we do have documentation that covers the basic setup and use cases.
There will be a training event in March that includes administrative topics. Many of the tutorials linked above will be included. Anyone can join. The event is global, asynchronous, and many more people from the community will be available to help. GTN Smörgåsbord 2: 14-18 March | Gallantries
You can also go through those tutorials on your own now and try to uncover the problem, or at least be able to provide more context about your configuration so the community can assist here. Examples of information that will help: Galaxy version, computer OS/version, dependency management choice(s), what admin configurations you have done, plus how some tests worked out. Have you installed tools and run tool tests? The goal is to find out things like: Do other datasets load properly? This same file type fails (always/sometimes? from different sources or just one particular source?). Do other data upload successfully – or do all uploads fail? Has any upload ever worked? Have any tools ever worked? If the analysis was successful before, have you made any changes since things worked?
What may be best if you do not want to go through all the administrative setup/tests, and this is a new server that you haven’t heavily invested in already:
Try an alternative deployment choice. Docker Galaxy comes with more of the administrative details pre-configured. Details here: Galaxy Docker - Galaxy Community Hub