I have been working for about a year with Crystal Reports in Visual Studio.NET 2003. I've had a number of applications successfully deployed. I finally convinced the company that I needed to use a dedicated server for deployment, as the configuration issues can be such that I don't want to impact anything on other company servers. I've been given a Windows 2003 SP1 box with IIS 6.0 to work with.
I'm using NT authentication to pass credentials to a SQL Server 2000 database, then running Crystal Reports XI.
All of this works fine on Windows 2000 SP4 server with IIS 5.0. But the same applications do not run on my 2003 box.
My first error is when attempting to connect to the database. I get an error "Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'." I'm using Integrated Windows authentication and have the good old "identity impersonate="true" in my Web.config file. The dumb thing about this, is that last week, I was working all day at trying to resolve this error without success, and then the next morning I simply logged on and have successfully logged on up until mid-day yesterday. I rebuilt my application, pointing to the production database, and the problem reappeared. Since then I have rebulit the release to point to the other database again, same error message.
I have other problems with getting the Crystal Reports to run, but I might already have a handle on those issues. It's been impossible to verify since this error message popped up again.
I'm just about certain the problem here will be in the Windows 2003 configuration or perhaps on the database side... any help is appreciated!
I'm using NT authentication to pass credentials to a SQL Server 2000 database, then running Crystal Reports XI.
All of this works fine on Windows 2000 SP4 server with IIS 5.0. But the same applications do not run on my 2003 box.
My first error is when attempting to connect to the database. I get an error "Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'." I'm using Integrated Windows authentication and have the good old "identity impersonate="true" in my Web.config file. The dumb thing about this, is that last week, I was working all day at trying to resolve this error without success, and then the next morning I simply logged on and have successfully logged on up until mid-day yesterday. I rebuilt my application, pointing to the production database, and the problem reappeared. Since then I have rebulit the release to point to the other database again, same error message.
I have other problems with getting the Crystal Reports to run, but I might already have a handle on those issues. It's been impossible to verify since this error message popped up again.
I'm just about certain the problem here will be in the Windows 2003 configuration or perhaps on the database side... any help is appreciated!