ASP.NET 2.0 - Publishing to Server Problems

[Bill Cohagan]

I've built a small app based on the Personal web site template and it works
fine on my development machine (within VS2005). When I Publish it to a
Windows Server 2003 machine it *almost* works fine. There are two problems,
one minor and one major:

1.) After publishing to the server I have to go to the server and manually
set the ASP.Net version up to 2.x since it defaults to 1.1.x. [Minor, but a
nuisance].

2.) The SQL2005 database that ends up on the server is Read Only. The web
app can apparently read it, but if it tries to write to it the app crashes
with an error page complaining that the database is Read Only. [Major
Problem!]

3.) None of the accounts created (in the database) on the development
machine work on the Server version. The logins fail, but it is impossible to
create a login using any of the names of accounts created on the development
machine. That tells me that the accounts are there, but don't work. I
*think* this is because (maybe) there's a different application guid on the
server, but don't know. If that's the problem then how do I deploy such an
application without losing all of the data?

Thanks in advance,
Bill

PS - I've tried both Publishing from the VS IDE and running an msi created
in a VS Setup project. Either way I get these problems.

 

[Yuan Ren[MSFT]]

Hi Bill,

Thanks for posting!

For the first issue, the version is decided by the setting of the root site
in IIS. If there is no ASP.NET v1.1 application in the root site, I suggest
you set the version to v2.0 for the root site. After next deployment, the
version for the current application will be v2.0.

¡°The SQL2005 database that ends up on the server is Read Only.¡±

I do not understand this issue very clearly. Does this mean that the
account only has the read permission in the SQL Server Database or
something else? Could you please give me some details?

¡°None of the accounts created (in the database) on the development

machine work on the Server version. The logins fail, but it is impossible
to create a login using any of the names of accounts created on the
development machine. That tells me that the accounts are there, but don't
work.¡±

Does that mean you created the same account (I mean these accounts have the
same credential information) both in the development machine and server
machine? If not, could you please give me more detailed steps? This will
help me to understand the current issue clearly. I appreciated your
understanding.

I¡¯m looking forward your reply!

Regards,

Yuan Ren [MSFT]
Microsoft Online Support