November 16, 2011 at 8:02 am
I was installing a HRMS application that runs on SQL server 2005 and developed using ASP.NET. The installation file is a MSI. During installation i didn't encounter any error and the process finished as usual. But when i saw the installation log, (which was more than 16 MB in size) it contained a list of queries which were to be executed in the Database. Naturally, he application refused to run on IIS.
I believe that , this can't be a rights or permissions issue as the application was able to create a single table in the database.
Please help me out as this is pretty urgent.
P.S: I am a Newbie and a functional guy.
November 16, 2011 at 8:13 am
Your first stop for this kind of problem should be the application vendor's support people. They're more likely to have a clue than we are (since we have no idea what the app is, what it's supposed to do or anything)
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
November 16, 2011 at 8:18 am
Thanks for the quick reply...! In this case i represent the application vendor but i am not from a support or development background. 🙂
I can give you a brief description on the software. It is basically a payroll application which can run over the intranet as well as on the web. I am very curious about this issue as i have done more than 7 installations but never experiences this kind of issue. Your support would be of great help. Please put up some questions if required, i will try to answer them if it helps me get to the root cause of this problem. Thanks..
November 16, 2011 at 8:23 am
What did you find in the install logs?
That's really have you have to go on if you don't call support.
November 16, 2011 at 8:26 am
@ ^
Only "Create Table" queries. The log usually shows the queries that are to be executed on the database. The error type was "SQL ERROR:". But as i mentioned earlier only one table related to Reimbursements got created, the database, apart from this was blank.
November 16, 2011 at 8:31 am
Back to call the vendor... nothing we can do here for you.
November 16, 2011 at 8:33 am
Fine. Thanks for the replies guys.
November 16, 2011 at 8:33 am
It sounds like something broke the connection in the install. I'd tend to agree that it's not rights if you use the same connection/credentials to run all the queries and you had one table created.
It sounds like you don't have enough logging or error handling. Can you re-run one of the queries using the credentials the installer uses?
November 16, 2011 at 8:36 am
krishikrish (11/16/2011)
Fine. Thanks for the replies guys.
Sorry I missed the part about who you were.
If you have an exact error as it happens we can defenitely help.
November 16, 2011 at 8:45 am
krishikrish (11/16/2011)
@steve-2 JonesYes, i can and tables do get created when I run the queries given in the install logs manually. Must be a connection issue only. But how and where do i check these configurations...?
Do you have a try catch around those executions?
Maybe you simply need to add a retry logic if anything happens.
November 16, 2011 at 8:49 am
Ninja's_RGR'us (11/16/2011)
krishikrish (11/16/2011)
@steve-2 JonesYes, i can and tables do get created when I run the queries given in the install logs manually. Must be a connection issue only. But how and where do i check these configurations...?
Do you have a try catch around those executions?
Maybe you simply need to add a retry logic if anything happens.
Nope. There is no try catch around the executions. I tried installing the MSI more than 3 times but in vain. I got the same result each time. Can it be due to some windows services not running in the background...?
November 16, 2011 at 8:51 am
krishikrish (11/16/2011)
Ninja's_RGR'us (11/16/2011)
krishikrish (11/16/2011)
@steve-2 JonesYes, i can and tables do get created when I run the queries given in the install logs manually. Must be a connection issue only. But how and where do i check these configurations...?
Do you have a try catch around those executions?
Maybe you simply need to add a retry logic if anything happens.
Nope. There is no try catch around the executions. I tried installing the MSI more than 3 times but in vain. I got the same result each time. Can it be due to some windows services not running in the background...?
MSI is way out of my expertise, world for that matter.
I'm with Steve on this one. If you created 1 table, then it's not the services nor the permissions.
Anyway you can run the MSI from VS in debug mode? We need to know what's really going on. Guessing is not going to get anywhere fast.
November 16, 2011 at 10:01 am
Two things I can think of. And you might need to run a trace/profiler session as you run the MSI to check. Make sure you run the code from the trace, not your log.
1. There's a syntax error of some sort in the code that's conflicting with some setting on this instance. Potential collation issue or something else.
2. No retry logic and there's maybe a conflict with an existing object/schema and the installer doesn't account for that.
Can you drop the database and re-run the install from scratch? Can you run against another instance? Those tests might help you narrow down the issues.
Ultimately someone probably needs to clean up the installed to include better code checks and error trapping/handling.
November 16, 2011 at 8:39 pm
As i mentioned in my earlier post, i tried installing the application many times after dropping the DB. As of now, i believe a fresh installation of SQL server is the only option.
Viewing 15 posts - 1 through 15 (of 19 total)
You must be logged in to reply to this topic. Login to reply