Windows Azure, ASP.net MVC 4 - Issues with pages - asp.net-mvc-4

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.

Related

Possibilities of Datazen server migration

I know that similar topics have been already raised, but maybe there are some latest news or ideas?
I want to migrate Datazen users/sources/dashboards etc. to another server (production one) in a smooth way. I was trying to do that via backup/restore, but then I couldn't access the control panel on the target server. I received an error
401 unauthorized access.
Maybe I should change something in logs/config files on the destination server?
Any ideas? I would be grateful for any help!
I dont think there is a way to do this out of the box. However, the files are quite simple XML, so can be pointed at a different server if you know PowerShell (and work out the correct values from the server).
You will have to re-point the GUID, ServerGUID and ServerURI within the sources.xml file and then rezip (as .datazen). Providing you have your hubs set up the same, Datazen will then believe the file belongs to your prod environment and you will be able to publish

PouchDB corruption detection

I am building up a webapp with offline functionality. I am using combination of webcache and pouchDB to achieve it.
Currently I am testing recovery mechanisms against DB corruption. My premise is that since pouchDB is running in client, it is exposed to anyone who by mistake or on purpose can corrupt the DB. Also maybe in case of bugs or similar, DB could get corrupted. Then, if DB gets corrupted, unless it gets detected and clean by webapp, this will never work correctly.
Test is quite simple:
- Create PouchDB:
var dbOptions = {
auto_compaction : false,
cache : false
};
var db = new PouchDB('myDB',dbOptions);
With Developer Tools delete part of the database.
On loading the application it tries to read all documents:
db.allDocs({include_docs : true}, function(_err,_response){
(certain code here)
}
It is at this point when "Uncaught TypeError: Cannot set property '_rev' of undefined " is thrown. I tried to catch exception and using provided promise by pouchDB but none did work.
Did any of you fellows have similar problem? How did you solve it?
EDIT:
When PouchDB returns 500 Internal error, how is the application supposed to recover from it? I tried to destroy the database
db.destroy(function(err,info){console.log(err||info);}
but it does not work. It returns 500 Internal error as well.
It indeed sounds like your database got corrupted. Sorry about that; we try to write bulletproof code, but since we're working against the WebSQL/IndexedDB APIs, there's always the possibility that something goes wrong at that interface, the browser crashes, lightning strikes your computer, etc.
500 errors indicate an internal PouchDB error, so you're not supposed to recover from them. Probably the best way to protect against corruption like that is just to set up continual sync with a CouchDB server (kind of the point of PouchDB anyway). CouchDB is a full database implemented from top to bottom and is very robust – since it uses append-only database files, your database can never get corrupted. So if you use continuous sync, you can always delete the PouchDB database and recover from CouchDB.
That being said, if you could let us know which version of PouchDB you're running, which browser you saw this on, or even a code snippet to reproduce, that would be really helpful. If you're using Firefox, you can also send us the storage files themselves for IDB by following the instructions here to find the Profile folder and then sending us the contents of the storage/persistent/<my_site>/idb folder. Thanks!
I got this error while adding a new schema to my RxDB database. It turned out I included the primary key and wrong property names into encrypted fields. I removed the primary key and put proper names and it worked fine after that.

Domino web app Error 500 HTTP Web Server: Corrupt Data Exception

I have a Domino App that runs on the web as well as in the lotus notes client. I can open and save my main form in the LN client without issues and i can open it in the browser as well. When i try to save it in the browser, i get the "Error 500 HTTP Web Server: Corrupt Data Exception" page displayed. I made a copy of the form, and started removing all of the fields on the original one field at a time and still got the error page. I copied an identical form from my test database to the production db thinking that would work but i get the error "Error 404 Entry not found in index" error page with that form.
I am at a complete loss as what to do next so i am hoping that someone here can give me a little direction.
Thanks
Corrupt Data Exception is usually displayed if: 1 open the document in web, 2 change the designe of the form 3 try to save.
Did you removed all cache of you browser (ok this is trivially but I can't be sure you checked this)
could you check in the log.nsf what is the precise error written there (Corrupt Data.. which DB which &seq= )
did you try rebooting (or at least tell http restart) the server?
the 2nd part Entry not found in index, check if the form makes a DBlookup or what ever:
- on view in the current DB that is in test
- on another DB which design doesn't contain same design element in prod than in test
if all this doesn't help make a backup of the db and try fixup and so on.

Problems with BigQuery and Cloud SQL in same project

So, we have this one project which uses Cloud Storage and BigQuery as services. All has been well.
Then, I wanted to add Cloud SQL to this project to try it out. It asked for a unique Project ID so I gave it one. (The Project ID is different than the Project Number.)
Ever since then, I've been having a difficult time accessing my BigQuery tables. When I go to the BigQuery web interface, the URL contains the Project ID instead of the original Project Number. It shows the list of datasets, but now shows the Project Number before each dataset name and the datasets are greyed out and inaccessible. If I manually change the URL to contain the Project Number instead of the Project ID, it appears to work although it shows the list of datasets in the left nav twice, one set greyed out and inaccessible and the other set seemingly accessible.
At the same time, some code that I've been successfully using in Apps Script that accesses BigQuery is now regularly failing with a generic "We're sorry, a server error occurred. Please wait a bit and try again." I'm not sure if this is related to the Project ID/Project Number confusion, or if it's just a Red Herring.
Since we actively use the Cloud Storage service of this project, I am trying to be cautious with further experimentation with this project. I'm not sure if I should delete the Cloud SQL service in this project to get it back to the way it was, or if this is a known issue with some back-end solution. Please advise.
After setting the project id, there can be a delay where BigQuery picks up the change. It should happen within 15 minutes or so, but sometimes it takes longer.
If you send the project ID I can make sure it has been updated.

How do I get back to my Reporting Services Data?

I have almost exactly this problem. I say, almost exactly because the answer that worked for this gentleman did nothing whatsoever for me. I can open my own database and see all of the lovely RS data sitting there staring at me but the actual Reporting Services installation still can't. This all came about because of precisely what he said. We accidentally left the password policy on on the Reporting Services account and it expired. When I changed it the whole thing went kaputt. I'm still getting the "key cannot be used in current state" error message even after dropping all encrypted data from the RS installation. I have no access to the Report Manager to reset encrypted information. Has anyone got any suggestions?
EDIT: In continuing my research I found this suggestion. It's not that.
Well... here's the thing.
I eventually tried creating a whole new user to take charge of the SSRS operations. I also remembered to update those details on our live data server. (I did this first and it failed to work as it was still telling me the key could not be used then.)
I guess that there must be something that prevents the reassignment of the SSRS gofer account's password. The new user is set up identically and works perfectly. So that's what cleared it up for me but I'm a little irritated that I still don't know exactly why...