While trying to troubleshoot a couple of bad queries, the application got upgraded. I opened an S.R with the vendor to see what new queries are running but I could not see anything new running in the database. The person I dealt with from support said that they hide their code. We have the usual solution stack: APPLICATION <--> MIDLLEWARE <--> DATABASE.
Is there a way to get around this?
Thanks in advance.
Related
I am having a very hard time making RavenFS behave properly and was hoping that I could get some help.
I'm running into two separate issues, one where uploading files to the ravenfs while using an embedded db inside a service causes ravendb to fall over, and the other where synchronizing two instances setup in the same way makes the destination server fall over.
I have tried to do my best in documenting this... Code and steps to reproduce these issues are located here (https://github.com/punkcoder/RavenFSFileUploadAndSyncIssue), and video is located here (https://youtu.be/fZEvJo_UVpc). I tried looking for these issues in the issue tracker and didn't find something directly that looked like it related, but I may have missed something.
Solution for this problem was to remove Raven from the project and replace it with MongoDB. Binary storage in Mongo can be done on the record without issue.
This error is occurring on every *.asp page in the application, but the *.aspx pages work just fine.
I did not develop the application, but the person who did has long since left the company. We have about 20 customers, all with the program working just fine. One of the customers had their server crash, and we had to re-set it up on their new server. Everything is working just fine now, except for this error on the *.asp pages.
The same connection string is used for all of our customers, so I know the problem is not there. There are no system DSNs or user DSNs defined on any of our customers.
This is a 32-bit application on a 32-bit server (server 2003 with SQL 2005).
I'm pretty sure it's a permissions or setting error, but I have checked absolutely everything I can think of.
Please help.
A company with 1400 employees can't use this program until I get it back up and running. I have no idea what else to do.
Thanks everyone for your help.
Sorry it took me a little bit to respond to you, but I had heard back from the original developer, and he had a hidden connection string deep within the program specifically to trip someone up if they were trying to install the program without authorization. He gave me the info I needed and it worked beautifully.
Thanks again!
I've been working with visual studio in a corporate environment for a long time, where we have a central SQL Server set up to store the data for all our in-house programs.
I've been asked to work on a side job for a small company where they want a program that will share data from a database between a half dozen computers.
My first reflex is to get them to set up a small server, install a database and then connect to it like I usually do, but before I start I'm wondering if there is a better way to do it.
Part of my problem is that if this works out really well, there is a chance that the program could be used in other companies, and I don't want to have to set up a server and write a custom version with a custom connection string for each one.
It could be that I'm thinking to deeply about this, I'm just hoping that a little research ahead of time might save a lot of time down the road.
Why would you need a custom build just to change the connection string ?
Just change your app App.config - or are we missing something here ?
What is App.config in C#.NET? How to use it?
I am completely new to Windows Azure and we don't have many people around the office that knows the technology, and those that do are out of the office and unreachable. so I turn to the community.
I have managed to:
Export my SQL Database to Azure standards and import it in for both sites currently using it.
Publish my sites to azure.
The issue is when I try and view any of the pages that require database information. That is, lets assume I try and view the locations page of my app at somesite.azure.com/locations this is suppose to pull in all my locatons instead I get: sorry error occurred while processing your request So I thought, this is a common database issue.
I was wrong - I think (you be the judge of that).
I made a second site that shares the database of the first site, this second site has a login, which goes to the database and checks your user name and password, well upon loggin in I get the same error, but it logs me in cause I redirect, but no data is displayed due to the error.
Is there a way to log the error? because the logging I have used only saved the error pages, like 500, 404, 503 and so on. but these error pages don't tell me much of any thing.
If it is a database issue, how can I get the specific error? When working in ASP and you throw and error the screen explodes into yellow anger. now I don't exactly want that, but I do want a stack trace.
This sounds like a database issue, but it might not be. Any ideas on how to trouble shoot. I don't find azures UI to be very friendly and the docs for this kind of thing are confusing.
The reason I don't think it is a database issue is because I let the publishing from VS 2010 to Azure create its own connection stirngs in the web.config file. but the fact that I cant display any data from the database points to that being the issue.
I'm using MigratorDotNet to manage Rails-style migrations for my web app. I have a workflow where, if I delete all the tables in the database, I can access an installation view that will run MigratorDotNet and create all the necessary tables.
This works locally. For some reason, when I upload my code to my Arvixe hosting, the migrations just never run. I get this odd error:
There is already an object named 'SchemaInfo' in the database.
This is odd because, prior to running migrations, I manually deleted all the tables in the database (to make sure it wasn't left over from a previous install).
My code essentially boils down to:
new Migrator.Migrator("SqlServer", connectionString.ToString(), migrationsAssembly).MigrateToLastVersion();
I've already verified by logging that the connection string is correct (production/hosting settings), and the assembly is correctly loaded (name and version).
Works locally, but not on Arvixe. How do I troubleshoot this?
This is a dark day.
It turns out (oddly) that the root cause was my hosting company used a schema other than dbo for my database. Because of this, the error message I saw (SchemaInfo already exists) was talking about their table.
My solution, unfortunately, was to rip out MigratorDotNet and go with FluentMigator instead. not only did this solve the problem, but it also gave me a more intelligible error message (one referring to the schema names).
While it doesn't seem possible to auto-set the schema, and while I need to switch the schema on my dev vs. production machine, it's still a solvable problem (and a better API, IMO). I googled, but did not find any way to change the default schema in migratordotnet.
I'm sorry for the issues that you were having. On shared hosting, unfortunately the only way that we may be able to change the schema is manually. If you are still looking for a solution that requires our assistance, please forward your ticket ID to qa .at. arvixe.com as well as arvand .at. arvixe.com and we can look into the best way to resolve this.