Ajax web part does not work in Windows server 2003 - windows-server-2003

I have an AJAX web part which is working properly in my local windows 7 environment, but when I deployed in the real environment which is running win server 2003, it doesn't work as I expected. Does anybody have an idea to resolve this? I am using MOSS 2007
Thanks in advance.

I found the problem to the situation. It was a matter mismatch between my development environment and the real deployment environment..
Btw thanks for your input as well...
Best Regards,
Asanka

Related

Imagemagick IIS install issue VBScript error "800a01ad"

I have Imagemagick running on a remote server and have had it running on a local server successfully for many years, but recently I have had need to reinstall on a new machine and can't for the life of me figure out what i'm doing wrong, It's probably really simple and I'm hoping someone can point me in the right direction.
Scenario
WIN 10 running iis as localhost
Successfully installed Imagemagick 32 and 64 bit so they run on the local machine, however when try to access the localhost web page requiring Imagemagic I'm receiving the following message
Microsoft VBScript runtime error '800a01ad'
ActiveX component can't create object: 'ImageMagickObject.MagickImage.1'
my app pool is current set to allow 32bt application and as far as I am aware all permissions are correct, although I do believe this may be the issue somewhere.
Can anyone help to shed some light on this issue.
Thanks :-)
Resolved.. It turns out the latest version of Imagemagick 7.1.x does not ship with ImagemagickObject.dll, fortunately, I had a saved download .exe for an earlier version 7.0.8 which still had the .dll, once install I could copy imageMagickObject.dll to the system32 folder, after that everything worked as expected. Not sure what would replace this in my code if I have to ever user a newer version, if someone knows please add to the post.

IIS not working after upgrade to Windows 10 Pro from Windows 7 Unlimited

Today I upgraded my windows 7 ultimate to windows 10 pro. Every thing seems to work fine. But the localhost is now throwing error : HTTP Error 503. The service is unavailable.
I checked IIS, it is running. I checked the version of IIS from IIS Manager, it is showing Version 10.0.10240.16384.
I test my sites on localhost.
Before upgrade, in windows 7 ultimate it was working fine. I also checked "Turn windows feature on or off" and found that IIS is installed properly.
Please guide me.
Thanks Joe Raio for providing the hint. I checked the event log and found that rewrite.dll was causing error. I uninstalled IIS URL rewrite extension and the problem is gone. Now everything is working as before, classic asp, php, everything.
Please try this solution
Go to the Application Pool ...
Advanced Settings ...
Process Model ...
Identity ...
Set it to "LocalSystem"

Why this Help Desk System redirects me to the old server?

I am using the Liberum Help Desk as a Service Request System. It is host on a server that is running Windows Server 2008 R2 32-bit. I configured it with an Access database. It works well. Now, I am trying to shift it to another server running Windows Server 2008 R2 64-bit. At the beginning, I have an error with the JET driver, because there is no JET driver for the 64-bit machines. I fixed it by enabling 32-bit option in the advanced settings of the application pool. However, I am still facing a strange problem which is the following:
When I tried to browse the system that is on the new server (64-bit), it will redirect me to the system hosted on the old server (32-bit) and I don't know why. I checked the code to see if there is any link or something for redirecting me to the old server and I did find anything.
So how to fix this problem? what is the reason of it?
Finally, I found the solution. The problem was with the Access Database; there is a table called config and inside it there is a column for determining the link. I changed the link there and everything works fine.

Installing add-ins for SharePoint Foundation 2010 on Developer Win 7 Pro

I'm having a lot of trouble getting SharePointRS_x64.msi to install sucessfully says it cannot find sharepoint when in fact that sharepoint is installed and running on Win 7 Pro. Because of the operating system I am unable to install the prereq package that comes with SharePoint Foundation 2010 (which includes this reporting addin).
I already have a reporting server set up for my MSSQL2008 instance(win 2008 server R2). It's working when I go to the http:\servername\Reports i'm able to launch the report builder and everything works. I'm now having trouble setting up the other end on SharePoint (different (developement) machine - running win 7 pro).
Any Help would be GREATLY appriciated.
Please let me know if what I want to do is possible.
Thanks,
Mike
I found the solution.
You need to open config file:
C:\Program Files\Microsoft SQL Server\MSRS10.\Reporting Services\ReportServer\rsreportserver.config
In this config find string:
Add Key="SecureConnectionLevel" Value="2"
Change value 2 to 0.
Values meaning:
3 - Most secure-Use SSL for absolutely everything.
2 - Secure-Use SSL for rendering and methods that pass credentials but don't insist on it for all SOAP calls.
1 - Basic Security-Accepts http but rejects any calls that might be involved in the passing of credentials.
0 - Least Secure-Don't use SSL at all.
You have to remember that installing sp2010 on your desktop is going to limit your farm. It is not going to be a fully functional farm. Advanced features like search and user profile sync will not work/get buggy. I guess now, you can add reporting services intergration to the list of things that don't work. Safe your self a lot of trouble but building a vm, which is going to be closer to your production environment anyway.
UPDATE
I thought it might not be supported by Foundation, but it is:
http://msdn.microsoft.com/en-us/library/bb326356.aspx

Server.Transfer not working on IIS7

I have a few ASP pages. One of them is using Server.Transfer to load another ASP page. But the page does not get called. If I change it to Response.Redirect, it is working fine. Can anyone help me?
By the way, it is working fine on IIS 6 on Windows Server 2003. It only has problem when I moved to IIS 7 on Windows Server 2008.
Thanks
transfer can only support within same domain...
Try changing your code from Server.Transfer to Server.TransferRequest.
I have found this works for IIS 7 applications running in Integrated Mode.

Resources