I don't think I've ever been there longer than half an hour from the time I park to the time I'm out. It's all they do, and they're good at it. Going to bring my Jetta here since they won't charge extra for it like most places.
Waiting room chairs could be softer and have handrails, I've helped a couple of oldtimers get up from these seats. Pros: Fast service, no up-selling, kind employees, car kept clean, reasonable and fair pricing for most of their services (especially windshield wipers)!Ĭons: Location, it's adjacent to Meineke Muffler store so its hidden out of sight from Brick Blvd and there's no easy way to turn around once you drive past it. It took me a while to figure it out, but I noticed that if I had an oil change sticker from another place on my windshield they'd tell me that that place stripped my oil plug and that I'd need a replacement which *luckily* they have on hand for just $5.Īs long as Quicky is around I will continue to have my vehicles serviced by them. The property was sold to a drug store chain, and we moved to our present. We started out in 1988 in Brick, on the corner of Midstreams Rd and Rt 88, then moved to the corner of Bridge Ave and Rt 88 in 1997. No upselling for things you do not need like that Silver Bay Car Wash & Oil change place in Toms River I used to go to. Specialties: Oil Changes(conventional, synthetic, high mileage), coolant changes, transmission fluid changes, wiper blades, air filters, headlight restoration, bulbs, Established in 1988. Wish they did more than the basics, because they'd be great at it! NET Framework Version:9 ASP.NET Version.There are many other Oil change businesses closer to my house, but its worth traveling to Quicky Oil change because I don't have to wait for hours for a 15 minute oil change and they don't try to oversell me things I don't need.īeen here many times, with all three of my cars and always get great service. (IIS7WorkerRequest wr, HttpContext context) +731 InitializeApplication(IntPtr appContext) +343 (IntPtr appContext, HttpContext context) +402 (HttpApplicationState state, MethodInfo handlers, IntPtr appContext, HttpContext context) +172 (IntPtr appContext, HttpContext context, MethodInfo handlers) +186 (HttpContext context, HttpApplication app) +540 Information regarding the origin and location of the exception can be identified using the exception stack trace below.Ĭ(Int32 mapCount, String connectionString, String sql, Object map, Object param, String splitOn, Nullable`1 inTransaction) +3177 (provider: TCP Provider, error: 0 - The remote computer refused the network connection.)Īn unhandled exception was generated during the execution of the current web request. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. The server was not found or was not accessible. Please review the stack trace for more information about the error and where it originated in the code.Įxception Details: : A network-related or instance-specific error occurred while establishing a connection to SQL Server. (provider: TCP Provider, error: 0 - The remote computer refused the network connection.) Description: An unhandled exception occurred during the execution of the current web request. (provider: TCP Provider, error: 0 - The remote computer refused the network connection.) Server Error in '/' Application.Ī network-related or instance-specific error occurred while establishing a connection to SQL Server. A network-related or instance-specific error occurred while establishing a connection to SQL Server.
0 kommentar(er)
