We have two Servers. One Windows 2008 and one Windows 2012. On both servers there is a domino Server (2008 - without fixpacks and 2012 - with fixpack 10). On the domino servers there are identical Xpages with identical customcontrols.
On the Windows 2008 Server everything works fine. On the 2012 Server we get a validation error on a number input which is a currency field. It says "This field is not a valid number" from server side validation.
I assume that it might have to do with the language setting on the server which is on the 2008 "Deutsch(Deutsch)" and on 2012 Germany(Germany).
Anyone has experience with Server settings in relation to server side validation?
-------Update-------
In the 2008 environment the converter looks like this:
<xp:this.converter>
<xp:convertNumber type="currency"
currencySymbol="€">
</xp:convertNumber>
</xp:this.converter>
I changed code in the 2012 environment to this:
<xp:this.converter>
<xp:convertNumber type="currency">
</xp:convertNumber>
</xp:this.converter>
And it seems to work. On the browser everything looks the same.
Check the decimal separator on the two servers. It's possible that may be different. It may also be a problem caused by currency symbol. Without knowing what values you've tried, it's hard to advise.
Related
I have a Web forms application that runs fine in Visual Studio 2012 but when I run int in VS 2013 I get
System.SystemException occurred
Message: A first chance exception of type 'System.SystemException' occurred in mscorlib.dll
Additional information: The trust relationship between the primary domain and the trusted domain failed.
for a stacktrace when loading up the inital page. I am not sure where to start in trying to figure out what is causing the issue. Its running on the same framework version and has the same web config
Update .... I switch Visual Studio 2012 to use IIS Express and now get the same exception in VS 2012 and VS 2013. Now to resolve the exception ?
Any idea ?
This is because 2013 does not use cassini web server but instead uses IIS Express. This can happen in Visual Studio 2012 as well if you enable IIS Express instead of Cassini. To fix this follow these steps:
In visual studio click on your web project and then press F4
1) Anonymous Authentication needs to be disabled
2) Windows Authentication needs to be enabled
Note: if one of these are grayed out that means that you have a override in your IIS Express Config file which is located
\My Documents\IISExpress\config\applicationhost.config
Check for
<section name="anonymousAuthentication" overrideModeDefault="Allow"/>
or
<section name="windowsAuthentication" overrideModeDefault="Allow" />
More information:
http://msdn.microsoft.com/en-us/magazine/hh288080.aspx
http://www.codegorilla.com/2012/12/how-to-enable-windows-authentication-when-using-iisexpress/
From the error I'm making the assumption that you are using windows authentication..
You can get this error if you are calling isInRole and pass a role that doesn't exist..
HttpContext.Current.User.IsInRole("SomeMadeUpRole");
With regards to the difference between running in 2012 and 2013, 2013 uses IIS Express which is basically a cut down IIS 7.5 instead of 7...
Not 100% sure on this though, would be glad to hear if this helps!
We're in the process of moving from 2003 IIS6 Web servers to 2008 R2 with IIS 7.5.
We also have a Windows 2008 server running IIS7 and everything works fine on this server.
On the new servers when we go to our crystal reports viewer page we get prompted for windows authentication, then if you type in valid credentials or not you get the following error in firefox:
XML Parsing Error: no element found
Location: http://192.168.10.112/Reports/ReportViewer.aspx?id=49
Line Number 1, Column 1:
^
In IE you just get a blank screen.
The same code runs fine in debug mode on the server in Visual Studio 2010, and works fine on our other servers
Thanks
I know that the answer is too late, but to be a reference for other users.
I faced this problem too in IIS 7.5, and after 5 days investigation, I found that the problem is because the Crystal Reports Viewer running as 32-bit, to solve this issue:
in IIS, go to Application Pools
Select pool that you are using it for your application, normally its "ASP.Net v4.0".
Click on "Advanced Setting..." in the right panel.
set the value "Enable 32-bit Application" to "True"
Also, note that you have to install the oracle client 32-bit version too.
I am specing out new development workstations for my team and I am running into a conflict. I am a developer and I want Windows Server 2008 R2 because that is what our production servers are running. The IT guys want to give us Windows 7 because that is where they have tested all their infrastructure.
My question is this: is there enough of a difference between the two to push for 2008 R2? I know MSFT has crippled IIS in previous versions of Windows unless it was the server edition so I am skeptical about Win7 giving me what we need.
You can use Windows 7 for your development machines and have one Windows Server 2008 R2 for UAT deployments. This way you can have the best of both worlds. IT will be happy that you are all running Windows 7 and you will be happy that you're able to test your application in windows server 2008.
This question answer might be helpful.
Differences between Windows 7 and Windows Server 2008 R2
Your IT guys are correct aside from licensing issues such cost as Office without workstation on OpenValue, OpenSelect etc.. (remember they are packaged together) etc.. there are hardware issues and compatibility with future software.
There is no way you need 2008 R2 Server, do you want to work in the data center too? or have a full copy of the live database? You should have a CI server though that represents the live environment , the IT guys should provide this for you - probably as a VM.
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
I'd like to move on Windows Server 2008 and could save 20 Euro every month if I am using Web Edition instead of the Standard Edition. The only "problem", Windows Server 2008 hasn't a build in DNS Server anymore.
Now I am asking me, which is the best third party DNS for my Webserver. I took a look on simpleDNS it seems quiet cool. Any additional idea or experience?
BIND. Plenty of documentation, and works just fine if you have time to learn.