The graphic conversion tool is not working properly due to OS upgradation from windows server 2008 to 2022 in the client machine.

Question

1.00/5 (2 votes)

See more:

We are working for a web-based project which is related to Graphic conversion, we already developed the project and provided the web link to the client, so that client can directly access the link and open the tool in webpage. The client is using the Production machine which has "Windows server 2008" and recently we upgraded that to "Windows server 2022". After successful OS upgradation from 2008 to 2022, the tool was not working properly. So, what might be the cause of this issue? Please help me to resolve this issue. (for your information, the source code and any supporting files also not available in the client machine it is only the testing machine) Thanks in advance

What I have tried:

I tried some online solutions those were related to fix compatibility issues,

C:\Windows\SysWOW64\config\systemprofile, C:\Windows\System32\config\systemprofile

I have created 'Desktop' folder in the above path given the full control access to below users in the client machine

Everyone, IUSER, ISSUSERS,Aunthenticated users

Initially the tool was not opened. after giving the full control, tool was opened and taking input files but not generating the reports which we need.

Posted 23-Nov-23 20:33pm

rajasekhar dasari

Updated 24-Nov-23 7:09am

Andre Oosthuizen

v2

Add a Solution

Comments

Richard MacCutchan 24-Nov-23 3:41am

No noe here can possibly guess what is wrong, especially since you have not even described a problem. Please use the Improve question link above, and add complete details of what is not working.

Dave Kreskowiak 24-Nov-23 11:17am

With what you have provided in your post, it's impossible for anyone to tell you what the problem may be.

You're attempts to fix this problem are nothing more than wasted time. You have to diagnose the problem before you start making changes. Giving the server rights to the client Desktop is useless as the web server NEVER has access to the client machine at all.

You have to dig into the console in the browser and look for error messages and download failures. Look at the IIS logs on the server for any problems or crashes.

Without understanding the problem, anything you do to try and fix it is just a wild-ass gamble, and you'll lose every single time.

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

KarstenK · Answer 1 · 2023-11-25T06:58:00

That isnt answerable that way, so you must hunt down the bug. Best way is to write a log file at first shot along the "happy path". So you find the first place where the errors is happening and fiddle it out. Than test again with additional logging at this place, if the errors isnt obvious. (but ut should)

My best guess is that you use some system specific call or value which has changed between these two versions.

Andre Oosthuizen · Answer 2 · 2023-11-24T07:16:00

As the comments stated above, it is almost impossible to guess where the issue lies to a solution. Imagine that you have jsut tried to upgrade Windows from XP to 11, imagine how many apps will blatantly fail... The same happened with your upgrade, that is why there is upgrades, to improve from previous versions which means that the "old" code will become obsolete which can sometimes lead to compatibility issues, especially if there are dependencies or configurations that have changed in the new 2022 version.

Without proper checking we cannot even get close to suggest which steps you should follow.

The graphic conversion tool is not working properly due to OS upgradation from windows server 2008 to 2022 in the client machine.

2 solutions

Solution 2

Solution 1

Add your solution here

Preview 0